BCP 190

RFC 7320

URI Design and Ownership, July 2014

Canonical URL:
https://www.rfc-editor.org/rfc/rfc7320.txt
File formats:
Plain TextPDF
Status:
BEST CURRENT PRACTICE
Updates:
RFC 3986
Author:
M. Nottingham
Stream:
IETF
Source:
appsawg (app)

Cite this RFC: TXT  |  XML

DOI:  http://dx.doi.org/10.17487/RFC7320

Discuss this RFC: Send questions or comments to apps-discuss@ietf.org

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

Section 1.1.1 of RFC 3986 defines URI syntax as "a federated and extensible naming system wherein each scheme's specification may further restrict the syntax and semantics of identifiers using that scheme." In other words, the structure of a URI is defined by its scheme. While it is common for schemes to further delegate their substructure to the URI's owner, publishing independent standards that mandate particular forms of URI substructure is inappropriate, because that essentially usurps ownership. This document further describes this problematic practice and provides some acceptable alternatives for use in standards.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader



Search RFCs
Advanced Search
×