RFC 4151: The 'tag' URI Scheme
In plain English — editorial summary, not part of the RFC
This document describes the "tag" Uniform Resource Identifier (URI) scheme. Tag URIs (also known as "tags") are designed to be unique across space and time while being tractable to humans. They are distinct from most other URIs in that they have no authoritative resolution mechanism. A tag may be used purely as an entity identifier. Furthermore, using tags has some advantages over the common practice of using "http" URIs as identifiers for non-HTTP-accessible resources. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4151
- Published
- October 2005
- Authors
- T. Kindberg; S. Hawke
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4156The wais URI SchemeCurrent
August 2005
- RFC 4157The prospero URI SchemeCurrent
August 2005
- RFC 4095Attaching Meaning to Solicitation Class KeywordsCurrent
May 2005
- RFC 4078The TV-Anytime Content Reference Identifier (CRID)Current
May 2005
- RFC 4246International Standard Audiovisual Number (ISAN) URN DefinitionCurrent
February 2006
- RFC 4248The telnet URI SchemeCurrent
October 2005
- RFC 4266The gopher URI SchemeCurrent
November 2005
- RFC 4002IANA Registration for Enumservice 'web' and 'ft'Updated
February 2005
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?