CurrentBEST CURRENT PRACTICEIETF streamBCP190

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 substructure in URIs is often problematic. This document provides guidance on the specification of URI substructure in standards. This document obsoletes RFC 7320 and updates RFC 3986.

Document record

Document ID
RFC8820
Published
June 2020
Authors
M. Nottingham
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
Pages
8
Also known as
BCP190
Obsoletes:
RFC 7320
Updates:
RFC 3986

Topics

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/8820-uri-design-and-ownership