search

agiorguk / gemini

Resources relating to the UK Gemini metadata profile
5 stars 3 forks source link

2020-31 ISO 19139 Code list locations #18

Closed PeterParslow closed 1 week ago

PeterParslow commented 3 years ago

GEMINI examples use https://schemas.isotc211.org/schemas/19139/resources/codelist/gmxCodelists.xml

INSPIRE Metadata TG uses https://standards.iso.org/iso/19139/resources/gmxCodelists.xml, and the INSPIRE Validator checks for that - which results in e.g. being told that you haven’t given a date of publication of the INSPIRE document that you cite in Conformity.

Clause 2.2.9 in UK GEMINI Encoding Guidance (agi.org.uk), and 27 times in Encoding examples across a number of elements

Because this “INSPIRE requirement” is only explicit in footnotes in the INSPIRE TG, and actually overrides a specific requirement, I have raised it to INSPIRE. See ISO 19115 codelist locations · Issue #479 · inspire-eu-validation/community (github.com)

PeterParslow commented 3 years ago

INSPIRE issue moved to https://github.com/INSPIRE-MIF/helpdesk-validator/issues/479, but largely diverted to a different issue!

PeterParslow commented 3 years ago

The resolution on the INSPIRE-MIF validator is to only validate the codeListValue attribute, i.e. to accept INSPIRE Metadata TG Clause 2.1.1 as the requirement:

"Both the value of the codeList attribute (a URL that references a code list definition within a register or a code list catalogue) and the textual content of the ISO 19139 element are purely informative"

i.e. that the use of "shall" in the INSPIRE TG footnotes does not introduce further requirements.

We should fix our examples, and perhaps use that TG requirement text in the general description of code list encoding.

PeterParslow commented 3 years ago

2021-07-01 Noting that the 'codelist' attribute of MD_ScopeCode is an identifier not a URL, we still think it right to change our examples & Clause 2.2.9 to make life easier for our users.

PeterParslow commented 3 years ago

Fixed on Peter's laptop (202107NN)

Clause 2.2.9 on https://www.agi.org.uk/gemini/40-gemini/1048-uk-gemini-encoding-guidance/ had already been fixed

PeterParslow commented 2 years ago

See also https://github.com/INSPIRE-MIF/technical-guidelines/releases/tag/2022.1, announcing a new release of the INSPIRE Metadata TG that fixes this issue at their end. They define this fix as a "breaking change", even though the URLs are stated to be only informative.

PeterParslow commented 9 months ago

In the meantime, https://schemas.isotc211.org/schemas/19139/resources/gmxCodelists.xml has moved to https://[schemas.isotc211.org/schemas/19139/-/resources/codelist/gmxCodelists.xml](https://schemas.isotc211.org/schemas/19139/-/resources/codelist/gmxCodelists.xml) - so the "fix" we agreed in July 2021 would no longer work.

https://[standards.iso.org/iso/19139/resources/gmxCodelists.xml](https://standards.iso.org/iso/19139/resources/gmxCodelists.xml) works.

INSPIRE TG now at https://github.com/INSPIRE-MIF/technical-guidelines/blob/2022.2/metadata/metadata-iso19139/metadata-iso19139.adoc & clear that you can use either.

Move this back to "For review".