- From: <bugzilla@jessica.w3.org>
- Date: Thu, 09 Sep 2010 18:22:04 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10291 --- Comment #5 from Markos Zaharioudakis <markos_za@yahoo.com> 2010-09-09 18:22:03 --- We all agree there is a problem. I understand that from a user's point of view, throwing an error in a situation like this is not good. But, given the current spec, I don't see how an error can be avoided without any implementation-defined extensions. What is proposed in comment #4 is a modification to the spec, right? In this case, why extend the dynamic context only? Why not do the same for the static context as well? This would allow more query optimizations during compile time. Another possible solution is to provide for public and private schema imports. If a module A imports a schema "publicly", that schema become visible to any other module that imports A. Just a thought .... -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 9 September 2010 18:22:05 UTC