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

[Bug 1848] New: Module Imports

From: <bugzilla@wiggum.w3.org>
Date: Tue, 16 Aug 2005 10:15:17 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1E4yTV-0007OS-Eh@wiggum.w3.org>

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

           Summary: Module Imports
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: minor
          Priority: P2
         Component: XQuery
        AssignedTo: chamberl@almaden.ibm.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


This is a minor technical point which can probably be handled editorially.

We allow a module to do an "import module" on its own namespace.

We say that the effect of this is to import all modules for that namespace. This
includes the importing module.

We say that it's an error if the imported module contains functions or variables
that clash with those defined in the importing module. But when a module imports
itself, there will always be such a clash.

Solution: we should specify that when a module does an "import module" on its
own namespace, it should import all modules for that namespace *other than itself*.

(We have a bit of a problem with module identity: how do we know whether two
URIs identify the same module? But I suggest we leave implementations to sort
that one out.)
Received on Tuesday, 16 August 2005 10:15:20 UTC

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