- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 07 Sep 2009 14:34:08 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7529
Summary: [XQuery] General comparison argument conversion with
xs:untypedAtomic and xs:NOTATION
Product: XPath / XQuery / XSLT
Version: 2nd Edition Recommendation
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: XQuery
AssignedTo: jonathan.robie@redhat.com
ReportedBy: oliver@cbcl.co.uk
QAContact: public-qt-comments@w3.org
The errata XQ.E18 defines argument promotion for untyped atomic values in
general comparisons as follows:
If T is a numeric type or is derived from a numeric type, then V is cast to
xs:double.
If T is xs:dayTimeDuration or is derived from xs:dayTimeDuration, then V is
cast to xs:dayTimeDuration.
If T is xs:yearMonthDuration or is derived from xs:yearMonthDuration, then V is
cast to xs:yearMonthDuration.
In all other cases, V is cast to the primitive base type of T.
This definition is a bit wooly when it comes to comparing an xs:untypedAtomic
value with an xs:NOTATION value.
xs:NOTATION is clearly the primitive base type of xs:NOTATION. Should this
raise a type error, or should a value be created with the abstract type
xs:NOTATION for purposes of the comparison?
Nowhere in the specification is it defined what it means to cast to an abstract
type, this issue is carefully avoided every time a cast is used otherwise.
This bug also affects XPath 2.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 7 September 2009 14:34:17 UTC