Changes between Version 7 and Version 8 of MapServerOGCCITECompliance
- Timestamp:
- Jan 27, 2009, 2:02:53 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MapServerOGCCITECompliance
v7 v8 4 4 Status: All tests passed. Need to get compliance certificate. 5 5 6 MapServer used to pass 97 required tests.6 !MapServer used to pass 97 required tests. 7 7 8 8 == WFS 1.0.0 == … … 12 12 * not supporting multiple namespaces: see #2484 for more on this issue 13 13 14 MapServer passed 34 of 132 tests.14 !MapServer passed 34 of 132 tests. 15 15 16 There are two main issues. The first one is concerned about a GetFeature request with an invalid format. We need to know in which format we need to send the response. An email will be sent to the list. Also MapServer does not support multiple namespaces. An email has been sent to the list. There are 11 of 17 bugs still opened.16 There are two main issues. The first one is concerned about a GetFeature request with an invalid format. We need to know in which format we need to send the response. An email will be sent to the list. Also !MapServer does not support multiple namespaces. An email has been sent to the list. There are 11 of 17 bugs still opened. 17 17 18 18 All bugs are shown with this query: … … 22 22 Status: Testing completed 23 23 24 MapServer passed 37 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 becauseMapServer does not advertized it in its capabilities document.24 !MapServer passed 37 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. 25 25 26 26 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.