Lists Home |
Date Index |
- From: "Tom Otvos" <email@example.com>
- To: "XML Dev" <firstname.lastname@example.org>
- Date: Tue, 30 Jun 1998 15:53:29 -0400
Hmm, is that the only case where an XML parser might do the "wrong thing" if
it came across a document without a supporting DTD? It seems to me that if
a document comes through without a DTD, and an element contained data not
explicitly escaped, then it would not be unreasonable to assume PCDATA and
try to parse it. However, if a DTD is there to provide more info, then use
it. I am not sure I see how it is significantly different than validating
that an element may, or may not, be a child of another element.
Director of Research, EveryWare Development Inc.
"Try not! Do, or do not. There is no 'try'." - Yoda
From: David G. Durand <email@example.com>
To: XML Dev <firstname.lastname@example.org>; Tom Otvos <email@example.com>
Date: Tuesday, June 30, 1998 4:27 PM
Subject: Re: PCDATA vs CDATA
>Unmarked CDATA in an instance is not parseable without the element
>and without making all XML parsers read all DTDs to determine if CDATA
>might be found in any elements. This violates some of the design goals of
>and thus the decision was taken to eliminate CDATA content models.
>EMPTY has also been effectively trashed by XML's willingness to allow
>to represent an element <a> with an EMPTY content model.
>in both cases we pay a price (in convenience for CDATA and expressiveness
>for EMPTY), but we do get a system that will work well on the WWW in ways
>full SGML does not.
> -- David
>David Durand firstname.lastname@example.org| david@dynamicDiagrams.com
>Boston University Computer Science | Dynamic Diagrams
>http://www.cs.bu.edu/students/grads/dgd/ | http://dynamicDiagrams.com/
> | MAPA: mapping for the WWW
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/
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)