Changes between Version 53 and Version 54 of MapServerOGCCITECompliance


Ignore:
Timestamp:
Aug 11, 2009, 7:13:13 AM (15 years ago)
Author:
nsavard
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapServerOGCCITECompliance

    v53 v54  
    215215  http://dev1.lan.mapgears.com/manwe/cgi-bin/mswcs100_ogc_cite?&VeRsIoN=1.0.0&SeRvIcE=wcS&ReQuEsT=Getcapabilities
    216216
    217 !MapServer passed 37 out of 69 tests.  This number is not really meaningful though because the updateSequence tests are triggered and !MapServer does not support it.  Also the tests on time dimension are not triggered because !MapServer does not advertized it in its capabilities document. 
    218 
    219 There are a main issue about OGC CITE tests suite.  The WCS capabilities document does not validate with XMLSpy.  An email has been sent  to the mailing list  and we are waiting for an answer on this issue.
    220 
    221 There are seven of thirteen bugs still opened.
    222 
    223 
     217!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 a main issue about OGC CITE tests suite.  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 it was detected that a XML restriction on the AbstractDescriptionBaseType element was causing this issue.
     218
     219There are two of thirteen bugs still opened.
    224220
    225221All bugs are shown with this query:
    … …  
    227223
    228224- Note
    229   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 is not updated with the proposed solution.  There is a mistake in the capabilities schema found on http://schemas.opengis.net/wcs/1.0.0/wcsCapabilities.xsd.  The relevant parts of the emails exchange are pasted below.  To solve this issue, the second solution proposed by Alexandre Robin was applied.  So the capabilities schema was changed as follow.
     225  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.
    230226
    231227{{{