Changes between Version 56 and Version 57 of MapServerOGCCITECompliance

Timestamp:

Aug 11, 2009, 11:05:58 AM (15 years ago)

Author:

nsavard

Comment:

--

MapServerOGCCITECompliance

@@ -224 +224 @@
   !MapServer passed 65 out of 69 tests.  Of these four tests that failed, two are the same tests but they used a post request instead of a get request.  
 
-  There are some issues about OGC CITE tests suite.  The first one is that the WCS capabilities document does not validate with XMLSpy.  An email has been sent to the CITE mailing list (http://lists.opengeospatial.org/pipermail/cite-forum/2008-January/000082.html, http://lists.opengeospatial.org/pipermail/cite-forum/2008-February/000098.html) and after some discussion on the wcs-1.2.swg@opengeospatial.org mailing list, it was detected that a XML restriction on the AbstractDescriptionBaseType element was causing this issue.
-
-  There is another issue when testing the version negotiation.  If a GetCapabilities request is sent with no value for the version parameter then the capabilities response have to be the highest version supported.  Since MapServer supports wcs 1.1.1 this is the wcs 1.1.1 capabilities response that is returned and the XML does not validate against the wcs 1.0.0 schema.  (http://lists.opengeospatial.org/pipermail/cite-forum/2008-February/000109.html)
 
    The following table lists the tests that failed and the related ticket number.
@@ -238 +235 @@
 http://trac.osgeo.org/mapserver/query?reporter=%7Ensavard&component=WCS+Server&order=priority
 
-- Note
-  The purpose of this note is to keep a record of what need to be done in order to have a valid capabilities schema since the official Web schema http://schemas.opengis.net/wcs/1.0.0/wcsCapabilities.xsd was not updated with the proposed solution.  The relevant parts of the emails exchange are pasted below since the discussion happened on the wcs-1.2.swg@opengeospatial.org mailing list.  To solve this issue, the second solution proposed by Alexandre Robin was applied on a local copy of the schema.  The XML was validated against this local copy and is valid.  So the capabilities schema was changed as follow.
+- Note 1:
+
+  There are some issues about OGC CITE tests suite.  The first one is that the WCS capabilities document does not validate with XMLSpy.  An email has been sent to the CITE mailing list (http://lists.opengeospatial.org/pipermail/cite-forum/2008-January/000082.html, http://lists.opengeospatial.org/pipermail/cite-forum/2008-February/000098.html) and after some discussion on the wcs-1.2.swg@opengeospatial.org mailing list, it was detected that a XML restriction on the AbstractDescriptionBaseType element was causing this issue.
+
+  The purpose of this note is to keep a record of what need to be done in order to have a valid capabilities schema since the official Web schema http://schemas.opengis.net/wcs/1.0.0/wcsCapabilities.xsd was not updated with the proposed solution.  The relevant parts of the emails exchange are pasted in the appendix A below since the discussion happened on the wcs-1.2.swg@opengeospatial.org mailing list.  To solve this issue, the second solution proposed by Alexandre Robin was applied on a local copy of the schema.  The XML was validated against this local copy and is valid.  So the capabilities schema was changed as follow.
+
+- Note 2:
+
+  There is another issue when testing the version negotiation:  wcs1-0-0:basic_service_elements-version_numbering_and_negotiation-1.  If a GetCapabilities request is sent with no value for the version parameter then the capabilities response have to be the highest version supported.  Since MapServer supports wcs 1.1.1 this is the wcs 1.1.1 capabilities response that is returned and the XML does not validate against the wcs 1.0.0 schema.  Chuck modified the test to pass as long as the wcs server does not return a service exception (http://lists.opengeospatial.org/pipermail/cite-forum/2008-February/000109.html)
+
+- Appendix A
 
 {{{