- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 18 Jul 2005 05:18:46 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1704 Summary: [FS] editorial: [FS] technical: 5.2 Module Declaration: importing a namespace that is the target of two modules Product: XPath / XQuery / XSLT Version: Last Call drafts Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Formal Semantics AssignedTo: simeon@us.ibm.com ReportedBy: jmdyck@ibiblio.org QAContact: public-qt-comments@w3.org 5.2 Module Declaration SCP / rule 1 If there are two library modules (L1 + L2) that share a target namespace (N), this rule allows you to conclude N =>module_statEnv statEnv_L1 and/or N =>module_statEnv statEnv_L2 and you could use *either* of those to satisfy 5.11 / SCP / rule 1 / premise 1 for some other module's "import module N". But the intended semantics are that the import pulls in (roughly) statEnv_L1 + statEnv_L2. (Ditto all this for DCP.) You could handle this with some ad-hockery such as: L1, ..., Ln = fs:all-library-modules-with-target-namespace(N) L1 =>stat statEnv1 ... Ln =>stat statEnvn statEnv = fs:combine_statEnvs( statEnv1, ..., statEnvn ) ---------------------- N =>module_statEnv statEnv
Received on Monday, 18 July 2005 05:19:03 UTC