The schema location of a wcs 1.0.0 exception is not pointing out to the correct schema

[nsavard]

When an exception is raised from a WCS server 1.0.0, the location of the schema is pointed out to:

​http://schemas.opengis.net/wms/1.1.1/OGC-exception.xsd

instead of the one in the specification document. Notice that I didn't find the schema at the usual place:

​http://schemas.opengis.net/wcs/1.0.0/OGC-exception.xsd

An example of a request that raises an exception is: ​http://dev1.lan.mapgears.com/manwe/cgi-bin/mswcs100_ogc_cite?ReQuEsT=GetCapabilities&VeRsIoN=&SeRvIcE=WCS

[tomkralidis]

I remember helping resolve this, where some of the WCS folks told us to use the WMS exception .xsd because one did not exist for WCS 1.0.0, hence our choice.

Norm: can you check with the CITE folks on what we should do for WCS 1.0 exceptions? If we point to non-existent ​http://schemas.opengis.net/wcs/1.0.0/OGC-exception.xsd, then the XML response will be invalid.

[nsavard]

Norm: can you check with the CITE folks on what we should do for WCS 1.0 exceptions? If we point to non-existent ​http://schemas.opengis.net/wcs/1.0.0/OGC-exception.xsd, then the XML response will be invalid.

Tom: I'll do that.

[nsavard]

More information. The OGC CITE test concerned by this bug is: wcs1-0-0/basic_service_elements/version_numbering_and_negotiation/1

[nsavard]

Replying to tomkralidis:

I remember helping resolve this, where some of the WCS folks told us to use the WMS exception .xsd because one did not exist for WCS 1.0.0, hence our choice.

Norm: can you check with the CITE folks on what we should do for WCS 1.0 exceptions? If we point to non-existent ​http://schemas.opengis.net/wcs/1.0.0/OGC-exception.xsd, then the XML response will be invalid.

I sent the following email to the CITE list.

email content start:

The wcs1-0-0/basic_service_elements/version_numbering_and_negotiation/1 test against our WCS 1.0.0 server outputs an error saying that our service exception report point out to a schema that does not match the one in the specification (Annex A6). There is no WCS exception schema at the usual URL. If we points out our exception report to a non existing schema (says ​http://schemas.opengis.net/wcs/1.0.0/OGC-exception.xsd) then the response will be invalid.

Can someone tell me we where we should point out our exception report to?

email content end

[tomkralidis]

Done in r7331. Norm: can you check and verify?

[nsavard]

Replying to tomkralidis:

Done in r7331. Norm: can you check and verify?

Tom: I'll do.

[nsavard]

Replying to nsavard:

Norm: can you check with the CITE folks on what we should do for WCS 1.0 exceptions? If we point to non-existent ​http://schemas.opengis.net/wcs/1.0.0/OGC-exception.xsd, then the XML response will be invalid.

I sent the following email to the CITE list.

email content start:

The wcs1-0-0/basic_service_elements/version_numbering_and_negotiation/1 test against our WCS 1.0.0 server outputs an error saying that our service exception report point out to a schema that does not match the one in the specification (Annex A6). There is no WCS exception schema at the usual URL. If we points out our exception report to a non existing schema (says ​http://schemas.opengis.net/wcs/1.0.0/OGC-exception.xsd) then the response will be invalid.

Can someone tell me we where we should point out our exception report to?

email content end

Answer to this email is:

email content start: All,

The WCS 1.0.0 OGC-exception.xsd has now been posted to the schemas repository. It is available at

​http://schemas.opengis.net/wcs/1.0.0/OGC-exception.xsd

Thank you catching the error.

kevin

email content end

[tomkralidis]

FYI added exception in msautotest in r7334.

[nsavard]

Replying to nsavard:

Replying to tomkralidis:

Done in r7331. Norm: can you check and verify?

Tom: I'll do.

Tom: I checked. It seems there is another problem than the one you fixed because I still see the wrong dtd in the exception report. I used the URL in the ticket description to test (An example of a request that raises an exception).

[tomkralidis]

Norm: per #2475, I think this related to the fix in mapwms.c. Can you test again against latest trunk? Should work now.

[nsavard]

Replying to tomkralidis:

Norm: per #2475, I think this related to the fix in mapwms.c. Can you test again against latest trunk? Should work now.

You're right. This is fixed.