- From: <bugzilla@jessica.w3.org>
- Date: Fri, 28 Aug 2015 08:32:30 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29094 Bug ID: 29094 Summary: [xslt 3.0] conflict between xsl:accept and xsl:override Product: XPath / XQuery / XSLT Version: Last Call 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 Target Milestone: --- Consider: <xsl:use-package name="Q"> <xsl:accept component="variable" name="v" visibility="hidden"/> <xsl:override> <xsl:variable name="v" select="93.7"/> </xsl:override> </xsl:use-package> The current spec suggests that the xsl:override wins (xsl:accept says "In the absence of a matching xsl:override element ...) and essentially assigns no semantics to the xsl:accept declaration in this case. I think it would be consistent with the decision on bug #26781 to raise an error in the case where xsl:accept names a component explicitly (not by wildcard) and there is an xsl:override for the same component. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 28 August 2015 08:32:33 UTC