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

Re: VTD-XML an open-source, high-performance and non-extractiv

• To: Michael Champion <michaelc.champion@g...>
• Subject: Re: VTD-XML an open-source, high-performance and non-extractiveXML processing API
• From: Elliotte Harold <elharo@m...>
• Date: Tue, 18 Oct 2005 15:05:12 -0400
• Cc: XML Developers List <xml-dev@l...>
• In-reply-to: <e3a5cb2c0510181116v47d63931kb46f7eea8fb16dcd@m...>
• References: <bbe40a480510171950m6fb4db02u7d913de27e936d14@m...> <4354C0AA.2020502@m...> <e3a5cb2c0510181001i3f04e82fkb0a0e45009360935@m...> <43552D7F.7060403@m...> <e3a5cb2c0510181116v47d63931kb46f7eea8fb16dcd@m...>
• User-agent: Thunderbird 1.4 (Macintosh/20050908)

Michael Champion wrote:

> I think the argument is that -- unlike Binary XML -- VTD *is* XML,
> plus a little hint to a downstream parser on where the markup
> boundaries are. Those downstream processes (on the same machine or
> different, whatever can be made to work) can use the hint or ignore
> it, whatever suits their needs.

I'm not willing to give up well-formedness checking at application 
boundaries, and I'm afraid a lot of the Eviscerated XML Interchange 
proposals do exactly that.

What would be interesting is if it were possible to conclusively verify 
the well-formedness of an XML document using its VTD in a much faster 
way than just parsing the XML itself. That is, could one verify that the 
VTD could only match a well-formed XML document, and then verify that 
the VTD indeed does match the XML document it's bundled with? and could 
one do this more quickly than one could parse the XML document itself? 
i.e. could the VTD hint the verification process enough that checking 
well-formed documents becomes noticeably faster while malformed 
documents are still detected? I don't know the answer to that question; 
but if it were answered in the affirmative that might be really useful.

-- 
Elliotte Rusty Harold  elharo@m...
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

• Follow-Ups:
  • Re: VTD-XML an open-source, high-performance and non-extractive XML processing API
    • From: Michael Champion <michaelc.champion@g...>

• References:
  • VTD-XML an open-source, high-performance and non-extractive XML processing API
    • From: Harry Xu <harry.hxu@g...>
  • Re: VTD-XML an open-source, high-performance and non-extractiveXML processing API
    • From: Elliotte Harold <elharo@m...>
  • Re: VTD-XML an open-source, high-performance and non-extractive XML processing API
    • From: Michael Champion <michaelc.champion@g...>
  • Re: VTD-XML an open-source, high-performance and non-extractiveXML processing API
    • From: Elliotte Harold <elharo@m...>
  • Re: VTD-XML an open-source, high-performance and non-extractive XML processing API
    • From: Michael Champion <michaelc.champion@g...>

• Prev by Date: RE: DTDs still widely used ? was RE: Namespaces A Mess?
• Next by Date: XPath selectNodes() returns empty List
• Previous by thread: Re: VTD-XML an open-source, high-performance and non-extractive XML processing API
• Next by thread: Re: VTD-XML an open-source, high-performance and non-extractive XML processing API
• Index(es):
  • Date
  • Thread