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

[Bug 1715] New: [FS] editorial: 5.11 Module Import

From: <bugzilla@wiggum.w3.org>
Date: Mon, 18 Jul 2005 19:56:42 +0000
To: public-qt-comments@w3.org
Message-Id: <E1DubjG-0006he-V8@wiggum.w3.org>


           Summary: [FS] editorial: 5.11 Module Import
           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.11 Module Import

SCP / rule 1 / premise (2|3)
"statEnv1 + varType(fs:local-variables(...))"
"statEnv2 + localFunc(fs:local-functions(...))"
    This syntax is unspecified.

SCP / rule 1 / premise 3
"statEnv2 + localFunc(...)"

SCP / rule 1 / conclusion
"import module (namespace NCName =)? ..."
    If NCName appears, it should be bound to the target namespace in

Notation 2
"The rules below depend on the following auxilliary judgments."
    Presumably, this should be followed by declarations of the
    "=>import_variables" and "=>import_functions" judgment forms.

    Such a Notation section should precede the DCP section though.

"This judgment adds each ..." (twice)

DCP / rule 2
dynEnv2 ; URI |- (expanded-QName2(Type2,1, ..., Type2,n)), иии,"
                 (expanded-QNamek(Typek,1, ..., Typek,n)) => ...
    This requires that all functions imported from a module have the same
    number of arguments (n), which is not what you want.

    You could fix this with subscripts-on-subscripts, but that would make
    the rule harder to read and understand. The better route, which
    actually makes the rule *easier* to read and understand, is to
    introduce a Formal symbol for (this kind of) function signature.

"to the input dynamic context."
    "input"? Maybe s/input/importing/

DCP / rule 3 / premise (2|3)
"fs:local-foo(statEnv2, URILiteral1)"
    Delete the subscript 1.

"URILiteral ; dynEnvi |-"
    Change to "dynEnvi ; URILiteral |-" to match previous rules.

dynEnv2, statEnv2
    It's not clear why dynEnv2 isn't used, or where statEnv2 comes from.
Received on Monday, 18 July 2005 19:57:18 UTC

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