4080 2006-12-14 17:21:00 +0000 [F+O] Backwards compatibility appendix 2007-02-25 23:43:40 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Functions and Operators 1.0 Proposed Recommendation PC Windows XP CLOSED FIXED P2 minor --- 1 mike ashok.malhotra public-qt-comments oldest_to_newest 13182 0 mike 2006-12-14 17:21:00 +0000 The non-normative backwards compatibility appendix in F+O (Appendix D) lists some incompatibilities in string functions that no longer exist: they were removed during the last call period. Since this appendix is informative only, I suspect there is no objection to us correcting the information during PR. Note also that in most of these cases, the function signature given in the appendix doesn't match that in the body text. I haven't done a complete trawl, but the incorrect statements include: concat(): If compatibility mode is off, an error will occur if ... argument is a number or a boolean. starts-with(): In 1.0, returns false if the first argument is an empty node-set. In 2.0, returns () contains(): In 1.0, returns false if the first argument is an empty node-set. In 2.0, returns () substring-before(): In 1.0, returns "" if the first argument is an empty node-set. In 2.0, returns () substring-after(): In 1.0, returns "" if the first argument is an empty node-set. In 2.0, returns () substring(): In 1.0, returns "" if the first argument is an empty node-set. In 2.0, returns (). normalize-space(): In 1.0, returns "" if the first argument is an empty node-set. In 2.0, returns () 13413 1 ashok.malhotra 2007-01-10 15:44:45 +0000 On the Jan 9, 2007 telcon the WGs decided to accept the suggestions made by Michael Kay and make the editorial changes. 14145 2 jim.melton 2007-02-25 23:43:40 +0000 Closing bug because commenter has not objected to the resolution posted and more than two weeks have passed.