- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 08 Sep 2005 15:23:28 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1998 ------- Additional Comments From holstege@mathling.com 2005-09-08 15:23 ------- Yes, I now see this constraint added to modules in general and it appears to have snuck in in some earlier draft, where I missed it. Apologies for not having noticed this until now. I would, nevertheless, very much appreciate knowing when this new rule was agreed to. The last I remember significant discussions of module import semantics was at the August 2004 F2F (the whole module resources vs module renaming discussion). At that time, there was no such rule in the spec, and I see no such rule in the proposal we agreed to at that time. Indeed, I recall as part of the discussion (although this point doesn't seem to be captured in the official minutes) a rejection of this interpretation. This "all modules with that namespace" is a weird and unenforceable constraint anyway and should be dropped, especially if we never explicitly agreed to it.
Received on Thursday, 8 September 2005 15:23:42 UTC