Unexpected error messages on CEMTClass in TN-W

[JohannaOtt]

When validating this WFS in the staging instance of the validators I get two errors concerning CEMTClass that I cannot understand when looking at the data:

1. Test ID EID5c4808a6-566d-3b93-a5e5-e6002f4fc8a7 returns: Unexpected result evaluating XPath expression with context node tn-w:CEMTClass:
   ns1:validFrom[@xsi:nil='true'] expected [true] but found [false]

2. Test ID EID6d46ac1b-5490-3b3f-a19a-1487ae31dc22 returns: Unexpected number of {http://inspire.ec.europa.eu/schemas/tn-w/4.0}CEMTClass descendant elements. expected [2] but found [4]

This is an excerpt of the data with all CEMTClass objects contained
CEMTClass.zip

[dperezBM]

Dear @JohannaOtt ,

Thank you for your message. As we commented on issue #622, we have tested your service directly against OGC Validator and the results are the same that we have with the validator.

Maybe you could report this issue directly to the OGC GitHub repository.

Best regards.

[JohannaOtt]

I created https://github.com/opengeospatial/teamengine/issues/482 for it

[JohannaOtt]

opengeospatial/ets-wfs20#206 only covered parts of it. There is opengeospatial/ets-wfs20#223 now as well

[fabiovinci]

Dear @JohannaOtt,
it seems that the relevant OGC issues were closed, so I will close this issue.
Please reopen it if the error persists.

[JohannaOtt]

@fabiovinci Just tested the WFS from the original description in the staging instance (production instance seems not to work and is immediately returning an error) and the errors are remaining.
This is the link to the report.
So seems like the changes in the OGC Validator did not solve them. Not sure if that is something that now needs to be addressed in the INSPIRE validator or if it needs to be re-directed to the OGC Validator team.
Unfortunately, I cannot re-open the issue myself.

[fabiovinci]

Dear @JohannaOtt,

the INSPIRE Validator should use the latest version of the OGC Validator, we will test the service in production and compare results.

[fabiovinci]

Dear @JohannaOtt,

I validated your service with the production instance (see the report) and directly with the OGC Validator (Test Session Results.zip) and the results are the same.

The fix for the OGC issue 223 is assigned to milestone 1.39, but the one included in the Official OGC Validator is 1.38.

The correct implementation of the fix of your issue could be tested in the Beta OGC Validator which implements the 1.40 version of the WFS2.0 specification.

[JohannaOtt]

@fabiovinci I agree that the errors are not occurring any longer in the beta version of the OGC validator, so this issue can be closed IMO.