URN Syntax
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 8
- Abstract
- Uniform Resource Names (URNs) are intended to serve as persistent, location-independent, resource identifiers. This document sets forward the canonical syntax for URNs. [STANDARDS-TRACK]
- Publication Date
- 1997-05-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC2141- ISSN
2070-1721- Link
- https://doi.org/10.17487/RFC2141
- Author(s)
- Ryan Moats
- Keyword(s)
- URN-SYNTAX, URN
Latest version of IETF RFC 2141
Document Versions — IETF RFC 2141
-
▶ IETF RFC 2141 (1997-05-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 1630 [Active*]
- IETF RFC 1737 [Active*]
- SSCID.15062238 — 1 EXTERNAL
- SSCID.36305224 — T. Berners-Lee, L. Masinter, and M. McCahill, IETF RFC 1738, “Uniform Resource Locators (URL),” 1994. [Online]. Available: https://www.ietf.org/rfc/rfc1738.txt. EXTERNAL
- UNICODE.STD.2.0 — Unicode EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2141.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 2141, URN Syntax. Available at https://doi.org/10.17487/RFC2141
Snippet:
IETF RFC 2141, URN Syntax. Available at https://doi.org/10.17487/RFC2141
HTML (ISO 690 compliant)
Preview:
IETF RFC 2141, URN Syntax. Available at https://doi.org/10.17487/RFC2141
Snippet:
<span class="citation"><cite>IETF RFC 2141</cite>, URN Syntax. Available at <a href="https://doi.org/10.17487/RFC2141" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2141</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc2141">IETF RFC 2141</cite>, URN Syntax <span class="doi">10.17487/RFC2141</span> </li>
Referenced By
- ISO 26429-7:2008 [Active, Reaffirmed]
- ISO 26430-4:2009 [Active]
- IETF RFC 2276 [Active*]
- IETF RFC 2288 [Active*]
- IETF RFC 2396 [Superseded*]
- IETF RFC 2483 [Active*]
- IETF RFC 2518 [Superseded*]
- IETF RFC 2611 [Superseded*]
- IETF RFC 2648 [Active*]
- IETF RFC 2802 [Active*]
- IETF RFC 2915 [Superseded*]
- IETF RFC 3001 [Superseded*]
- IETF RFC 3043 [Active*]
- IETF RFC 3044 [Superseded*]
- IETF RFC 3061 [Active*]
- IETF RFC 3075 [Superseded*]
- IETF RFC 3084 [Active*]
- IETF RFC 3085 [Active*]
- IETF RFC 3120 [Active*]
- IETF RFC 3121 [Active*]
- IETF RFC 3151 [Active*]
- IETF RFC 3187 [Superseded*]
- IETF RFC 3188 [Superseded*]
- IETF RFC 3275 [Active*]
- IETF RFC 3367 [Active*]
- IETF RFC 3402 [Active*]
- IETF RFC 3403 [Active*]
- IETF RFC 3404 [Active*]
- IETF RFC 3405 [Active*]
- IETF RFC 3406 [Superseded*]
- IETF RFC 3553 [Active*]
- IETF RFC 3858 [Active*]
- IETF RFC 3862 [Active*]
- IETF RFC 3863 [Active*]
- IETF RFC 3864 [Active*]
- IETF RFC 3981 [Active*]
- IETF RFC 3986 [Active, Amended*]
- IETF RFC 3987 [Active*]
- IETF RFC 4122 [Superseded*]
- IETF RFC 4235 [Active*]
- IETF RFC 4246 [Active*]
- IETF RFC 4354 [Active*]
- IETF RFC 4395 [Superseded*]
- IETF RFC 4452 [Active*]
- IETF RFC 4480 [Active*]
- IETF RFC 4854 [Active*]
- IETF RFC 5049 [Active*]
- IETF RFC 5119 [Active*]
- IETF RFC 6288 [Active*]
- IETF RFC 6963 [Active*]
- IETF RFC 7254 [Active*]
- IETF RFC 7302 [Superseded*]
- IETF RFC 7462 [Active*]
- IETF RFC 7595 [Active*]
- IETF RFC 7972 [Active*]
- IETF RFC 8141 [Active*]
- SMPTE ST 2001-1:2013 [Superseded]
- SMPTE ST 2001-1:2015 [Active]
- SMPTE ST 2029:2009 [Superseded]
- SMPTE ST 2029:2022 [Active]
- SMPTE ST 2029:2023 [Active]
- SMPTE ST 2067-3:2013 [Superseded]
- SMPTE ST 2067-3:2016 [Superseded]
- SMPTE ST 2071-1:2012 [Superseded]
- SMPTE ST 2071-1:2014 [Superseded]
- SMPTE ST 2071-1:2016 [Active, Stabilized]
- SMPTE ST 395:2014 [Active]
- SMPTE ST 429-7:2006 [Active, Reaffirmed]
- SMPTE ST 430-4:2008 [Active, Amended]
- SMPTE ST 430-4:2008 Am1:2011 [Active]