OGC WMS becomes ISO Standard
The Open Geospatial Consortium (OGC) notes in its latest press announcement that the Web Map Service (WMS) implementation specification has finally been adopted as ISO 19128. After the Simple Feature implementation specification, WMS is the second OGC standard adopted by ISO, and some others are in the progress of becoming ISO standards (such as the Web Feature Service implementatin specification, for example).
It is really amazing how long institutions like ISO need to come up with standards - especially for a spec like WMS, which has been around for years, which is widely used and has proved to be useful in hundreds of cases.
RSS Feed
1. January 2006 um 18:24
It is important to mention, that only version 1.3 becomes a standard. Not every company will use this version in their products. Intergraph for example will probably keep version 1.1.1, since among other things 1.3 does not support Styled Layer Descriptors (SLD). That’s interesting, isn’t it? Intergraph - as a principal member of the OGC - is not going to use the official WMS standard.
12. January 2006 um 11:17
There is a comment on this post in the OGC Newsletter for January 2006:
“OGC staff responds: OGC has worked with ISO for many years. The OGC members agreed to release WMS to ISO to be approved as an ISO standard. The OGC and ISO had a joint edit team that worked on WMS resulting in IS19128:2005 which is identical to WMS 1.3. Each organization has its own vision and process. While we understand that some documents seem to take quite a while to be approved, we also believe that input from ISO to OGC and from OGC to ISO has been most valuable in creating the best standards possible.”
6. February 2006 um 14:04
A question with NO answer: what has changed between WMS 1.1.1 and 1.3?
Most people that have already implemented this spec just want to know what they have to change to implement the new version. At least with a corrigendum you know what paragraph changed and generally where a change occurred (similar issue is going to be discussed in the 19115 Technical Corrigendum …).
Changes described somewhere:
1)
In WMS 1.1.1, there were “stubs” for SLD in the specification text and schema. The SLD spec defined what to do with those stubs.
In WMS 1.3, those stubs have been removed, and now it is the job of the SLD spec to normatively reference and extend the WMS specification.
The forward dependence of WMS on SLD was removed during the WMS ISO 19128 standardization process (source: http://lists.eogeo.org/pipermail/wms-dev/2005-January/000691.html)
2)
This typing issue is a problem with the WMS 1.1.1 specification. The specification ridiculously specifies a mime type other than text/xml for the returned XML content, so unaware applications receiving the content treat it as an unknown content type. Your programs can work around this, but web browsers typically don’t. The problem is expected be corrected in the WMS 1.3 specification (source: http://www.codeproject.com/csharp/WMSOverviewAll.asp)
3)
Differencies in CRS –> In WMS 1.3.0, this is indicated by the line within a Layer definition in the Capabilities XML, which becomes
&CRS=CRS:84&BBOX=minLongitude,minLatitude,maxLongitude,maxLatitude in the GetMap query to the server. In WMS 1.1.1, the syntax is somewhat different, becoming
&SRS=EPSG:4326&BBOX=minLongitude,minLatitude,maxLongitude,maxLatitude
(source: http://svs.gsfc.nasa.gov/documents/arch_6.html)
and 4)
The “vocabulary” attribute was introduced in WMS 1.3.0 and is not available in WMS 1.1.1 (source: http://svs.gsfc.nasa.gov/documents/arch_7.html)