- From: <bugzilla@jessica.w3.org>
- Date: Sun, 04 Aug 2013 13:14:06 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22876
Bug ID: 22876
Summary: [XSLT 3.0] Binding component references from the body
of a template rule
Classification: Unclassified
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 3.6.2.6 describes the process of binding symbolic references (such as
the template name in xsl:call-template) to actual components.
However, the text is written as if all such references appear within
components. In practice, many do not: specific examples (perhaps the only
examples) are references in template rules (which are not components), and
references in the body of xsl:key (which I will consider in a separate bug
entry). Currently these non-components are not copied by use-package in the
same way that components are, which means that if they contain references to
components that get overridden, there is no opportunity to rebind those
references.
Because we can include individual template rules under xsl:override, I think
it's probably simplest if we treat them as components with no symbolic name,
whose visibility is always private (meaning they can only be referenced via the
mode they belong to, assuming the mode is visible). Template rules will
therefore never be the target of a component reference, but they can act as
containers of (outward) component references, and they will be copied into a
using package, with rebinding of their outward component references in the
usual way.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 4 August 2013 13:14:08 UTC