MS RFC 30: Support for WMS 1.3.0

[Kralidis,Tom [Burlington]]

> One last RFC before the weekend, I promise! :)  MS RFC 30 is to 
> document changes required in order to upgrade MapServer's OGC WMS 
> support to version 1.3.0:
> 
> http://mapserver.gis.umn.edu/development/rfc/ms-rfc-30
> 
> It was not clear whether this would require a RFC or not since this is

> just an upgrade to a new revision of an already well supported spec, 
> but after some discussion on the topic on IRC a little while ago it 
> was agreed that given the type of changes introduced by this revision 
> of WMS we should properly document the changes/issues in a RFC.
> 
> Unfortunately I have not yet sorted out the exact way that I will deal

> with the changes, and especially the new axis order handling (the main

> issue in WMS 1.3.0), but I have a good idea in mind and wanted to get 
> this RFC out as a heads up that I plan to add WMS 1.3.0 in MapServer 
> 5.0, and you should expect more details soon on this... and of course 
> I will fill in as much details as possible in the RFC before I call 
> for a vote on it.
> 

FYI here's the original ticket behind this:
http://trac.osgeo.org/mapserver/ticket/473

Market behaviour shows us that 1.1.1 is still the most heavily used.
WMS 1.3.0 came out in 2003, and adoption has been very slim.  It might
be something "good to have" in the OGC suite within MapServer, though.

Can the XML output can be done via libxml2?  Note that OGC:WMS 1.3.0
does NOT support OWS Common (which mapowscommon.c implements), but
future versions will.  This would position MapServer OGC:WMS support for
turnkey integration once OGC:WMS 1.4.0 is adopted (N.B.: most OGC specs
are or will be to be deriving from OWS Common).