Changes between Version 8 and Version 9 of MapGuideRfc119
- Timestamp:
- Jul 19, 2011, 1:59:28 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MapGuideRfc119
v8 v9 28 28 == Motivation == 29 29 30 Current layer definition schema already defines an element "URL" in "!VectorLayerDefinition" complex type to store URL definition. However,we may need further details of the URL, such as description of URL which can be displayed to user. Also, we may assign an FDO expression to URL element which designates a layer level URL setting for features, but at the the same time, we may as well would like to override it for a specific feature. For example: the URL xml element has been assigned Fdo value30 Current layer definition schema already defines an element "URL" of type string in "!VectorLayerDefinition" complex type to store URL information. However, this is too simple and we may need further details of the URL, such as description of URL which can be displayed to user. Also, we may assign an FDO expression to URL element which designates a layer level URL setting for features, but at the the same time, we may as well would like to override it for a specific feature. For example: the URL xml element has been assigned Fdo value 31 31 {{{ 32 32 Concat('http://www.map.com/fid=', FeatId) 33 33 }}} 34 where '!FeatId' property is the property to identify a unique feature of the feature class. The the URL of features should be something like "http://www.map.com/fid=123" for feature with FeatID=123. At the same time, a user may want to change the URL of this feature to something else, e.g a hard coded string "www.google.com". We have to specify where to store this value.34 where '!FeatId' property is the property to identify a unique feature of the feature class. The the URL of features should be something like "http://www.map.com/fid=123" for feature with FeatID=123. When a user wants to change the URL of this feature to something else, e.g a hard coded string "www.google.com", we have to specify where to store this value. 35 35 36 36 == Proposed Solution == 37 We need to change the layer definition a little bit. First we add a XML complex type named "URLDataType" to represent URL information.37 We need to change the vector layer definition a little bit. First we add a XML complex type named "URLDataType" to represent URL information. 38 38 39 39 {{{ … … 67 67 </xs:complexType> 68 68 }}} 69 The meaning of child elements this complex type is well explained in its annotation.69 The meaning of child elements in this complex type are well explained by their annotations. 70 70 71 71 Then change the original "URL" element in "!VectorLayerDefinition" from simple type "xs:string" to complex type "URLDataType".
