- From: <bugzilla@jessica.w3.org>
- Date: Sun, 14 Feb 2016 14:57:34 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29456
Bug ID: 29456
Summary: initial-function-100a et seq: param/@as in test
catalog
Product: XPath / XQuery / XSLT
Version: Candidate Recommendation
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: XSLT 3.0 Test Suite
Assignee: abel.online@xs4all.nl
Reporter: mike@saxonica.com
QA Contact: public-qt-comments@w3.org
Target Milestone: ---
In the sequence of tests starting initial-function-100a, we see things like
<param select="'sometoken'" as="xs:token"/>
Now, the semantics of the param/@as attribute are not actually described in the
test catalog documentation, but I would have expected them to follow similar
principles to the XSLT rules. Under those rules the above is an error: the
function conversion rules will not convert an xs:string to an xs:token. If we
want the casting rules to apply, we should say so. However, I think it would be
a lot simpler to write
<param select="xs:token('sometoken')"/>
rather than relying on the test driver to do something as complex as applying
the function conversion rules.
We have 3 choices for the semantics:
(a) the as attribute is merely an assertion about the type
(b) use function conversion rules
(c) use a cast
The last option would not actually work for all existing cases, e.g. where we
have as="xs:string*". I would be inclined to go for (a).
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 14 February 2016 14:57:43 UTC