This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title
links to the most recent version of a document.
For related introductory information, see: Identifiers.
Completed Work
W3C Recommendations have
been reviewed by W3C Members, by software developers, and by other
W3C groups and interested parties, and are endorsed by the
Director as Web Standards. Learn more about the W3C Recommendation
Track.
Group Notes are not standards and do not
have the same level of W3C endorsement.
Group Notes
|
2010-12-16
|
This document defines a generic, abbreviated syntax for
expressing URIs. This syntax is intended to be used as a common
element by language designers. Target languages include, but are
not limited to, XML languages. The intended audience for this
document is Language designers, not the users of those
Languages.
|
|
2008-12-03
|
The Resource Description Framework RDF
allows users to describe both Web documents and concepts
from the real world—people, organisations, topics, things—in a computer-processable way.
Publishing such descriptions on the Web creates the Semantic Web. URIs (Uniform Resource Identifiers) are very
important, providing both the core of the framework itself and the link between RDF and the Web. This document presents
guidelines for their effective use. It discusses two strategies, called 303
URIs and hash URIs. It gives pointers to several Web sites that
use these solutions, and briefly discusses why several other proposals have
problems.
|
|
2008-11-03
|
translations
For historic reasons, some formats have allowed variants of IRIs that are somewhat less restricted in syntax, for example XML system identifiers and W3C XML Schema anyURIs. This document provides a definition and a name (Legacy Extended IRI or LEIRI) for these variants for easy reference.
|
|
2001-09-21
|
This paper addresses and attempts to clarify two issues
pertaining to URIs, and presents recommendations. Section 1
addresses how URI space is partitioned and the relationship between
URIs, URLs, and URNs. Section 2 describes how URI schemes and URN
namespace ids are registered. Section 3 mentions additional
unresolved issues not considered by this paper and section 4
presents recommendations.
|
|
1999-10-21
|
This document is an informational document and discusses the
requirements posed to URI schemes for identifying resources in
Television (TV) Broadcast environments. The document is the outcome
of discussions on this subject by the W3C TV-Web Interest Group
[TVWebIG, TVWebMail].
Typical use cases are summarized where TV Broadcast URIs are
involved. A distinction is made between Global and Local usage.
Also, a hierarchy of resource types is identified. Requirements
related to the Global usage case are listed.
|
Drafts
Below are draft documents:
other Working Drafts.
Some of these may become Web Standards through the W3C Recommendation Track
process. Others may be published as Group Notes or
become obsolete specifications.
Other Working Drafts
|
2009-04-15
|
This is a sample short description for this specification;
over time we will replace this description with a real one.
|
Resources Developed Outside W3C
The following resources are relevant to this area of work.
RFC 3986
RFC 3986: Uniform Resource Identifier (URI): Generic Syntax defines URIs. Quoting from the RFC: "A Uniform Resource Identifier (URI) is a compact sequence of
characters that identifies an abstract or physical resource. This
specification defines the generic URI syntax and a process for
resolving URI references that might be in relative form, along with
guidelines and security considerations for the use of URIs on the
Internet."
W3C
