= !MapGuide RFC 108 - Support Watermark =

This page contains a change request (RFC) for the !MapGuide Open Source project.
More !MapGuide RFCs can be found on the [wiki:MapGuideRfcs RFCs] page.


== Status ==

||RFC Template Version||(1.0)||
||Submission Date|| July 30,2010 ||
||Last Modified|| Buddy Hu, July 30,2010 ||
||Author|| Buddy Hu||
||RFC Status|| Draft||
||Implementation Status||(pending)||
||Proposed Milestone|| 2.3 ||
||Assigned PSC guide(s)||(when determined)||
||'''Voting History'''||(vote date)||
||+1||||
||+0||||
||-0||||
||-1||||
||no vote|| ||

== Overview ==

This RFC updates MapGuide to support Watermark.

== Motivation ==

Some customers complaint that there is no standard way to add watermark to the Map definition.

== Proposed Solution ==

1.	Create a new resource type that contains information about watermark. This resource is used to define the what element to use(image or text) and where/how to place the watermark.

2.	User can use watermark by defining reference from map. The Map definition will be extented to reference the optional watermark resource. And a Map definition can reference multiple watermark resources.

3.	The watermark of WMS will automatically be the same as the published map.

4.      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.

== Implications ==

MapGuide Mastro should update to support watermark.

== Test Plan ==

How the proposed change will be tested, if applicable.  New unit tests should be detailed here???

== Funding / Resources ==

This section will confirm that the proposed feature has enough support to proceed.  This would typically mean that the entity making the changes would put forward the RFC, but a non-developer could act as an RFC author if they are sure they have the funding to cover the change.