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

[Bug 1659] New: [FS] editorial: Computed Element Constructors

From: <bugzilla@wiggum.w3.org>
Date: Sat, 16 Jul 2005 06:33:01 +0000
To: public-qt-comments@w3.org
Message-Id: <E1DtgEP-0002vh-JC@wiggum.w3.org>


           Summary: [FS] editorial: Computed Element Constructors
           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 Computed Element Constructors

"Local namespace declarations ..."
    This para is a leftover from the previous Last Call draft, and doesn't
    make much sense now.


"Computed element constructors using the fs:item-sequence-to-node-sequence
function over their content expression."
    This isn't a sentence.  s/using/use/ ?

Norm / rule (2|3)
"fs:item-sequence-to-node-sequence( [[ Expr ]]_Expr )"
    This function takes a single argument (of type item*), but
    [[ Expr ]]_Expr could result in a sequence of comma-separated
    ExprSingles, which would then constitute multiple args.
    Put [[ Expr ]]_Expr in parentheses to ensure a single arg.


"The static semantic"

"element QName { Expr }"
    These rules must be modified to handle a CompElemConstructor that
    (somehow) contains NamespaceBindings.


"Third, The namespace bindings"

DEv / rule (1|2)
    Change to "NamespaceBinding".

DEv / rule 1 / premise 1
Expr = CompElemNamespace1, ..., CompElemNamespacen, (Expr0)
DEv / rule 2 / premise 3
Expr2 = CompElemNamespace1, ..., CompElemNamespacen, (Expr3)
    The parentheses around the final Expr are odd.

DEv / rule 2 / premise 10
"statEnvm, dynEnv"
    Change the comma to a semicolon.

DEv / rule 1 / premise 10
DEv / rule 2 / premise 12
    This invocation is inconsistent with the "declaration" in 3.1.1,
    which indicates that it should be invoked as fs:active_ns(statEnv).

DEv / rules (1|2)
    These rules don't actually construct an element value!
    Their conclusions should be something like:
    ... => element QName of type something {Value} {NamespaceBindings}

DEv / rule (1|2)
    These rules are almost identical. Refactor.
    Rule 2 could be reduced to a few premises plus an invocaton of rule 1.
Received on Saturday, 16 July 2005 06:34:53 UTC

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