Changes between Version 57 and Version 58 of MapServerOGCCITECompliance


Ignore:
Timestamp:
Aug 11, 2009, 12:41:59 PM (15 years ago)
Author:
nsavard
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapServerOGCCITECompliance

    v57 v58  
    243243- Note 2:
    244244
    245   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)
     245  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 and http://lists.opengeospatial.org/pipermail/cite-forum/2008-August/000134.html)
     246
     247- Note 3:
     248
     249  There is also an issue with one of the test that uses the time parameter in a GetCoverage request.  The test retrieves the "timePositions" parameter instead of
     250the time position.  An email has been sent to the CITE list.
    246251
    247252- Appendix A