• To: XML Developers List <xml-dev@l...>
• Subject: Re: Question for updating existing XML file
• From: Michael Champion <mc@x...>
• Date: Tue, 27 Jul 2004 10:36:18 -0400
• In-reply-to: <41062B09.3040900@d...>
• References: <945A2CFE6C33D611A49D0002A59305DB044B4750@SWEC9901> <001901c4739a$00acd0e0$42e16945@d...> <41062B09.3040900@d...>

On Jul 27, 2004, at 6:14 AM, Jonathan Robie wrote:

>>
>>  http://vtd-xml.sf.net
>
> According to the description of VTD given at that URI, "It is a binary 
> format specification, not an API specification.
>
> Did I get that wrong?
>

As I understand it, the Virtual Token Descriptor itself is a binary 
format that describes the structure of a textual XML document.  The VTD 
project has an API that supports incremental update to the binary 
format to point the updated element to a new block of text.  I guess 
that means that the updated text itself would have to be re-serialized 
via the API to make it well-formed XML again, right Jimmy?

I find the VDT stuff an interesting combination of binary and textual 
"XML" (broadly defined, let's not get into that permathread right now) 
tools that may hit a sweet spot between performance and conformance, 
for those who can live with a subset of XML that (at least currently) 
doesn't include entities other than the built-in ones.

• Follow-Ups:
  • Re: Question for updating existing XML file
    • From: Jimmy Zhang <jzhang2004@s...>

• References:
  • Question for updating existing XML file
    • From: "Chen, Andrew ." <ChenA@w...>
  • Re: Question for updating existing XML file
    • From: <jzhang2004@s...>
  • Re: Question for updating existing XML file
    • From: Jonathan Robie <jonathan.robie@d...>

• Prev by Date: RE: rddl questions
• Next by Date: Re: Question for updating existing XML file
• Previous by thread: Re: Question for updating existing XML file
• Next by thread: Re: Question for updating existing XML file
• Index(es):
  • Date
  • Thread