[Bug 4080] [F+O] Backwards compatibility appendix

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4080

           Summary: [F+O] Backwards compatibility appendix
           Product: XPath / XQuery / XSLT
           Version: Proposed Recommendation
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators
        AssignedTo: ashok.malhotra@oracle.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


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 ()

Received on Thursday, 14 December 2006 17:21:21 UTC