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: Components.
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.
Standards
|
2003-03-25
|
translations
·
errata
The XPointer element() scheme is intended to be
used with the XPointer Framework [XPtrFrame] to allow basic addressing of XML
elements.
|
|
2003-03-25
|
translations
·
errata
This specification defines the XML Pointer Language (XPointer)
Framework, an extensible system for XML addressing that underlies
additional XPointer scheme specifications. The framework is
intended to be used as a basis for fragment identifiers for any
resource whose Internet media type is one of text/xml,
application/xml,
text/xml-external-parsed-entity, or
application/xml-external-parsed-entity. Other
XML-based media types are also encouraged to use this framework in
defining their own fragment identifier languages.
|
|
2003-03-25
|
translations
·
errata
The XPointer xmlns() scheme is intended to be used
with the XPointer Framework [XPtrFrame] to allow correct interpretation
of namespace prefixes in pointers, for instance,
namespace-qualified scheme names and namespace-qualified element or
attribute names appearing within scheme data.
|
Group Notes
|
2003-09-12
|
A URI reference may include an optional fragment identifier that
consists of additional reference information to be interpreted by
the user agent after the URI has been successfully retrieved. The
format and interpretation of fragment identifiers is dependent on
the media type of the retrieval result. The XML media type can
therefore specify a fragment identifier syntax that takes advantage
of the XML structure to define ways to point into an XML resource.
This document recommends the adoption of a specific fragment
identifier syntax for use with XML resources.
|
|
1999-02-24
|
This document is a liaison statement from XML Linking Working
Group to the XML Information Set working group. Because the
XPointer specification under development in the XML Linking WG must
refer to structural parts of XML documents, the structure it
addresses must be explicit. Document structure specifications such
as DOM and the XML Information Set may wish to consider the
XPointer requirements in order to insure interoperability when used
with XPointer and XLink. Thus we have set out in this document,
some constraints we believe XPointer has, for its use with a system
representing XML information structures.
|
|
1999-02-24
|
This document presents requirements for the XPointer language.
XPointer provides ways to directly identify any node, data, or
selection in any XML document by describing its structure and
context. An identified data location is called a "target." The
XPointer specification is particularly meant to enable hyperlinks
to identify any such data, regardless of whether there is (or even
could be) an ID on the target or not. The XPointer specification is
now being developed in the XML-Linking Working Group, building on
Working Drafts developed in the XML Working Group.
Because the XPointer language must refer to structural parts of
XML documents, those structures must be explicit. Document
structure specifications such as DOM and the XML Information Set
may wish to consider the XPointer requirements in order to insure
interoperability when used with XPointer and XLink.
|
Obsolete Specifications
These specifications have either been superseded by others,
or have been abandoned. They remain available for archival
purposes, but are not intended to be used.
Retired
|
2002-12-19
|
The XPointer xpointer() scheme is intended to be
used with the XPointer Framework [XPtrFrame] to provide a high level of
functionality for addressing portions of XML documents. It is based
on XPath [XPath], and adds the ability to
address strings, points, and ranges in accordance with definitions
provided in DOM 2: Range.[DOM2]
|
W3C
