This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 3695 - Static typing of value comparisons
Summary: Static typing of value comparisons
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows XP
: P2 minor
Target Milestone: ---
Assignee: Jerome Simeon
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-11 09:18 UTC by Tim Mills
Modified: 2007-01-16 17:52 UTC (History)
0 users

See Also:

Attachments

Description Tim Mills 2006-09-11 09:18:00 UTC 
In:

http://www.w3.org/TR/xquery-semantics/#sec_value_comparisons

"The static semantics for function calls is given in [4.1.5 Function Calls]. The comparison functions all have return type xs:boolean, as specified in [Functions and Operators]."

Since value comparisons can operate on empty sequences, shouldn't ValueOp(Expr1, Expr2) type check to xs:boolean? in the general case?
Comment 1 Jerome Simeon 2006-09-19 00:01:17 UTC 
This is a good catch. The text is not reflecting the current status (probably hasn't for a long time). This should be fixed. I believe the inference rules are consistent with F&O and do not need to be fixed.
- Jerome
Comment 2 Jerome Simeon 2006-09-26 14:04:14 UTC 
Tim,
This bug has been reclassified as editorial.
The XSLT and XML Query working groups have decided to
accept the comment and fix the text to align with the
F&O document.
Best,
- Jerome
On Behalf of the XSLT and XML Query WGs