W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2005

[Bug 1826] New: Editorial: op:union/op:intersect defined in F&O, but error handling in XPath 2.0

From: <bugzilla@wiggum.w3.org>
Date: Thu, 28 Jul 2005 16:23:44 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1DyBAe-0000EQ-7F@wiggum.w3.org>

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

           Summary: Editorial: op:union/op:intersect defined in F&O, but
                    error handling in XPath 2.0
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators
        AssignedTo: ashok.malhotra@oracle.com
        ReportedBy: frans.englich@telia.com
         QAContact: public-qt-comments@w3.org


Hello,

This is maybe intentional, but I find it a bit confusing that error handling for
op:union, op:intersect and op:intersect is defined in XPath 2.0, "If an operand
of union, intersect, or except contains an item that is not a node, a type error
is raised [err:XPTY0004].", while their definitions are in F & O "15.3 Equals,
Union, Intersection and Except."

Should the error handling specification be moved from XPath20 to F & O?


Cheers,
Frans
Received on Thursday, 28 July 2005 16:23:46 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:25 UTC