Uniform Resource Names (URNs)¶
Saint-Andre, P., & Klensin, J. C. (2017). Uniform Resource Names (URNs).
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Scoped Namespace Suffix
- The same convention appears wherever one thing must be named under many scopes: a Kubernetes object addressed as `payments/frontend` versus `staging/frontend` (the namespace segment is the scope), a package referenced as `acme.billing.Invoice` versus `acme.crm.Invoice`, or a resource named under a `urn:` scheme.
This sourceDefines resources named under the urn scheme through a namespace identifier and namespace-specific string.
- The same convention appears wherever one thing must be named under many scopes: a Kubernetes object addressed as `payments/frontend` versus `staging/frontend` (the namespace segment is the scope), a package referenced as `acme.billing.Invoice` versus `acme.crm.Invoice`, or a resource named under a `urn:` scheme.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:de648059cd5d · see in the full table