[
Lists Home |
Date Index |
Thread Index
]
On 10/18/05, Elliotte Harold <elharo@metalab.unc.edu> wrote:
> I don't see that as the use case at all. I certainly wouldn't support
> passing VTD between different processes, systems, or organizations; any
> more than I would suggest passing a DOM or a SAX event stream. The
> proper serialization for XML is XML, nothing more, nothing less.
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.
In my mind the question isn't what is "proper" but what is the least
improper given the nasty constraints and realistic alternatives. In
a world where Binary XML is proliferating, I'd think you'd see VTD as
one of the less evil alternatives :-)
|
