Cart
[Home] [By Thread] [By Date] [Recent Entries]
David Brownell writes:
> 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 ...
Granted -- my suggestion was just to skip all internal entities for
consistency.
<warning target="everyone" level="severe">
I am not willing to let this issue hold up SAX2, because I do not
believe that it is important enough (a minor point for an optional
add-on handler that few sane users should care about).
</warning>
That means that when SAX2/Java goes to final (there'll be at least one
more beta first), it may have a broken LexicalHandler or even no
LexicalHandler if necessary. It may also be that the optional
handlers simply don't get bundled in the main SAX2 distribution.
> so some other rename would be needed to address such issues.
> {start,end}ContentEntity maybe?
Obviously, there are a few people who feel strongly. Maybe we should
spin off the optional handlers as a separate distribution and put
someone else in charge of it. Any volunteers?
All the best,
David
--
David Megginson david@m...
http://www.megginson.com/
***************************************************************************
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
***************************************************************************
|
