all adopted OGC:WMS DTDs now at schemas.opengeospatial.net/

[tomkralidis]

...for versions 1.0.0, 1.1.0, 1.1.1, and 1.3.0.

We should make sure mapwms.c points to these schemas (trailing
"ows_schemas_location", i.e.:

for 1.0.0:

[ows_schemas_location]/wms/1.0.0/capabilities_1_0_0.dtd

for 1.1.0:

[ows_schemas_location]/wms/1.0.0/capabilities_1_1_0.dtd

[ows_schemas_location]/wms/1.1.0/exception_1_1_0.dtd

for 1.1.1:

[ows_schemas_location]/wms/1.1.1/WMS_MS_Capabilities.dtd
[ows_schemas_location]/wms/1.1.1/WMS_exception_1_1_1.dtd
[ows_schemas_location]/wms/1.1.1/WMS_DescribeLayerResponse.dtd

[dmorissette]

*** Bug 657 has been marked as a duplicate of this bug. ***

[assefa]

lookin into this

[assefa]

 If schema location metadata is not set the defualt is now  
http://schemas.opengeospatial.net

 Changes done fordtd/xsd

 Exceptions
 - wms 1.1.0 exception now points to 
[ows_schemas_location]/wms/1.1.0/exception_1_1_0.dtd

 - wms 1.1.0 exception now points to 
[ows_schemas_location]/wms/1.1.1/exception_1_1_1.dtd

 Capabilities

   - wms < 1.0.7 : [ows_schemas_location]/wms/1.0.0/capabilities_1_0_0.dtd
   - wms < 1.0.8 : [ows_schemas_location]/wms/1.0.7/capabilities_1_0_7.dtd
   - wms 1.1.0 : [ows_schemas_location]/wms/1.1.0/capabilities_1_1_0.dtd
   - wms 1.1.1 : [ows_schemas_location]/wms/1.1.1/capabilities_1_1_1.dtd

 - DescribeFeature 

 wms 1.1.1 : [ows_schemas_location]/wms/1.1.1/WMS_DescribeLayerResponse.dtd

 - SLD

  1.0.0 : [ows_schemas_location]sld/1.0.0/StyledLayerDescriptor.xsd

 


There are some missing dtds at opengis site so I left the current value:

 Exceptions

- wms revisons <= 1.0.1 
http://www.digitalearth.gov/wmt/xml/exception_1_0_1.dtd

 Capabilities

  - wms > 1.0.7 and < 1.1.0 still uses 
http://www.digitalearth.gov/wmt/xml/capabilities_1_0_8.dtd

[dmorissette]

For the record, http://ogc.dmsolutions.ca/ has been updated to contain a copy of
the schemas from http://schemas.opengeospatial.net/. I have also included a
readme for MapServer visitors at http://ogc.dmsolutions.ca/readme.txt

About the last two schemas that are still hardcoded in MapServer:

- http://www.digitalearth.gov/wmt/xml/exception_1_0_1.dtd
Tom: what are we supposed to use for that? The above is what we use for 1.0.7,
but there is no exception schema/dtd for 1.0.0 and 1.0.7 in the OGC repository

- http://www.digitalearth.gov/wmt/xml/capabilities_1_0_8.dtd
I have created bug 1022 for this one.

[tomkralidis]

w.r.t. 1.0.1, 1.0.7, 1.0.8:

Question: should we even be supported non-adopted versions!  Suggest only
*adopted* versions.  Though functionality and logic based on intermediate
non-public versions which may have been developed are valuable, I don't think we
should support at the interface level.  Comments?

[dmorissette]

w.r.t. adopted versions:
- I have dropped 1.0.8 in bug 1022 already
- we do not support 1.0.1 (I'm not sure where the ref to the 1.0.1 DTD comes
from: probably from some 1.0.7 example that I found way back when)
- 1.0.7 has been around for long enough and implemented by enough players that I
think it's worth supporting it. Plus OGC's repository has the WMS 1.0.7 DTD's so
that's a good sign that this is an important version.

The only question remaining is "what DTD/schema to use for WMS 1.0.7
exceptions"? I had a quick look at the OGC 1.0.7 spec document earlier today and
didn't find any ref to any exception schema/DTD. Any idea?

[tomkralidis]

I would say we go with the 1.0.0 Exception case (loose, but still); I'll check
with the OGC wms-dev list

[tomkralidis]

Update: WMS 1.0.7 says to use the OGC "Basic Services Model 0.0.8" document for
definition of exceptions (format is exceptions=SE_XML).

The Basic Services Model says to use the DTD at:

http://www.digitalearth.gov/wmt/xml/exception_1_0_1.dtd

...example is at:

http://www.digitalearth.gov/wmt/xml/exception_1_0_1.xml

Note that this DTD was never added to schemas.opengeospatial.net per se, however
it is identical to the 1.1.0 exception DTD.

Given the dated version, and level of effort to get OGC to publicize these
versions, seeing that MapServer now runs off the ows_schemas_location as the
root of all schemas/DTDs, maybe we can generate 1.0.7 exceptions with the 1.1.0
DTD -- comments?

[dmorissette]

We could use the 1.1.0 DTD (for WMS 1.0.0 and 1.0.7), but others will run into
this issue as well eventually, so getting OGC to publish that 1.0.1 DTD might
not be a bad idea.