• To: xml-dev@l...
• Subject: Re: Character Entities: An XML Core WG View
• From: Richard Tobin <richard@c...>
• Date: Tue, 5 Nov 2002 12:48:09 GMT
• Cc:
• In-reply-to: <200211050950.JAA04554@p...>
• Organization: HCRC, University of Edinburgh

>But if it were a well fored error you'd be able to put an (internal)
>entity resolver into the pipeline after the WF parse and before the
>XPath data model object was built.

I assume you mean "if it were NOT a well-formedness error"?

This seems to be as much an API issue as a well-formedness one.  What
is the parser going to output to the next stage?  It can't just leave
the entity unexpanded if it's undefined, otherwise what's going to
happen with

  Unix &tm; is a trademark of AT&T;

which would be passed as

  Unix &tm; is a trademark of AT&T;

It would possible to make SAX parsers return a skipped entity event
for undefined entities.  If it's not possible already, you might find
it quicker to get the parser writers to add a flag for this than to
get the spec changed and then get them to implement it!

And of course for experimentation purposes you could use a different
syntax for entity references.

-- Richard

• Follow-Ups:
  • Re: Character Entities: An XML Core WG View
    • From: David Carlisle <davidc@n...>

• References:
  • Re: Character Entities: An XML Core WG View
    • From: David Carlisle <davidc@n...>

• Prev by Date: Re: Character Entities: An XML Core WG View
• Next by Date: RE: RE: RE: XML/RDF
• Previous by thread: Re: Character Entities: An XML Core WG View
• Next by thread: Re: Character Entities: An XML Core WG View
• Index(es):
  • Date
  • Thread