W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2003

RE: multiple modules with the same name

From: Michael Rys <mrys@microsoft.com>
Date: Tue, 6 May 2003 11:24:17 -0700
Message-ID: <5C39F806F9939046B4B1AFE652500A3A0534D9E4@RED-MSG-10.redmond.corp.microsoft.com>
To: "Per Bothner" <per@bothner.com>, <public-qt-comments@w3.org>

Like in the case of XML Schema, the number of actual library files is
inconsequential since they will be presented as one unit for the purpose
of the import. The management of the modules is outside of the XQuery
specification's scope.

The rules are specified as consistency constraints (no two functions can
have conflicting signatures) instead of making limitations on the number
of modules that you can or cannot define.

Best regards

> -----Original Message-----
> From: Per Bothner [mailto:per@bothner.com]
> Sent: Tuesday, May 06, 2003 9:38 AM
> To: public-qt-comments@w3.org
> Subject: multiple modules with the same name
> The May draft is unclear about whether there can be more
> than one library module with the same target namespace.
> The description of ModuleImport implies that the import
> is from *a* library module.  However, the write-up of
> ModuleDecl just says the URI "serves as the target namespace
> of the module."
> It is a lot easier for an implementor if there is at most
> one module for a given URL.  I assume that is the intention,
> but I think it should be made unambiguous.
> --
> 	--Per Bothner
> per@bothner.com   http://per.bothner.com/
Received on Tuesday, 6 May 2003 14:24:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:12 UTC