Re: TR: URN Registration for UIC
[email protected] (Dale R. Worley)
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <[email protected]> |
"John R Levine" <[email protected]> writes: > This looks like it: https://osdm.io/spec/catalog-of-code-lists/ There may be issues with the codes on that page. One, as John points out, is the form "urn:x_zoo:...", which isn't compliant with RFC 8141. However, that is easily remedied by defining a sub-tree of urn:uic, so we can use "urn:uic:x:zoo:...". That is, UIC defines a subtree for proprietary values and manages the provider codes. I see these examples for country and currency codes: urn:iso:std:iso:3166:CH urn:iso:std:iso:4217:CFR ISO URNs are governed by RFC 5141. The RFC gives a detailed BNF with many options. The basic structure is "urn:iso:std:" docidentifier *supplement *docelement [addition] In these cases, docidentifier identifies the relevant ISO standard and is either "iso:3166" or "iso:4217". But for these URNs, some ISO authority must have defined "CH" and "CFR" as valid "addition" for these URNs. Arbitrary codes can't be "supplement" or "docelement". Dale