XPointer &schemename;() Scheme
&doctype;-&shortname;-&isodate;
W3C Proposed Recommendation
&day;
&month;
&year;
&W3C-path;&doctype;-&shortname;-&isodate;/
XML
http://www.w3.org/TR/&shortname;/
http://www.w3.org/TR/2002/WD-xptr-xmlns-20020710/
Steven J. DeRose
sderose@acm.org
Ron Daniel Jr.
rdaniel@taxonomystrategies.com
Eve Maler
Sun Microsystems
eve.maler@sun.com
Jonathan Marsh
Microsoft
jmarsh@microsoft.com
&abstract;
This document is a Proposed Recommendation (PR) of the W3C. This document has been produced by the W3C XML Linking Working Group as part of the XML Activity. It is intended to address a subset of the original XPointer requirements, and to serve as a possible part of a recommendation to the IETF for a fragment identifier syntax for the XML Mime types.
W3C Advisory Committee Members are invited to send formal review comments to the W3C Team until 13 December 2002 at team-xptr-review@w3.org. The public is invited to send comments to the public mailing list www-xml-linking-comments@w3.org (archive). After the review the Director will announce the document's disposition. This announcement should not be expected sooner than 14 days after the end of the review.
This document is based upon the XPointer Candidate Recommendation published on 11 September 2001. Feedback received during that review and a lack of a sufficient number of complete implementations led the Working Group to factor the basic functionality specified there into four specifications: the XPointer Framework, the XPointer element() Scheme, the XPointer xmlns() scheme (this specification), and the XPointer xpointer() scheme. This specification subsequently went through an additional Last Call period. The XML Linking Working Group believes that this specification addresses all relevant Last Call and Candidate Recommendation issues, and represents an interoperable subset of the implementations documented in the previous Implementation Report, and thus that a further Candidate Recommendation period is not necessary. Information about more recent implementations of subsets relevant to this specification and the XPointer element() Scheme and XPointer Framework can be found in the new Implementation Report. Other specifications such as XInclude 1.0 already make normative references to this specification, which makes timely progression to Recommendation desirable.
There are patent disclosures and license commitments associated with
this working draft, which may be found on the XPointer IPR Statement page in conformance with W3C policy.
Publication as a Proposed Recommendation does not imply endorsement by the W3C membership. This is still a draft document and may be updated, replaced or made obsolete by other documents at any time. It is inappropriate to cite a W3C Proposed Recommendation as other than a "work in progress." A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR/.
English
Extended Backus-Naur Form (formal grammar)
20020425: Initial draft of the xmlns() portion of the specification.
20020501: Second draft. Added reminder about the xml: namespace.
20020508: Third draft. Trivially updated the prolog to get ready for
publication. The WG voted to publish this draft.
20020511: Fourth draft. Minor editorial fixes.
20020522: Fifth draft. Incorporated editorial changes agreed on in
today's telecon, plus a few items pointed out in private communications.
Introduction
&abstract;
The key words must, must not, required, shall, shall not, should, should not, recommended, may, and optional in this specification are to be interpreted as described in .
The terms pointer part, scheme, XPointer processor, and namespace binding context are used in this specification as defined in the XPointer Framework specification.
The formal grammar for the &scheme-phrase; is given using simple Extended Backus-Naur Form (EBNF) notation, as described in the XML Recommendation .
Language and Processing
This section describes the syntax and semantics of the &scheme-phrase; and the behavior of XPointer processors with respect to this scheme.
The scheme name is &schemename;
. The scheme data syntax is as follows; if scheme data in a pointer part with the &scheme-phrase; does not conform to the syntax defined in this section the pointer part does not contribute an entry to the namespace binding context.
xmlns() Scheme Syntax
XmlnsSchemeData
NCName
S? '=' S? EscapedNamespaceName
EscapedNamespaceName
EscapedData*
S is as defined in the XML specification , NCName is as defined in the XML Namespaces specification , and EscapedData is as defined in the XPointer Framework specification .
A pointer part with the &scheme-phrase; declares a namespace prefix (NCName) to be associated with an XML namespace name (EscapedNamespaceName with any circumflex-escaping undone). Each pointer part that uses the &scheme-phrase; contributes a new entry to the namespace binding context. If a pointer part defines a binding for a namespace prefix that already has an entry in the namespace binding context, the new entry overrides the old one.
For example, the following pointer part binds the abc prefix to the http://example.com/ns/abc namespace name:
xmlns(abc=http://example.com/ns/abc)
A pointer part that uses the &scheme-phrase; never identifies a subresource and thus the XPointer processor evaluation always continues with the next pointer part. However, evaluation of the xmlns pointer part has a potential effect on pointer parts to its right.
The XPointer Framework on which this specification is based dictates that the initial namespace binding context prior to evaluation of the first pointer part consists of a single entry: the xml prefix bound to the URI http:/www.w3.org/XML/1998/namespace. Following the rules specified by the Framework, any attempt by a pointer part using the &scheme-phrase; to redefine the xml prefix will result in no change to the namespace binding context. Any attempt to bind a prefix to the namespace name http://www.w3.org/XML/1998/namespace will result in no change to the namespace binding context. Any attempt to define the xmlns prefix will result in no change to the namespace binding context. Any attempt to bind a prefix to the namespace name http://www.w3.org/2000/xmlns/ will result in no change to the namespace binding context.
The prefix used in pointer parts need not match the prefix (or lack of a prefix) actually used in the XML resource into which the pointer part is addressing. For example, assume the following target XML resource:
<customer xmlns="http://example.org/customer">
<name xmlns="http://example.org/personal-info">John Doe</name>
</customer>
Evaluation of a pointer part that refers to element customer will not identify any subresources if the namespace binding context contains no entry that binds a prefix to the namespace name http://example.org/customer. The following two pointer parts allow the xpointer() part to the right to refer to the customer element (as c:customer) and the name element (as p:name):
xmlns(c=http://example.org/customer) xmlns(p=http://example.org/personal-info)
xpointer(/c:customer/p:name)