XOM API for Processing XML with Java

[Elliotte Rusty Harold <elharo AT metalab.unc.edu>]

At 4:39 PM -0500 11/12/03, John Cowan wrote:


> The reason to split the XPointer from the URI was to work around
> the fact that there is still no definition of what a fragment id
> on an XML document means.

Yes, and already there's pushback on using the xpointer attribute 
from Dan Connolly. I think the xpointer attribute is really the wrong 
solution. The right solution is to define a fragment ID for an XML 
document, probably along the lines of http://www.w3.org/TR/xml-fragid/
And I think there's at least a 50/50 chance this is what's going to 
happen. I just don't want XOM caught in the crossfire while all this 
gets sorted out.
--

  Elliotte Rusty Harold
  elharo AT metalab.unc.edu
  Effective XML (Addison-Wesley, 2003)
  http://www.cafeconleche.org/books/effectivexml
  http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA