- From: Paul Grosso <pgrosso@arbortext.com>
- Date: Mon, 21 Mar 2005 14:04:04 -0500
- To: <public-xml-core-wg@w3.org>
See http://www.w3.org/XML/2005/01/proposed-xinclude-errata for the latest XInclude PE document. See http://www.w3.org/XML/2005/02/xml-f2f-20050303-minutes.htm#xinclude for our f2f minutes on this topic. PEX2 URI or IRI errors handling ------------------------------- At our f2f, we said: We don't expect implementors of XInclude to implement IRI processing, so whatever ends up happening with respect to IRIs isn't really the fault of the XInclude processor. However, we don't want to license such behavior, so we don't want to change our current wording here. [Paul doesn't really understand how to explain this, so someone else will have to write the proposed response here.] Someone needs to draft the proposed response. PEX3 What is an error --------------------- At our f2f, we said (among other things): As far as the case with accept="foo" (mentioned in the comment), the definition of the accept attribute in section 3.1 does not make this an XInclude error of any kind, though it may cause an error in a lower level that might result in a resource error, for example. Those present didn't seem quite satisfied with this resolution, so after some discussion, we decided to revisit this later. PEX5 XML encoding detection in parse="text" ------------------------------------------- See the PE document. PEX11 Reference to RFC 2279 should be RFC 3629 ---------------------------------------------- This is the RFC for UTF-8. We note that 2279 is listed in the normative references but there is actually no reference to it in the document. We will ask François for his opinion of how to handle this. Note that 3629 has a section about the BOM. PEX14 What if encoding is not an EncName? ------------------------------------------- http://lists.w3.org/Archives/Public/www-xml-xinclude-comments/2004Oct/0000 ERH asks "what should I do if the encoding attribute does not satisfy [XML 1.0's EncName] production [81] <http://www.w3.org/TR/REC-xml/#NT-EncName>? PEX15 XPointers with percent escapes: what type of error? ----------------------------------------------------------- http://lists.w3.org/Archives/Public/www-xml-xinclude-comments/2004Oct/0008 ERH says: Since the xpointer attribute is not a URI reference, %-escaping must not appear in the XPointer.... [He suggests clarifying that such would be] a resource error rather than a fatal error.
Received on Monday, 21 March 2005 19:04:07 UTC