1247 2005-04-13 15:09:25 +0000 fn:id uses error err:XPTY0004 but it should use err:XPTY0006 2012-03-27 23:33:01 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Functions and Operators 1.0 Last Call drafts PC Windows XP CLOSED FIXED P2 minor --- 1 amassari ashok.malhotra mike public-qt-comments oldest_to_newest 3742 0 amassari 2005-04-13 15:09:25 +0000 In §15.5.2, fn:id reports error err:XPTY0004 "if the context item is not a node"; but the error is defined in the appendix to be "It is a type error if, during the static analysis phase, an expression is found to have a static type that is not appropriate for the context in which the expression occurs, or during the dynamic evaluation phase, the dynamic type of a value does not match a required type as specified by the matching rules in 2.5.4 SequenceType Matching." As other functions (like namespace-uri, name,..) use err:XPTY0006 for the same reason, I think it should be used also here. 3743 1 amassari 2005-04-13 15:16:27 +0000 The same comment applies to fn:idref too 3744 2 mike 2005-04-13 15:26:17 +0000 In fact a decision was made to merge XPTY0004 and XPTY0006 into a single error code, because the only distinction between them was the time at which the error is detected rather than the nature of the error. Unfortunately this decision has not been implemented in the F+O book. Michael Kay 2722 3 ashok.malhotra 2005-06-07 21:59:15 +0000 The joint WGs agreed in the telcon on 6-7-2005 to change the error for "context item is not a node" to an F&O error. As suggested by Jerome, this should be a type error. See (member-only) mail: http://lists.w3.org/Archives/Member/w3c-xsl-query/2005May/0032.html http://lists.w3.org/Archives/Member/w3c-xsl-query/2005May/0035.html Ashok Malhotra 66157 4 mike 2012-03-27 23:33:01 +0000 Changing status from the rarely-used VERIFIED to CLOSED.