- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Tue, 17 Jul 2007 11:07:27 +0200
- To: Johannes Koch <johannes.koch@fit.fraunhofer.de>
- CC: public-wai-ert@w3.org
Hi Johannes, Johannes Koch wrote: > > Hi group, > > I identified an issue with XMLContent: the content character stream may > contain entity references (e.g. ), which can only be dereferenced > with a document type definition (internal or external). > > When we split the content into parts (preceeding the DoctypeDecl, the > DoctypeDecl itself, and following the DoctypeDecl) and use an XMLLiteral > for the part following the DoctypeDecl, the entity references cannot be > dereferenced any more. The RDF/XML serialization then is not well-formed. > > So we can only use XMLContent for XML content that does not contain > entity references. Or the ampersands need to be escaped in the XMLContent, and unescaped back when putting the pieces of the XML document together again. So " " would be temporarily recorded as "&nbsp;" within the HTTP-in-RDF code, and tools will decoded back and forth as needed. What do you think of this approach? Regards, Shadi -- Shadi Abou-Zahra Web Accessibility Specialist for Europe | Chair & Staff Contact for the Evaluation and Repair Tools WG | World Wide Web Consortium (W3C) http://www.w3.org/ | Web Accessibility Initiative (WAI), http://www.w3.org/WAI/ | WAI-TIES Project, http://www.w3.org/WAI/TIES/ | Evaluation and Repair Tools WG, http://www.w3.org/WAI/ER/ | 2004, Route des Lucioles - 06560, Sophia-Antipolis - France | Voice: +33(0)4 92 38 50 64 Fax: +33(0)4 92 38 78 22 |
Received on Tuesday, 17 July 2007 09:10:40 UTC