2447 2005-11-04 09:08:52 +0000 XPST0008 and XPST0081 used interchangeably 2006-02-14 00:20:28 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XPath 2.0 Candidate Recommendation PC Windows XP CLOSED FIXED P2 normal --- 1 mike chamberl public-qt-comments oldest_to_newest 7026 0 mike 2005-11-04 09:08:52 +0000 Previously raised on internal WG lists by Michael Kay at http://lists.w3.org/Archives/Member/w3c-xsl-query/2005Nov/0000.html and previously by Jonathan Robie at http://lists.w3.org/Archives/Member/w3c-xml-query-wg/2005Oct/0024.html The two error codes XPST0008 and XPST0081 used interchangeably when an expression contains a QName whose prefix has not been declared. There are conflicting statements about which should be used in a particular context. Section 2 Basics makes a general statement that XPST0081 is used for this condition, and there are specific mentions for computed element and attribute constructors, pragmas, and option declarations. However section 3.7.1.2 says that XPST0008 is used for the first two cases. Section 2.2.3 makes a general statement that XPST0008 is used, as does 4.12. There are specific mentions for node tests and direct element and attribute constructors. In XPath, there is the general statement that XPST0081 is used, but all the specific instances use XPST0008. I suggest that we standardise on XPST0081 as it is more specific. 8249 1 chamberl 2006-02-14 00:20:18 +0000 Mike, The working group discussed your comment on Feb 1, 2006 and agreed with your suggestion to consistently use the more specific error code XPST0081. Since you were present at the discussion, I have marked this issue as closed. Don Chamberlin (for the Query Working Group)