3704 2006-09-12 16:53:37 +0000 [XQuery] xml:space attributes 2007-02-25 23:51:10 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 1.0 Candidate Recommendation PC Windows XP CLOSED FIXED P2 normal --- 1 andrew.eisenberg chamberl mike public-qt-comments oldest_to_newest 11621 0 andrew.eisenberg 2006-09-12 16:53:37 +0000 In http://www.w3.org/Bugs/Public/show_bug.cgi?id=3636, Michael Kay raises the following issue: "However, I think that there's a wider question about whether XQuery and XSLT ought to allow the construction of a result tree containing the attribute xml:space="strip", given that it is "erroneous" XML." 11641 1 frans.englich 2006-09-13 10:50:35 +0000 This was discussed on w3c-xsl-query@w3.org: http://lists.w3.org/Archives/Member/w3c-xsl-query/2006Aug/0024.html (A general positiveness towards making it an error to specify an invalid value.) 11687 2 chamberl 2006-09-14 00:51:53 +0000 On June 13, 2006, the Query Working Group decided that an implementation MAY raise a dynamic error [XPDY0092] if a constructed attribute named xml:space has a value other than "preserve" or "default". This change will be reflected in the next version of the XQuery specification. Don Chamberlin (for the Query Working Group) 11714 3 mike 2006-09-14 07:59:26 +0000 I'm not sure why you put the error in the XPath space rather than the XQuery space? 11717 4 frans.englich 2006-09-14 11:59:06 +0000 Why is it "MAY"? This breaks interoperability since a query that runs fine on one implementation can break on another. It neither gives reliability to the user -- she can't trust that her xml:space attributes are verified. 11718 5 chamberl 2006-09-14 16:28:50 +0000 Replying to Michael Kay: Sorry, the correct error code is XQDY0092. It's correct in the XQuery document. Regards, Don Chamberlin 11804 6 andrew.eisenberg 2006-09-15 19:17:37 +0000 (In reply to comment #4) > Why is it "MAY"? We cosidered both the XML Recommendation and the practice of current implementations. The XML Recommendation, in section 2.10, White Space Handling, says in part: "This specification does not give meaning to any value of xml:space other than "default" and "preserve". It is an error for other values to be specified; the XML processor MAY report the error or MAY recover by ignoring the attribute specification or by reporting the (erroneous) value to the application. Applications may ignore or reject erroneous values." Also, when we discussed this, some members said that their products raise an error, and others said that they process it without difficulty. Finally, we noted that our Data Model does not prohibit values other than "default" and "preserve" for xml:space attributes. 11819 7 frans.englich 2006-09-18 11:10:36 +0000 Andrew, thanks for the summary. However, I'm not sure I would agree with the reasonings; for example, that invalid xml:space attributes works in some circumstances, doesn't necessarily mean it is a good idea to sometimes allow it. Nevertheless, I accept the resolution. 14164 8 jim.melton 2007-02-25 23:51:10 +0000 Closing bug because commenter has not objected to the resolution posted and more than two weeks have passed.