XML processing experiments

James Clark jjc at jclark.com
Sat Nov 8 12:22:47 GMT 1997

Tim Bray wrote:
> At 06:11 PM 07/11/97 +0100, Jarle Stabell wrote:
> >Ok. My current design will first return PCData="x", then entity ref="foo",
> >and (if the client want entities expanded: PCData="a" followed by
> >EmptyElement="b" and then PCData="c".)
> >ie it may return two consecutive PCData's, with perhaps some
> >EntityExpansionStart and -End signals between them.
> >(Is this design flawed?)
> If "foo" is an *internal* entity, the spec clearly requires your
> parser to expand it for the application.  But letting the app know
> that the ref was encountered is also fine.

I think it's also fine to give the app control over when the parser
performs the expansion.  One reason to do this is that the internal
entity may be defined in an external parameter entity or external DTD
subset.  An app may not want to wait to retrieve this when it could be
continuing to parse the entity in which the reference occurs.


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)

More information about the Xml-dev mailing list