[
Lists Home |
Date Index |
Thread Index
]
- From: roddey@us.ibm.com
- To: xml-dev@ic.ac.uk
- Date: Fri, 7 May 1999 17:00:15 -0600
Ok, I'm a little confused about the issues with & in entity literals. Here is
one JC test:
<!DOCTYPE doc [
<!ELEMENT doc (#PCDATA)>
<!ENTITY e "<![CDATA[&foo;]]>">
]>
<doc>&e;</doc>
In this one, there is definitely an ampersand in an entity literal which is not
part of a numeric character reference or an intrinsic character reference. The
spec does not seem to day "No raw & in an entity value unless its a numeric ref
or intrinsic ref, or some other reference that's just left unexpanded", right?
It just says that there can be no ampersands in an entity value unless its part
of a numeric reference or an intrinsic reference.
So am I really supposed to parse all general references in an entity value and
expand character references and intrinsic references and just ignore all others?
Where does it really say that that's what's supposed to happen?
And, while I'm at it, am I losing my mind or is this test from JC really not
correct:
<!DOCTYPE doc [
<!ELEMENT doc (#PCDATA)>
<!ENTITY e "<foo>">
]>
<doc>&e;</doc>
This would expand to:
<doc><foo></doc>
which is obviously wrong since foo has no end tag and is not empty? But its in
the valid\sa bucket.
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)
|