- From: <bugzilla@jessica.w3.org>
- Date: Thu, 09 Oct 2014 19:16:07 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27012 Bug ID: 27012 Summary: [xslt 3.0] xsl:context-item: apply conversion rules? Product: XPath / XQuery / XSLT Version: Working drafts Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: XSLT 3.0 Assignee: mike@saxonica.com Reporter: mike@saxonica.com QA Contact: public-qt-comments@w3.org Section 10.1.1 (xsl:context-item) makes conflicting statements about whether or not the context item is converted to the required type. First it says: No attempt is made to convert the context item to the required type (using the function conversion rules or otherwise). Later it says: If a context item is supplied (which will automatically be the case if the template is invoked using xsl:apply-templates, xsl:apply-imports, or xsl:next-match) then it will be converted to the required type by applying the function conversion rules; a type error [see ERR XTTE0590] occurs if conversion to the required type is not possible. Both designs are feasible, but I'm inclined to go for the "no conversion" option to avoid complications. For example, if a template matches a node and then atomizes it for processing, what does xsl:next-match do? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 9 October 2014 19:16:12 UTC