Changes between Version 6 and Version 7 of MapGuideRfc95

Timestamp:

06/21/10 09:06:48 (15 years ago)

Author:

brucedechant

Comment:

--

MapGuideRfc95

@@ -11 +11 @@
 ||Last Modified||Arthur Liu 06/13/2010||
 ||Author||Arthur Liu||
-||RFC Status||draft||
+||RFC Status||ready for review||
 ||Implementation Status||under development||
 ||Proposed Milestone||2.3||
@@ -50 +50 @@
 }}}
 
-It is necessary for MapGuide implement an API ProcessBoundingBoxAxes to handle different axis orientation for the bounding box parameter in GetMap and GetFeatureInfo operation. For example: change (lat,lon) back to (lon,lat).
+It is necessary for MapGuide implement an API !ProcessBoundingBoxAxes to handle different axis orientation for the bounding box parameter in !GetMap and !GetFeatureInfo operation. For example: change (lat,lon) back to (lon,lat).
 
 {{{
@@ -67 +67 @@
 The other important change in WMS 1.3.0 specification is the CRS namespace. WMS 1.3.0 specification introduced two more CRS namespaces besides EPSG, they are CRS namespace which in the form specified by ISO 19111 and  AUTO2 namespace is used for "automatic" coordinate reference systems.
 
-In order to pass the OGC certification, the CRS CRS:84 must be supported. There's a workaround that it could be predefined in OgcWmsService.config.
+In order to pass the OGC certification, the CRS CRS:84 must be supported. There's a workaround that it could be predefined in !OgcWmsService.config.
 
 {{{
@@ -94 +94 @@
 After the implementation of OGC WMS 1.3.0 enhancement, an official OGC certification(http://cite.opengeospatial.org) will test if MapGuide provides standard WMS service.
 
-== Funding/Resources ==
+== !Funding/Resources ==
 
 Supplied by Autodesk.