Closed m2fuhrmann closed 1 year ago
Dear @m2fuhrmann,
thank you for opening the issue.
You are right, the test should pass even if the <gco:DateTime>
element is used.
We will review the related ATS and ETS and notify you when the fix is available in staging.
Dear @m2fuhrmann
A solution has been implemented and now is present in staging environment. Could you please verify and check that now is working as expected? Thanks
Regards
Dear all,
I tested the fix in the staging instance and it works fine.
Select the INSPIRE resource you would like to test
Select the Technical Guidelines version
Select the type of metadata record(s) to be tested
Select the conformance classes to be assessed
3.) upload the XML-file and start the test : 2022-12-01_9e95f21f-4ecf-4682-9a44-e5f7609f6fa0.zip
[x] the browser and version used : Google Chrome Version 110.0.5481.178 (Offizieller Build) (64-Bit)
[x] a screenshot illustrating the problem:
[x] the Test Report (ideally as an attachment to the issue) Test run on 1111 - 02.03.2023 with test suite Conformance Class 2c INSPIRE data sets and data set series metadata for IACS.html.zip
[x] the name of the Test that failed or better: change the
Level of Detail
in the Report by clicking onAll Details
, then scroll down to the failed test and copy the Link on the right-hand side of theAssertion URI
: https://yzyiqfakm4.execute-api.eu-west-1.amazonaws.com/validator/v2/TestRuns/EID974aa279-bf3c-4fcc-8aeb-15c876cc6c29.html?lang=de#EID1d669a53-9c6c-4ced-a3c3-7d3e5be6ce70[x] the Problem: The INSPIRE TG Version 2.0.1 says: TG Requirement C.11: ... The date values shall be expressed using Gregorian calendar and in accordance with [ISO 8601] with either date precision or date and time precision. For date precision the
gmd:CI_Date/gmd:date/gco:Date
element, and for date and time precisiongmd:CI_Date/gmd:date/gco:DateTime
element shall be used.So both variants (Date and DateTime) should be possible. However, the test fails on DateTime.
Could you check that please?
Thanks & regards.