- From: <bugzilla@jessica.w3.org>
- Date: Mon, 05 Oct 2015 10:29:41 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=4378 --- Comment #23 from Michael Kay <mike@saxonica.com> --- We could introduce the idea of a binding to the context item having static scope, but there's no such concept in the current spec. All the prose talks of it being bound dynamically, reflecting the XSLT 1.0 history. I think that making it a static error would be a fairly disruptive change, both in terms of the effect on the spec, and in terms of backwards compatibility. Making XPDY0002 into a type error is a much "gentler" change, because it's a very small change to the spec, and because implementations have more discretion, so they can make their own choices about how to manage the backwards compatibility issue. In addition it works much better for XPath, where it's the host language that knows whether or not a context item is defined for the XPath expression. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 5 October 2015 10:29:45 UTC