Ability to interrogate configured MapGuide Feature Sources over HTTP about georest HOT 2 OPEN

This sounds like a cool idea.  I actually thought we already had something like 
that, but it may just be for the OData support (/$metadata request)

I wonder if this would be best at the base URL for the service (/rest/data/, 
with XML, JSON, and templatable HTML results), or as a sidebar (/rest/config/ 
or something like that).  I'm leaning towards the former.  If we did go with 
the former, it would be a great starting point for metadata publishing as well; 
the config file could eventually be extended with things like title, 
definition, author, accuracy, etc...

As part of this, I would like to see an extension to the Resource and 
Representation entities that flags them as "hidden" from the service 
description.  I'm relying on obscurity for a couple services that I want to use 
internal to templates (as joined feature sources) but which I wouldn't want to 
publish and support for external use.

There are a few different levels where editability is controlled, from HTTP 
protocols supported in the GeoREST config, through readonly flag on FDO data 
source, to underlying RDBMS permissions. I'm guessing that this feature would 
only take into account the GeoREST configuration.