Re: Attribute values with unresolved entities

At 6:08 PM -0400 4/25/04, Karl Waclawek wrote:

>This looks as if it is OK for a non-validating processor *not* to 
>include replacement
>text of internal entities if the declaration has not been read.

Yes, that's OK. What's not OK is not to tell the user that the entity 
has been skipped. Normally a skipped entity results in a call to 
skippedEntity(), except when the skipped entity is in an attribute 
value. I am not saying the parser must resolve the entity. I am 
saying it should tell the client if it does not.

>In addition, this is how "error" is defined - and it would allow the 
>parsing to continue:

Yes, the parsing can continue, but first the parser should call error 
(not fatalError) and give the client an opportunity to respond to the 
problem somehow.


-- 

   Elliotte Rusty Harold
   [email protected]
   Effective XML (Addison-Wesley, 2003)
   http://www.cafeconleche.org/books/effectivexml
   http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
List: sax-devel, [email protected]
See:  http://www.saxproject.org/
https://lists.sourceforge.net/lists/listinfo/sax-devel