[mapguide-internals] Moving more config options into MapDefintion Resource Headers (RFC?)

[Trevor Wekel]

Hi Zac,

Currently header information in the resource repository is used to define security attributes and metadata for the resource.  It is "extra" information that does not really define attributes of the resource.

<ResourceDocumentHeader xsi:noNamespaceSchemaLocation="ResourceDocumentHeader-1.0.0.xsd">
  <Security xsi:noNamespaceSchemaLocation="ResourceSecurity-1.0.0.xsd">
    <Inherited>true</Inherited>
  </Security>
</ResourceDocumentHeader>

I would consider image format, selection color, and the meta tile factor all attributes of a map definition.  As such, they should be included in the XML document.

Jason also mentioned a separate base map (tile set definition).  There are a few ways to do this.  I would probably add the image format (two formats: normal and base layers), selection color, and meta tile factor to our current MapDefinition and then add a second "tile" MapDefinition to WebLayout and ApplicationDefinition.  As far as I know, both viewers render the base tiles as a separate div tag so it wouldn't be much work to point them at a different MapDefinition.

Since we are about to hit beta, I'm not sure if RFC90 should be considered for inclusion in 2.2.  According to our posted release process, no new features should be submitted after the beta.  http://mapguide.osgeo.org/releaseprocess.html.  Definitely something to consider.

Also, any changes to MapDefinition or LayerDefinition right now would probably break cross compatibility between MGE and MGOS.  Studio wouldn't work with MGOS and Maestro may not work with MGE. 
 
Regards,
Trevor