- From: Peter Sorotokin <psorotok@adobe.com>
- Date: Sat, 15 Jan 2005 22:22:49 -0800
- To: Bjoern Hoehrmann <derhoermi@gmx.net>, www-svg@w3.org
Bjoern, Thank you for the feedback! I do not quite understand your point here, so let me try to clarify. Aren't we simply bound by general XML rules (that entity reference is always expanded when attribute value is obtained)? If entity reference is not expanded by parser (or inserted dynamically through DOM), it is treated simply as a text node. Perhaps there is something special about XBL that it must be clarified for XBL (as opposed to any other XML dialect), or perhaps there is any other way to process entity references (that I am not aware of)? Peter At 12:09 PM 1/15/2005 +0100, Bjoern Hoehrmann wrote: >Dear Scalable Vector Graphics Working Group, > > From http://www.w3.org/TR/2004/WD-sXBL-20041122 it is not clear how >sXBL processing is defined if sXBL attributes refer to entities which >the implementation did not attempt to resolve or failed to resolve, >e.g. > > <!DOCTYPE ...> > ... > <xbl:definition ref = '&foo;bar#baz' ...> > ... > >could be processed in a number of ways, the document could be rejected, >the element could be ignored, the attribute could be ignored, the entity >reference could be ignored, the literal reference could be considered >part of the attribute value, and so on. This assumes of course that the >document is well-formed. Please change the draft such that processing is >well-defined if the sXBL fragment refers to unresolved parsed entities. >If the changes cause such sXBL documents to be not interoperable, please >change the draft such that the language elements that cause this lack of >interoperability are discouraged in this context. > >regards. >-- >Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de >Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de >68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Sunday, 16 January 2005 06:24:03 UTC