The XML Linking Working Group has completed its work and is no longer active. The XML Activity Statement discusses the W3C's work on XML as a whole; the XML Linking Working Group's final charter covers its last set of work on XML Linking and XPointer in more detail. Responsibility for maintenance of documents issued by the WG rests with the XML Core Working Group in the first instance.
A public registry for XPointer schemes is available.
Check the Implementation Chart.
XML Linking and XML Base reached Recommendation status on June 27th
Introduction :
The XML Linking Language [XLink] defines Extensible Markup Language (XML) 1.0 [XML] constructs to describe links between resources. One of the stated requirements on XLink is to support HTML [HTML40] linking constructs in a generic way. The HTML BASE element is one such construct which the XLink Working Group has considered. BASE allows authors to explicitly specify a document's base URI for the purpose of resolving relative URIs in links to external images, applets, form-processing programs, style sheets, and so on.
This document
Abstract:
This document proposes a facility, similar to that of HTML BASE, for defining base URIs for parts of XML documents.
Status of this Document:
This document has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited as a normative reference from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the
Unlike its companions XLink and XML Base, XPointer has retreated from Candidate Recommendation to Last Call Working Draft status.
Daniel Veillard noted that:
"This second Last Call has been made necessary by a change required to XPointer to insure that URI References built using XPointer are context independant. This specific addition is detailed in section 5.2.1 of this XPointer Working Draft."
The problem appears to revolve around namespaces, as the spec now adds:
"For any XPointer part that uses the xpointer scheme, the evaluation context
RSS/XML