22877 2013-08-04 13:26:00 +0000 [XSLT 3.0] Binding component references in xsl:key definitions 2014-05-15 14:00:35 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Working drafts PC All CLOSED FIXED P2 normal --- 1 mike mike public-qt-comments oldest_to_newest 91620 0 mike 2013-08-04 13:26:00 +0000 The definition of a key can include function calls in its use= attribute, or in predicates within its match= attribute. It can also contain references to global variables and to named templates rules; potentially it can use apply-templates. We therefore need to consider what happens when the functions/templates/variables that it references are overridden in a using package. The scope of keys is local to a package, and a call to the key() function can only appear within the package containing the declaration of the key. Therefore, I think we get the right effect if outward component references from a key definition are always "fixed" to components in the package containing the key declaration, and are never subsequently re-bound. This has the additional merit that the compiler knows the full definition of the key when compiling the package, and can use this knowledge. We need to explain this, with examples, in section 3.6.4. 93803 1 mike 2013-09-25 15:21:36 +0000 Contrary to what is suggested in the bug report, we don't think outward references from the key should be treated as final if the target components are in fact overridden. Keys should be treated as private components that can contain outward references but cannot be overridden or exposed in using packages. 93862 2 mike 2013-09-26 07:56:54 +0000 The change described in comment 1 was accepted and has been applied.