Cart
[Home] [By Thread] [By Date] [Recent Entries]
David Brownell <david-b@p...> writes:
> David Megginson wrote:
> >
> > David Brownell writes:
> >
> > > > How about if we renamed them to start/endExternalEntity and
> > > > forgot altogether about signalling internal entity
> > > > boundaries?
> > >
> > > That'd work for me. (Just saw this note, sorry -- mailer
> > > troubles.)
>
> I forgot to mention: it's not "external" entities that are the
> issue, so some other name would be needed:
>
> <foo> &bar; </foo>
>
> can be sanely reported regardless of whether "bar" is internal or
> external ... so some other rename would be needed to address such
> issues. {start,end}ContentEntity maybe?
In several cases I would prefer internalEntityReference() and
externalEntityReference() event handlers that simply report the
reference but do not resolve the reference, or that call back the
parser to further resolve them.
-- Ken
***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/threads.html
***************************************************************************
|
