Closed idevisser closed 4 years ago
Hi,
Language codeList should start with http:// and not with https://
Hi, It is true that only the location of the unsecured url is included in the footnote, but I expect the validator to handle this more flexibly, because many organizations proceed to create and use only secured urls, That is the reason i was asking to accept also the secured ones.
Also in my opinion the test should be relaxed in order to accept also the https url.
Dear @idevisser
We will update the test in order to accept https url and let you know when it is ready.
Regards
Dear @idevisser
The test now accepts https urls in the CodeList for requirements C.5 and 1.6.
Could you please check it in staging instance and provide us feedback?
Regards
Dear @danielnavarrogeo
thanx, it works like expected
best regards Ine
Dear @idevisser
Thank you very much for your feedback.
We will keep the issue open to tracking it properly.
Regards
TG Requirement C.5: metadata/2.0/req/common/metadata-language-code The language of the provided metadata content shall be given. It shall be encoded using gmd:MD_Metadata/gmd:language/gmd:LanguageCode element pointing to one of the three-letter language codes of the ISO 639-2/B code list19;
test failed; expected behavior to accept also the HTTPS version https://www.loc.gov/standards/iso639-2/
tested in staging environment; http://staging-inspire-validator.eu-west-1.elasticbeanstalk.com/etf-webapp/v2/TestRuns/EID838ceb8e-e878-4533-9b77-fef13e7f1329.html
test xml; TEST_EU_Metadata_Dataset_2019.zip