Lists Home |
Date Index |
Some questions about the XPointer Framework:
1. "An XPointer processor takes as input an XML-encoded resource and a
fragment identifier taken from the URI reference that was used to access
the resource, and produces as output either an identification of some
subresource within that resource based on the pointer extracted from the
fragment identifier, or one or more errors, or both."
What is an "identification of some subresource"? The only resonable output
from an XPointer expression I can think of is an XML fragment.
As I understand it, XLink and XPointer are specs meant to acctually *do*
something (fetch a document or fragment), while XPath is just a syntax for
pointing at things.
2. In "XML Bible" (1999) I read about two other problems surrounding
- In practice, HTTP can't deliver fragments, only whole documents.
- Fragments are not valid XML, sometimes not even well-formed.
I haven't seen much activity in these areas since 1999. No XML aware HTTP
1.2 and XML Fragment Interchange is stuck as a CR. Is SOAP the solution?
3. "...this specification reserves all scheme names for definition in
additional W3C XPointer scheme specifications. However, the scheme
mechanism provides a general framework for extensibility..." Where's the
extensibility? If I can't name my own scheme, then the extensibility is
only in the hands of W3C, right?
4. The comma in production  should be removed, shouldn't it?