Changes between Version 16 and Version 17 of MapGuideRfc16


Ignore:
Timestamp:
Feb 23, 2007, 8:44:19 AM (17 years ago)
Author:
chrisclaydon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc16

    v16 v17  
    3737=== Layer Definition Schema Modifications ===
    3838
    39 The layer definition schema contains numerous <!ExtendedData1> elements that allow the schema to be extended without breaking forward or backward compatibility. The changes proposed in this RFC would initially be added into one of these elements, and would eventually be moved to the main part of the schema whenever the next schema version update is carried out. See [wiki:MapGuideRfc10 MapGuide RFC 10] for more details.
     39The layer definition schema contains numerous <!ExtendedData1> elements that allow the schema to be extended without breaking forward or backward compatibility. The changes proposed in this RFC would initially be added into one of these elements, and would eventually be moved to the main part of the schema whenever the next schema version update is carried out. See [http://wiki.osgeo.org/index.php/MapGuide_RFC_10_-_Make_Schemas_More_Amenable_to_Interim_Enhancements MapGuide RFC 10] for more details.
    4040
    4141The affected section of the original schema looks like this:
    … …  
    140140
    141141This RFC does not describe any modifications to the GUI tools used to create layer definitions. The elevation settings would need to be configured by manual modification of the layer definition XML files.[[BR]]
    142 Because the changes are contained in an <!ExtendedData1> element, a layer definition can be read, modified, and saved by !MapGuide Studio, and the elevation settings will be preserved.[[BR]]
    143142There are no changes to the existing public API.
    144143