metasystema.org
ObsoletedBEST CURRENT PRACTICEIETF stream

RFC 7320: URI Design and Ownership

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8820.

Current version: RFC 8820 — URI Design and Ownership

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC7320
Published
July 2014
Authors
M. Nottingham
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
art
Pages
9
Also known as
—
Obsoleted by:
RFC 8820
Updates:
RFC 3986

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/7320-uri-design-and-ownership