W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2005

[Bug 1998] Inconsistency wrt module import new text

From: <bugzilla@wiggum.w3.org>
Date: Fri, 30 Sep 2005 03:04:29 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1ELBCH-0007nD-QD@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1998





------- Additional Comments From jmdyck@ibiblio.org  2005-09-30 03:04 -------
(In reply to comment #5)
>
> "Each module import names a target namespace and imports an
> implementation-defined set of modules that have this target namespace."

So if there are two or more modules co-operatively implementing a given target
namespace, you can't portably know that they'll all be imported, so the only
portable course of action is to never have more than one module for a given
target namespace. Which raises the question, why does XQuery allow multi-module
imports anyway? It seems to be a nasty complication with dubious benefit.
Perhaps it should be deferred. Per Bothner suggested this 18 months ago and
didn't get a good answer, in my opinion.
http://lists.w3.org/Archives/Public/public-qt-comments/2004Mar/0013.html

(I can see why you might want multiple *alternative* modules for a namespace,
i.e., each one completely implementing a given interface, but that's a different
matter. For that, you'd want assurance from the spec that exactly *one* of those
modules would be imported.)
Received on Friday, 30 September 2005 03:04:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:09 UTC