Lists Home |
Date Index |
- From: Peter Jones <firstname.lastname@example.org>
- To: "'email@example.com'" <firstname.lastname@example.org>
- Date: Tue, 25 Aug 1998 14:13:16 +0100
I'm not quite sure if you're agreeing with me here so I'll run through
the process as I see it and you can correct my mistakes:
I have a well-formed document thus:
<text> Blah blah blah &ent1; </text>
&ent1; and &ent2; are by definition parsed entities. But within the
above document there is no indication as to whether the 'contents' of
the entity (the substitution which occurs at parse time) are
Q1) will a non-validating parser flag an error when it encounters either
of the entity references above?
My thinking here is that it should, as parsing means that the
substitution should occur. Am I wrong here?
(ii) in order to avoid the referencing problem I put <!ENTITY....>
declarations in the doc above to provide the 'answers' to the entity
Q2) Will a non-validating parser know how to deal with such <!ENTITY...>
declarations and thus not flag errors on the entity references at parse
time? I.e. will I avoid being forced to use a validating parser to deal
with the document.
WebDev Technical Editor
Wrox Press UK Ltd.
Tel 44 121 706 6826
Fax 44 121 706 2967
> -----Original Message-----
> From: Henry S. Thompson [SMTP:email@example.com]
> Sent: Tuesday, August 25, 1998 2:03 PM
> To: Peter Jones
> Subject: RE: Query about doc well-formedness
> Ah, I see a source of your confusion. PARSED entity doesn't
> necessarily mean VALIDATED, just processed as XML as the processor is
> processing XML in the matrix document, so in the case of a
> well-formedness-checking-only processor, PARSED means well-formed.
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/
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)