This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1704 - [FS] technical: 5.2 Module Declaration: importing a namespace that is the target of two modules
Summary: [FS] technical: 5.2 Module Declaration: importing a namespace that is the tar...
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Last Call drafts
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Jerome Simeon
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-18 05:18 UTC by Michael Dyck
Modified: 2006-10-19 18:17 UTC (History)
0 users

See Also:


Attachments

Description Michael Dyck 2005-07-18 05:18:46 UTC
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
Comment 1 Jerome Simeon 2005-07-21 19:07:00 UTC
Yes, that is a good catch. I have the same opinion, and I think your
fix makes sense.

- Jerome
Comment 2 Jerome Simeon 2005-08-31 15:15:15 UTC
The XML Query and XSLT WGs have accepted your bug with the proposed resolution. 
- Jerome
Comment 3 Michael Dyck 2006-10-04 23:11:40 UTC
The 2006-06 CR does not use my proposed resolution.
Comment 4 Jerome Simeon 2006-10-10 14:52:17 UTC
Finally implemented as suggested. Similar fix applies to the DCP rules.
- Jerome