= !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 ==

This is a more detailed description of the actual changes desired.  The contents of this section will vary based on the target of the RFC, be it a technical change, website change, or process change.  For example, for a technical change, items such as files, XML schema changes, and API chances would be identified.  For a process change, the new process would be laid out in detail.  For a website change, the files affected would be listed.

== Implications ==

This section allows discussion of the repercussions of the change, such as whether there will be any breakage in backwards compatibility, if documentation will need to be updated, etc.

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