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

[Walter Underwood]

At 02:27 PM 2/19/99 -0800, Jeffrey E. Sussna wrote:
>I think this issue needs to be addressed. It may be the case that 
>the stream contains, not one, but many documents, where each 
>information "packet" is a document. Or perhaps the afore-mentioned 
>notion of "document fragment" is introduced, and each packet is a 
>fragment. But it will definitely be necessary to support this kind 
>of processing in some manner. 

"will definitely"? Any stream has to start, and ought to be able
to end gracefully. Why not start and stop once in a while for
resyncronization? A series of document-packets (packuments?)
should work fine.

On the other hand, I'm not sure that XML must be used to solve
every problem. It's beyond me what we gain by incompatibly 
re-implementing RPC, SQL, Java class files, or whatever in XML.
Let's solve some new problems.

If we don't let go of the XML hammer once in a while, everything 
starts to look like a thumb.

wunder

--
Walter R. Underwood
wunder at infoseek.com
wunder at best.com (home)
http://software.infoseek.com/cce/ (my product)
http://www.best.com/~wunder/
1-408-543-6946

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at 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 at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)