Open dstenger opened 1 year ago
Following up on this is issue, are there any news on implementing this test?
@pvretano @cportele @ghobona
Looking at the abstract tests "A.2.1 Version negotiation" and "A.2.2 Lists version number" in http://docs.opengeospatial.org/is/09-025r2/09-025r2.html#131 it seems that the requirement for the explicit version number 2.0.2 makes this change more of a major change, as servers only supporting version 2.0.0 would fail, right?
Even if more values are allowed in
Any comment would be appreciated.
@StefStr - To conform to WFS 2.0.2 the server must of course accept version 2.0.2 in negotiation. This is how OWS Common version negotiation was designed. Perhaps it would have been better to restrict the version numbers for the purpose of negotiation to the major and minor number and exclude the corrigendum number (that is, just use 2.0), but this is not what OWS Common has specified. A server that wants to support both 2.0.0 and 2.0.2 clients has to accept both version numbers.
Thank you very much @cportele
Understood. Now the Cite tests "only" need to be upgraded to allow for WFS 2.0.2 compliance testing.
Currently, the test suite just support versions WFS 2.0.0 and FES 2.0.0.
Both, WFS and FES shall be updated to version 2.0.2.
Also see https://github.com/opengeospatial/ets-wfs20/issues/224#issuecomment-1311672294.