Changes between Version 12 and Version 13 of MapGuideRfc108

Timestamp:

Aug 11, 2010, 5:50:59 AM (14 years ago)

Author:

hubu

Comment:

--

MapGuideRfc108

@@ -32 +32 @@
 == Proposed Solution ==
 
-1.      Use the symboldefinition to define the content of watermark. The watermark supports text and image.
+1.      Create a new resource type for watermark, which defines content (in the format of an inline symbol definition), appearance (rotation / transparency) and position information of watermark. The schema of watermark definition is attached below.
 
-2.      Create a new resource type  for watermark. This resource reference the symboldefinition and define the position, rotation and transparency of watermark. Add a new XSD file to define the watermark, and the !MdfModel and !MdfParser are needed to updated about this change. 
+2.      User can add a watermark to MapDefinition or LayerDefinition by referencing corresponding watermark resource(s) in it. However, we do NOT support inline watermark in MapDefinition and LayerDefinition.
 
-3.      Support inlining the watermark in mapdefinition and layerdefinition.
+3.      When MapDefinition or LayerDefinition references a watermark resource, it can choose to override its appearance and position information to bring flexibility to the user. The override attributes defining in MapDefinition or LayerDefinition has a higher priority than that in watermark when rendering.
 
-4.      User can use watermark by referencing it from map and layer. The mapdefinition and the layerdefinition will be extented to reference the optional watermark resource. The Layerdefinition and Mapdefinition can reference multiple watermark resources. 
+4.      When being rendered, the watermark group of an MgMap is actually the collection of the watermarks referenced in its MapDefinition and the watermarks referenced in the LayerDefinition in it. 
 
-5.      Change the render logic for map. When all the layers have been rendered and the renderer hasn’t output the result, render the watermark into the result.
+5.      When using watermark in LayerDefinition, user can decide in what situation the watermark is visible during rendering by defining “Usage” properties. For example, a watermark of a WMS layer is only visible when the value of its “Usage” properties is “WMS” or “ALL”. (There is no such problem when using watermark in MapDefinition, because it will never be used in WMS.)
 
-Please refer to the attachment to find the schema of WatermarkDefinition and the updated schemas of LayerDefinition/MapDefinition.
 
 == Implications ==