search

opengeospatial / ets-wfs20

Executable Test Suite for WFS 2.0
Other
9 stars 11 forks source link

Basic WFS getFeaturesByType validation failing - unclear why #262

Closed JohannaOtt closed 10 months ago

JohannaOtt commented 11 months ago

Describe the bug When validating this WFS with the production or the beta instance (both using WFS 2.0 test in version 1.40 currently), there are error messages on the getFeaturesByType test failling that I cannot understand so far grafik It claims that "Attribute 'xlink:href' is not allowed to appear in element 'sd:referenceSpeciesId'." and similar errors for other types. I would not see why it is not allowed to appear there according to the schema.

To Reproduce Steps to reproduce the behavior:

  1. Validate the WFS linked above against the WFS 2.0 validator version 1.40.

Expected behavior I would not expect the getFeaturesByType test to fail

Screenshots provided in description

Additional context Not sure if it is relevant but the ns91 namespace prefix used in the query is not defined in the service. Not sure if this is an internal notation of the validator though. grafik

dstenger commented 11 months ago

Thank you for reporting. We recognized problems with the XLink schema and are already working on it. The issue reported here is most likely related to that.

dstenger commented 11 months ago

I just re-tested your service with https://cite.ogc.org/teamengine/ and the get Features By Type test is successful. We did not change anything on the Production environment. So, I assume that the problem was related to the remote XLink schema. Can you please check if your problem is solved?

JohannaOtt commented 10 months ago

@dstenger I can confirm that the error messages are not occurring any longer when testing the WFS in the production instance.