W3C home > Mailing lists > Public > public-qt-comments@w3.org > February 2012

[Bug 16089] [QT3] FunctionCall-015

From: <bugzilla@jessica.w3.org>
Date: Thu, 23 Feb 2012 11:13:13 +0000
To: public-qt-comments@w3.org
Message-Id: <E1S0Wbp-0007ZD-Q2@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16089

--- Comment #2 from Tim Mills <tim@cbcl.co.uk> 2012-02-23 11:13:13 UTC ---
(In reply to comment #1)
> I think the reasoning is:
> 
> (a) the equivalent cast expression is an error under
> http://www.w3.org/TR/xpath-30/#id-cast rule 1
> 
> (b) Section 17.1 of F+O states "The semantics of the constructor function "
> xs:TYPE(arg) " are identical to the semantics of " arg cast as xs:TYPE? "
> 
> But I agree, your argument seems reasonable, that the argument to the
> constructor function should be atomized in the same way as for any other
> function.
> 
> So I think we have a spec issue.

I had suspected that, but checked 3.13.2 Cast.

1.  The input expression is evaluated.

2.  If the result contains a node, and the target type is namespace-sensitive,
a type error [err:XPTY0117] is raised.

Since the target type (xs:anyAtomicType) is not namespace-sensitive, the
semantics of the cast are equivalent to the constructor.

-- 
Configure bugmail: https://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 Thursday, 23 February 2012 11:13:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:37 UTC