Changes between Version 44 and Version 45 of MapGuideRfc119

Timestamp:

Aug 2, 2011, 7:53:21 PM (13 years ago)

Author:

samwang

Comment:

--

MapGuideRfc119

@@ -38 +38 @@
 where '!FeatId' property is the property to identify a unique feature of the feature class. So the URL of a feature in this layer should be in the form 'map.google.com/fid=[!FeatId]' where [!FeatId] part will be replaced with the actual '!FeatId' property value for each feature. However if user wants to change the URL of a specific feature(and only this one) which turns out to be 'map.bing.com/fid=[!FeatId]' for some reason. It is obvious that we can not change URL element value that will affect all other features. So what we can do is to specify a property of the feature class that the layer is based on where we can store this overriden value.
 
-So when new shcema containing these information is applied(as proposed below), a sample of part of the new XML should look like:
-
-{{{
-<UrlData>
- <Content>Concat('map.google.com/location=', ADDRESS)</Content>
- <Description>Concat('Feature at location:', ADDRESS)</Description>
- <ContentOverride>URL</ContentOverride>
- <DescriptionOverride>DESCRIPTION</DescriptionOverride>
-</UrlData>
-}}}
-
-
-Normally, if a feature does not individually override its layer's setting. Then the URL and description of this feature of should be the evaluated value of the FDO expression specified. That is to say, if the ADDRESS property value of this feature is "627 5th Avenue", then the URL of this feature is "map.google.com/location=627 5th Avenue" and respectively description of this feature is "'Feature at location: 627 5th Avenue". Otherwise if user want to use a different URL, he can override this value and store it in URL property and if he wants to use a different URL description, he can store it in DESCRIPTION property. Both overriden setttings(specified in "ContentOverride" and "DescriptionOverride" elements) take precedence over layer setting(specified in "Content" and "Description" elements).
-  
 == Proposed Solution ==
 We need to change the vector layer definition a little bit. First we add a XML complex type named "URLDataType" to represent URL information.
@@ -103 +89 @@
 The same rule applies to URL description.
 
+So when new shcema containing these information is applied(as proposed above), a sample of the new XML should look like:
+
+{{{
+<UrlData>
+ <Content>Concat('map.google.com/location=', ADDRESS)</Content>
+ <Description>Concat('Feature at location:', ADDRESS)</Description>
+ <ContentOverride>URL</ContentOverride>
+ <DescriptionOverride>DESCRIPTION</DescriptionOverride>
+</UrlData>
+}}}
+
+
+Normally, if a feature does not individually override its layer's setting. Then the URL and description of this feature of should be the evaluated value of the FDO expression specified. That is to say, if the ADDRESS property value of this feature is "627 5th Avenue", then the URL of this feature is "map.google.com/location=627 5th Avenue" and respectively description of this feature is "'Feature at location: 627 5th Avenue". Otherwise if user want to use a different URL, he can override this value and store it in URL property and if he wants to use a different URL description, he can store it in DESCRIPTION property. Both overriden setttings(specified in "ContentOverride" and "DescriptionOverride" elements) take precedence over layer setting(specified in "Content" and "Description" elements).
+  
+
 == Implications ==
 A new version 2.4 of the layer definition schema was recently added to support RFC 113, and the schema changes proposed in this RFC will be added to this version.  Backward compatibility with older versions of the schema will be maintained, and schema documentation will also be updated.