| 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. |
| 218 | | |
| 219 | | 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. |
| 220 | | |
| 221 | | 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) |
| | 217 | - !MapServer Version |
| | 218 | 5.4.2 |
| | 219 | |
| | 220 | - Tests Engine |
| | 221 | http://cite.opengeospatial.org/teamengine/ |
| | 222 | |
| | 223 | - Results summary |
| | 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. |
| | 225 | |
| | 226 | 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. |
| | 227 | |
| | 228 | 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) |
