XOM API for Processing XML with Java

["Greg Saunders" <saundersgreg AT hotmail.com>]

Thanks again for the clarification.

On a related note: though I didn't see it listed in "XOM down the road" [1], 
are there any plans to implement the "xpointer()" scheme [2], even though it 
is only a W3C "working draft" and not a "recommendation"?

Regarding XPointer, you mention in your book: "If you need some means of 
pointing into an XML document, I suggest sticking with pure XPath instead."  
(Harold, 2004, p159.) [3]  Is there some way to use XPath with XInclude 
other than the "xpointer()" scheme?  Or how could we use XPath instead of 
XPointer?

Greg.


Great book, by the by.  Clearest explanation of character sets and character 
encoding that I've read so far, for example.

[1] http://www.cafeconleche.org/XOM/futuredirections.xhtml
[2] http://www.w3.org/TR/2002/WD-xptr-xpointer-20021219/
[3] Harold, Elliotte Rusty.  "Effective XML: 50 Specific Ways to Improve 
Your XML."  2004.  Addison-Wesley, Boston.


> From: Elliotte Harold <elharo AT metalab.unc.edu>
> To: Greg Saunders <saundersgreg AT hotmail.com>
> CC: xom-interest AT lists.ibiblio.org
> Subject: Re: [XOM-interest] xpointer
> Date: Mon, 06 Dec 2004 13:11:37 -0500
>
> Here's what I think is happening, though I'm only 90% sure.
>
> Xerces only reports attribute types through the SAX interface that are 
> identified by the DTD, not any other schema. Therefore it does not tell XOM 
> that the id attribute has type ID. Therefore the XPointer support in XOM  
> does not find it.
>
> XOM and XInclude both operate on the infoset. Schema validation produces a 
> post-schema validation infoset which XOM never sees or pays any attention 
> to.
>
> To have your IDs recognized for XInclusion you need to identify with a DTD, 
> not a schema.
>
> --
> Elliotte Rusty Harold  elharo AT metalab.unc.edu
> XML in a Nutshell 3rd Edition Just Published!
> http://www.cafeconleche.org/books/xian3/
> http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim