OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: XML Information Set Requirements, W3C Note 18-February-1999

[ Lists Home | Date Index | Thread Index ]
  • From: <Michael.Orr@Design-Intelligence.com>
  • To: <clark.evans@manhattanproject.com>
  • Date: Fri, 19 Feb 1999 11:33:19 -0800

> -----Original Message-----
> From: Clark Evans [mailto:clark.evans@manhattanproject.com]
> Sent: Thursday, February 18, 1999 9:09 PM
> Subject: Re: XML Information Set Requirements, W3C Note 18-February-1999
> 
(snip)
> 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.

I'd like to understand this better... 

Naive question 1: Ignoring the realities of engaging with the
recommendation process, just focusing on understanding the nature of
your concerns, what types of requirements, modes of thought, etc. would
become more prominent if the objects-over-streams bias were suddenly
removed? For instance, is one aspect of your thinking a desire to chunk
an "XML stream" so that validation can be performed incrementally, while
still wishing the XML rec to govern the overall well-formedness (?) of
the stream as a whole? Or is this totally off base? I'm groping to
understand the point of view you're promoting here... 

Naive question 2: Is there anything to be learned from the DTDs that
have been defined to date for applications that raise stream-ish issues
to one extent or another? I'm thinking of things like ICE for content
syndication, CDF for push channels, CBL and cXML for e-commerce, etc.
Not trying to make any particular point here (and I don't know these
specs in depth) -- it would just seem they must have engaged some of the
questions you're raising and might therefore throw light on the
capabilities, drawbacks, and coping paradigms available with current
approaches. 

Just looking for a better understanding of the issues, 
Mike

----------------------------------------
Michael Orr, CTO, VP R&D
Design Intelligence Inc, Seattle WA USA
http://www.design-intelligence.com
pager:888-688-4609  fax:206-343-7750


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)





 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS