| 34 | | 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. |
| | 34 | 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. |
| | 35 | |
| | 36 | 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. |
| | 37 | |
| | 38 | 3. The watermark of WMS will automatically be the same as the published map. |
| | 39 | |
| | 40 | 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. |
