Actually, the changes on the XInclude spec are rather minor. Basically, instead of having the XPointer specified as a fragment identifier, it is handled as a separate attribute.
This is what we had to do to satisfy some rather obscure theoritical problems with the fragment id.
--
Arnaud Le Hors - IBM, XML Standards Strategy Group / W3C AC Rep.



Elliotte Rusty Harold wrote:
At 9:18 AM +1000 11/5/03, Chalker, Dean wrote:
Hi all,

I am investigating implementing XPointer in the existing XInclude feature, and have found org.apache.xerces.impl.xpath.XPath and org.apache.xerces.impl.xs.identify.XPathMatcher.

Before I launch into major code development, I'd appreciate any thought about how (or whether) these class can be extend to provide XPath for XPointer. I guess my major question is how to extend XPath to add the additional functions that XPointer provides.


You probably want to hang tight for a couple of weeks. The W3C working group is preparing a major new working draft of XInclude which will substantially revise how XPointers are handled. If I were you I'd want to see this before beginning a lot of work I might have to throw out.




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to