Lists Home |
Date Index |
- From: "Bill la Forge" <email@example.com>
- To: "Kay Michael" <Michael.Kay@icl.com>, "XML Developers' List" <firstname.lastname@example.org>
- Date: Mon, 22 Mar 1999 11:35:54 -0500
From: Kay Michael <Michael.Kay@icl.com>
>It seems we are trying to provide two views of a document, the reader's view
>and the writer's view. The reader's view needs to present roughly what's in
>SAX1. The writer's view arguably should preserve all the arbitrary choices
>made by the document author, including whether to use CDATA or entity
>references or character references, where to put the line breaks, whether to
>use empty element syntax, where to put optional spaces, what kind of quotes
>to use round attributes, etc, etc. If we are retaining any of this for the
>benefit of people who want to edit the document, then logically we should
>retain all of it.
Beautiful. I think you have identified two distinct modes of operation. I think this
applies to namespaces as well. A reader has no need for the original prefix
and namespace processing should remove all the xmlns attributes, while a writter
may wish to preserve the information.
Perhaps we should have a writer feature that we can turn on or off, which will
give us two broadly different modes of operation. Other features may be
turned on or off individually, but the default for those features may well depend
on the use of the parser by a reader or a writer.
This also gives us a way to partition events--an interface for a set of events
should not include both reader and writer events.
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)