Rule Acronym: PC-R5 states:
Any URI identifiable resource devised in a data specification shall be dereferenceable.
Later there is
Dereferencing means that one can use the URI as an URL to retrieve related information back.
Why not require use of URL in the first place?
Is this done so IRIs are not used to identify resources?
There are suggestions that non-ascii characters should not be used. This is fine since the names of things are in English. Still, I would like to see IRI instead of URI everywhere for multiple reasons.
RDF since 1.1, used heavily throughout the EU Vocabularies, is based on IRIs
If any EU country would like to reuse the style guidelines, it is not reasonable to restrict them to US-ASCII URIs only. For example in Czechia, we use IRIs (with unicode characters) quite extensively, for good reasons.
Thank you, Jakub, for pointing this out.
After discussions, we have concluded that relying on URIs specifically, not IRIs facilitates to a larger degree the interoperability and reuse.
please refer to:
CMC-R3CMC-R4GC-R4
Rule Acronym: PC-R5 states:
Any URI identifiable resource devised in a data specification shall be dereferenceable.
Later there isDereferencing means that one can use the URI as an URL to retrieve related information back.
Why not require use of URL in the first place? Is this done so IRIs are not used to identify resources?