Lists Home |
Date Index |
- From: "Simon St.Laurent" <email@example.com>
- To: David Brownell <firstname.lastname@example.org>, XML-Dev Mailing list <email@example.com>
- Date: Tue, 29 Jun 1999 19:47:43 -0400
At 01:57 PM 6/28/99 -0700, David Brownell wrote:
>Speaking of parsers, and perhaps committing a brand of sacrilege
>here (almost certainly so from the SGML side of the world) ...
>... what do folk think of using the following XML subset:
> Everything in XML, except the <!DOCTYPE ...> support
> which takes up something like 2/3 of most parsers.
>Clearly that'd be subset for which validation doesn't apply;
>all data integrity would be provided by higher levels.
>BUT -- it'd be a subset that'd work nicely with all conformant
>XML parsers (validating and non), it'd support namespaces and
>all the schema proposals I last heard of, and there should be
>no issue of size for most environments.
I can think of two ways to do this, each of which might be appropriate in a
different situation. (Both could read the same profile of XML with no
problems as well.)
1) A 'parser' that just reads the document and spits out events without
attempting to interpret them. It might be smart enough to identify
document parts (like DOCTYPE, or identifying &entity; as an entity), but
wouldn't check the structure at all. It would just read with no concern
for the structure of what it read.
2) A parser that only read a canonical form of XML, 100% normalized, with
no DOCTYPE information to create entities or specify defaults.
Both are interesting projects. 1 would let higher levels of the app fill
in the gaps, while 2 would be more limiting, though 2 might feel more in
the spirit of XML.
XML: A Primer / Building XML Applications
Inside XML DTDs: Scientific and Technical
Sharing Bandwidth / Cookies
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)