Lists Home |
Date Index |
- From: Clark Evans <email@example.com>
- To: Marcus Carr <firstname.lastname@example.org>
- Date: Fri, 19 Feb 1999 05:08:59 +0000
Marcus Carr wrote:
> I think you might be applying a meaning to that
> phrase that it doesn't deserve - it doesn't call XML
> a document standard, it uses the term "XML document",
> with document defined in the XML recommendation as:
> "A data object is an XML document if it is well-formed,
> as defined in this specification. A well-formed XML document
> may in addition be valid if it meets certain further constraints."
> This allows you to use the phrases "XML data object" and
> an "XML document" interchangeably.
> This isn't incongruous with stream markup - you just need to
> consider the stream as an XML document. Seriously though, you
> probably wouldn't have the same concerns about "XML data object" ...
My concerns would be even greater. This conjures up in my
mind a Java or C++ object where the complete stream
has to be loaded in memory (or some other random-access
medium) before it can be used. Yes, I know you can have
a multi-threaded implementation so that you can start using
the data object before it finishes reading, etc. However,
given the object model it is *reasonable* for the niave
programmer to ask for something at the _end_ of the stream.
This will cause the call to block untill the stream ends.
If "data stream" processing was treated with *equal*
importance by the W3C committees, then they would see,
in many cases, that this complementary approach is at
least as good as, or in some cases far superior to
an "data object" approach.
Constantly viewing XML as a standard for the description
of "data objects" and not "data streams" is a subtle, and
important bias. It is taking object-orientation too far
and discarding parallel stream processing, and it's related
technologies like SAX and SAXON.
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)