[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XPath and XPattern (was Re: More on tamingSAX)

• To: lists@j...
• Subject: Re: XPath and XPattern (was Re: More on tamingSAX)
• From: Uche Ogbuji <uche.ogbuji@f...>
• Date: Fri, 24 Dec 2004 00:29:16 -0700
• Cc: David Megginson <david.megginson@g...>,xml-dev@l...
• In-reply-to: <41CBC315.3020208@j...>
• Organization: Fourthought, Inc.
• References: <E1ChXnb-0004PJ-00@u...> <41CB29FA.8010201@t...> <75cb920c041223124846b805a9@m...> <1103865539.16585.12.camel@borgia> <41CBC315.3020208@j...>
• User-agent: Mozilla Thunderbird 0.9 (X11/20041127)

Jeff Rafter wrote:

>> I'd say only the parent stack, or shallow but very wide documents become
>> resource hogs.  An extension mechanism could allow implementations to
>> support sibling access, or perhaps that would be a matter of conformance
>> levels (a la DOM or XAPI).
>
>
> Are there a lot of use cases for a streamable but very wide document? 
> I remember a thread here a while ago talking about the actual 
> deployment of wide docs and it wasn't high. Not that I am arguing for 
> preceding or against it-- I am just speculating.


I would ask the opposite question: is there a use case for streaming a 
merely deep document?  I'd think that wide documents are where the 
performance and working set control of streaming is especially 
important.  The recent XML vs. CSV flame-war that I read about in XML 
Deviant sounds like it makes the case pretty well.

Any way, to pick just one drop from the ocean, if I have a large address 
book, I would expect it to be very wide, and I would probably want to 
stream to process one entry at a time.  In that case, I wouldn't want 
systematic preceding axis support (though my application code might 
accumulate interesting values from preceding nodes).

-- 
Uche Ogbuji                                    Fourthought, Inc.
http://uche.ogbuji.net    http://4Suite.org    http://fourthought.com
Use CSS to display XML - http://www.ibm.com/developerworks/edu/x-dw-x-xmlcss-i.html
Full XML Indexes with Gnosis - http://www.xml.com/pub/a/2004/12/08/py-xml.html
Be humble, not imperial (in design) - http://www.adtmag.com/article.asp?id=10286
UBL 1.0 - http://www-106.ibm.com/developerworks/xml/library/x-think28.html
Use Universal Feed Parser to tame RSS - http://www.ibm.com/developerworks/xml/library/x-tipufp.html
Default and error handling in XSLT lookup tables - http://www.ibm.com/developerworks/xml/library/x-tiplook.html
A survey of XML standards - http://www-106.ibm.com/developerworks/xml/library/x-stand4/
The State of Python-XML in 2004 - http://www.xml.com/pub/a/2004/10/13/py-xml.html

• Follow-Ups:
  • Re: XPath and XPattern (was Re: More on tamingSAX)
    • From: Jeff Rafter <lists@j...>

• References:
  • RE: XPath and XPattern (was Re: More on taming SAX)
    • From: "Michael Kay" <mike@s...>
  • Re: XPath and XPattern (was Re: More on tamingSAX)
    • From: Oleg Tkachenko <oleg@t...>
  • Re: XPath and XPattern (was Re: More on taming SAX)
    • From: David Megginson <david.megginson@g...>
  • Re: XPath and XPattern (was Re: More on tamingSAX)
    • From: Uche Ogbuji <Uche.Ogbuji@f...>
  • Re: XPath and XPattern (was Re: More on tamingSAX)
    • From: Jeff Rafter <lists@j...>

• Prev by Date: Re: XPath and XPattern (was Re: More on tamingSAX)
• Next by Date: Re: XPath and XPattern (was Re: More on tamingSAX)
• Previous by thread: Re: XPath and XPattern (was Re: More on tamingSAX)
• Next by thread: Re: XPath and XPattern (was Re: More on tamingSAX)
• Index(es):
  • Date
  • Thread