1704 2005-07-18 05:18:46 +0000 [FS] technical: 5.2 Module Declaration: importing a namespace that is the target of two modules 2006-10-19 18:17:40 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Formal Semantics 1.0 Last Call drafts All All CLOSED FIXED P2 normal --- 1 jmdyck simeon public-qt-comments oldest_to_newest 4790 0 jmdyck 2005-07-18 05:18:46 +0000 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 5084 1 simeon 2005-07-21 19:07:00 +0000 Yes, that is a good catch. I have the same opinion, and I think your fix makes sense. - Jerome 5601 2 simeon 2005-08-31 15:15:15 +0000 The XML Query and XSLT WGs have accepted your bug with the proposed resolution. - Jerome 12290 3 jmdyck 2006-10-04 23:11:40 +0000 The 2006-06 CR does not use my proposed resolution. 12377 4 simeon 2006-10-10 14:52:17 +0000 Finally implemented as suggested. Similar fix applies to the DCP rules. - Jerome