Changes between Version 3 and Version 4 of MapGuideRfc119

Timestamp:

07/19/11 01:46:34 (14 years ago)

Author:

samwang

Comment:

--

MapGuideRfc119

@@ -28 +28 @@
 == Motivation ==
 
-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 value
+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 value
 {{{
 Concat('http://www.map.com/fid=', FeatId)
 }}}
-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 this feature, e.g a hard coded string "www.google.com". We have to specify where to store this value.
+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.
   
 == Proposed Solution ==