- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 20 Sep 2005 11:24:17 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2259 ------- Additional Comments From mike@saxonica.com 2005-09-20 11:24 ------- Looking at this comment from another perspective, I note that the XQueryX specification doesn't ever mention the static context. Is it intended that the translation from XQuery to XQueryX should make any use of the static context? If so, there's a constraint that the resulting XQueryX query must execute in a static context that resembles the original static context in certain unspecified ways. (The relevance here is that to know whether a function is a constructor function, you need to know the in-scope type definitions, and as a result, the XQueryX form of the query becomes intolerant of changes to the in-scope type definitions.) I can't see any other aspects of the static context that influence the translation, so I think it would be better to make the translation entirely context-free. I had a look to see what the translation is supposed to do about the static base URI, and it seems that nothing is said. That's perhaps a subject for a separate discussion. Michael Kay
Received on Tuesday, 20 September 2005 11:25:54 UTC