XOM API for Processing XML with Java

["Michael Kay" <mike AT saxonica.com>]

I've raised a note with the WGs about whether we should relax this
constraint. It's appropriate that a data model constructed by parsing raw
XML, and a data model constructed by XSLT or XQuery should have conjoined
text nodes, but I can't see a strong reason why a data model constructed
programmatically should have to obey this constraint.

Michael Kay
http://www.saxonica.com/ 

> -----Original Message-----
> From: xom-interest-bounces AT lists.ibiblio.org 
> [mailto:xom-interest-bounces AT lists.ibiblio.org] On Behalf Of 
> Elliotte Harold
> Sent: 10 January 2005 19:17
> To: norwoods
> Cc: xom-interest AT lists.ibiblio.org
> Subject: Re: [XOM-interest] RE: XPath support in XOM
> 
> norwoods wrote:
> 
> > if xml does not allow adjacent text nodes and xom only 
> allows correct 
> > xml, shouldn't a xom text node insert operation adjacent to 
> an existing 
> > text node combine the strings into the existing text node?  
> would this 
> > not eliminate the xpath problem?
> 
> It's not XML that doesn't allow adjacent text nodes. It's 
> XPath. At one 
> point early on I had planned to make XOM disallow (or automerge) 
> adjacent text nodes just to avoid this problem. However, I 
> was convinced 
> otherwise. At this point, though, I think I'm sticking to my 
> guns. XPath 
> is defined on a data model that does not allow adjacent text 
> nodes, and 
> to query XOM with XPath we need to account for that.
> 
> -- 
> 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
> _______________________________________________
> XOM-interest mailing list
> XOM-interest AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/xom-interest
>