The text in section 13 paragraph one:
there are many other potential roles, see for example the CI_RoleCode values from [ISO-19115-1].
the reference points to the ISO standards document, which is not freely available; a more useful link to see the codelist would be https://standards.iso.org/iso/19115/resources/Codelists/gml/CI_RoleCode.xml, which shows up in a browser as a readable html page.
the CI_RoleCode list is also referenced in paragraph 1, section 13.1
likewise for DS_AssociationTypeCode referenced in the following sentences, a more useful link is https://standards.iso.org/iso/19115/resources/Codelists/gml/DS_AssociationTypeCode.xml
DS_AssociationTypeCode is also referenced in section 13.2
And they are all available as linked data (one URI per value, conneg enabled) here: http://registry.it.csiro.au/def/isotc211
I stood this up as a temporary measure 3 years ago, pending ISO getting their act together ...
As far as I know they're not available as linked data except from the csiro.au service, but I do think its better to provide a link in the DCAT text that actually lets you look at a list of the terms from a TC211 hosted site (instead of pointing to the pay-walled spec, in which the vocabs are buried and not easy to find). If the csiro.au/isotc211 services are intended to be persistent, I think it would be useful to point people at those as well, even if they're not 'authoritative TC211 resources'.
Maybe we can still keep the bib ref, but add a link to the publicly available code list - e.g.:
there are many other potential roles, see for example the CI_RoleCode values from [ISO-19115-1].
@sjskhalsa the links to https://standards.iso.org/iso/19115/resources/Codelists/gml/CI_RoleCode.xml are the 'release' versions of what's at https://github.com/ISO-TC211/schemas/tree/master/19115/resources/Codelist/gml
@smrgeoinfo Could the stylesheet CodelistDictionary-v32.xsl be modified to show the gml:id values so that the URIs of the individual entries are visible?
My stylesheet suggestion is for ISO to deal with. It does potentially provide visibility for normative URIs for the ISO codes, but still in XML and not 'real' linked data :-) But we should not delay merging #1001 because it could be a looong wait, from my previous experience.
(A few more tweaks to the PR as well.)
I'll put an issue in the ISO XML github on the gml:id
Leave as future work, pending any further discussion/update on https://github.com/ISO-TC211/XML/issues/205
@dr-shorthair , @smrgeoinfo , I wonder whether you have any updates on this issue.
Not me, but @nicholascar may, as he is now helping ISO/TC 211 with linked data services
Noting we are not the only ones unhappy with this situation - see https://github.com/INSPIRE-MIF/helpdesk-validator/issues/479
Most helpful comment
I'll put an issue in the ISO XML github on the gml:id