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 2671 - Type promotion
Summary: Type promotion
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Last Call drafts
Hardware: All All
: P2 normal
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-01-06 15:05 UTC by Lionel Villard
Modified: 2006-11-09 22:30 UTC (History)
0 users

See Also:


Attachments

Description Lionel Villard 2006-01-06 15:05:41 UTC
In the section 8.5.1, in the Example subsection, the following judgment does NOT
hold:

xdt:untypedAtomic     can be promoted to  xs:double
Comment 1 Jerome Simeon 2006-01-28 17:34:16 UTC
I agree. I don't believe this is just an issue with the example though. The 
following rule in the same section:

<<
xdt:untypedAtomic can be promoted to any type:

-----------------------------------------------------
statEnv |-  xdt:untypedAtomic can be promoted to Type 
>>

Is redundant with the use of the fs:convert-simple-operand in the
normalization of function calls [See Sections 4.1.5 Function Calls]
and [7.1.2 The fs:convert-simple-operand function].
 
As is, I think the 'can be promoted to' rule above is never
called as that fs:convert-simple-operand is applied before. So
we should be able to remove the rule and the example without changing
the semantics. That would make 'can be promoted to' consistent
with the english prose in the language book.

- Jerome
Comment 2 Jerome Simeon 2006-02-14 16:32:24 UTC
The XSLT and XQuery WG have accepted your comments, and the issue will be fixed
by adopting the changes listed in comment #1.

Best regards,
- Jerome