Lists Home |
Date Index |
- From: "Bill la Forge" <email@example.com>
- To: "Paul Prescod" <firstname.lastname@example.org>, <email@example.com>
- Date: Sat, 20 Feb 1999 11:37:04 -0500
From: Paul Prescod <firstname.lastname@example.org>
>I'm not glum. It just is not the mandate of the infoset group to invent
>new purposes for XML. The infoset group is exactly like a supreme court
>interpreting -- but not changing -- the constitution, which in this case
>is the XML specification. The terminology used in the XML specification is
>"document". Therefore that should be the terminology used by the infoset
>As far as a "document focus" being limiting: XML's current popularity in
>all sorts of fields indicates that that is not the case. If you take a
>database and encode it for transmission over a wire then you have a
>document. If you encode a message from one computer to another then you
>also have a document. I don't see this view as in any way limiting XML's
The issue here isn't a matter of inventing new purposes for XML.
The issue is more a matter of recognizing what is happening.
API like SAX and SAXON appear to have broad applicability beyond
applications where everything needs to be read into memory. It isn't just
streams, but very large documents too. The W3C's DOM and XSL are far too
expensive (and even unnecessary!) for the majority of XML's applications.
The real advantage of considering streams is that you are also accommodating
very large documents as well. This is an important consideration for the majority
of the XML community as it exists today.
Things like DOM and XSL and Coins all have their place. But SAX and
SAXON and MDSAX are probably more important. You will observe that
SAXON 4.0 makes it easy to use DOM as needed, providing good
integration between DOM and non-DOM processing. The same is happening
I think the request here is that the W3C simply give some consideration for
large document and stream processing. Not doing so could create real
problems for the entire industry.
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)