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

[Bug 1663] New: [FS] editorial: 4.7.3.5 Computed Processing Instruction Constructors

From: <bugzilla@wiggum.w3.org>
Date: Sat, 16 Jul 2005 08:05:26 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1Dthfq-0007Yn-Cf@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1663

           Summary: [FS] editorial: 4.7.3.5 Computed Processing Instruction
                    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


4.7.3.5 Computed Processing Instruction Constructors

Norm / rule (2|3)
fs:item-sequence-to-untypedAtomic-PI( [[ 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.

Norm / rule (2|3)
fn:data( [[ Expr1 ]]_Expr )
    Ditto the above. Add parentheses to ensure a single arg.

DEv / rule 3 / premise 3
"xs:NCName(Value1); =>"
    Delete semicolon.

DEv / rule (2|3|4) / premise 3
"dynEnv |- xs:NCName(Value1) => NCName1"
    I don't think you need dynEnv for this.  Change to:
        NCName1 = xs:NCName(Value1)

DEv / rule (2|3|4)
    These three rules differ only in premise 2. Couldn't you combine them
    into one rule, with:
        statEnv |- Value1 matches (xs:NCName|xs:string|xdt:untypedAtomic)
    as its premise 2?
Received on Saturday, 16 July 2005 08:05:28 UTC

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