[mapserver-commits] r8528 - trunk/docs/development/rfc

[svn at osgeo.org]

Author: assefa
Date: 2009-02-11 17:49:12 -0500 (Wed, 11 Feb 2009)
New Revision: 8528

Modified:
   trunk/docs/development/rfc/ms-rfc-30.txt
Log:
Update RFC with more info

Modified: trunk/docs/development/rfc/ms-rfc-30.txt
===================================================================
--- trunk/docs/development/rfc/ms-rfc-30.txt	2009-02-11 18:45:03 UTC (rev 8527)
+++ trunk/docs/development/rfc/ms-rfc-30.txt	2009-02-11 22:49:12 UTC (rev 8528)
@@ -7,9 +7,11 @@
 :Date: 2007/06/15
 :Author: Daniel Morissette
 :Contact: dmorissette at mapgears.com
-:Last Edited: 2007/09/05
+:Author: Yewondwossen Assefa
+:Contact: yassefa at dmsolutions.ca
+:Last Edited: 2009/02/11
 :Status: Draft
-:Version: MapServer 5.2
+:Version: MapServer 5.4
 :Id: $Id$
 
 Overview
@@ -27,8 +29,8 @@
 This RFC is mostly to document those changes and the way MapServer deals 
 with them.
 
-Technical Solution
-------------------
+Coordinate Systems and Axis Orientation
+--------------------------------------
 
 The main issue introduced by WMS 1.3.0 is the change in the way it handles
 axis order for several SRS. This has an impact on the way the
@@ -48,17 +50,65 @@
 information about the axis order of all EPSG SRS codes and treat them
 using the correct axis order.
 
-New SRS codes in the CRS:xxxx space have also been added by WMS 1.3.0
-that will need to be supported by MapServer
+New CRS codes such as CRS:xxxx and AUTO2:xxxx have also been added by WMS 1.3.0
+that will need to be supported by MapServer. Note the wo types of Layer CRS 
+identifiers are supported by the specification: “label” and “URL” identifiers.
+The intention is to support at this point the label types CRS. 
 
+List of CRS planned to be supported are:
+
+- CRS:84 (WGS 84 longitude-latitude) CRS:83 (NAD83 longitude-latitude)
+CRS:27 (NAD27 longitude-latitude) CRS:1 (pixel coordinates)
+
+- AUTO2:42001 AUTO2:42002 AUTO2:42003 AUTO2:42004 AUTO2:42005
+
+EPSG codes: when advertising (such as BoundingBox for a layer elemnt) or using 
+a CRS element in a request such as GetMap/GetFeatureInfo, elements using epsg code >=4000 
+and <5000 will be assumed to have a reverse axes.  
+
+
 All the above need to be done in a way that allows continued support for
 older versions of the WMS specification (1.0.0 to 1.1.1) and will have 
 the least impact on existing WMS services.
 
-At this point the exact implementation details have not all been sorted out.
-They will be documented here as we refine them.
+Implementation for the reverse axis will follow closely to what was already
+done for WCS1.1 support (http://mapserver.org/development/rfc/ms-rfc-41.html)
 
 
+WMS and SLD
+-----------
+
+All references to SLD support has been removed from the WMS 1.3.0 specifications.
+It has been replaced by two specifications:
+- Styled Layer Descriptor profile of the Web Map Service
+- Symbology Encoding Implementation Specification
+
+The Styled Layer Descriptor profile allows:
+- to extend the WMS to support additional operations (DescribeLayer, GetLegendGraphic)
+- addtional parameters related to the SLD for the GetMap support
+- advertise SLD support.
+
+This specification will be supported in the current implementation. 
+Note that the GetStyles operation (available in WMS 1.1.1) might not be supported
+in the first phase
+
+The Symbology Encoding Implementation represent basically the definitions for the 
+different symbolizers. We need to upgrade the current SLD support to support this
+specification.
+
+  
+
+HTTP Post support
+-----------------
+
+HTTP Post support is optional and currently supported by Mapserver WMS 1.1.1.
+WMS 1.3.0 defines that if POST is supported, the the request message is formulated 
+as an XML document.
+Although this is highly deirable, the first implemenation of the WMS 1.3.0 might
+not support the XML Post requests.
+   
+
+
 MapScript Implications
 ----------------------
 
@@ -71,9 +121,10 @@
 
  mapwms.c
  mapwmslayer.c
- ...
+ mapfile.c
+ mapows.c/h
+ mapogcsld.c
 
-
 Backwards compatibility issues
 ------------------------------