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

[Bug 1660] New: [FS] editorial: 4.7.3.2 Computed Attribute Constructors

From: <bugzilla@wiggum.w3.org>
Date: Sat, 16 Jul 2005 07:19:15 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1Dtgx9-0005I0-Q2@wiggum.w3.org>

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

           Summary: [FS] editorial: 4.7.3.2 Computed Attribute 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.2 Computed Attribute Constructors

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

DEv / rule (1|2)
"fs:item-sequence-to-untypedAtomic(Expr)"
    Similar to previous.
    Put "Expr" in parentheses to ensure a single arg.

DEv / rule (1|2)
dynEnv |- fs:item-sequence-to-untypedAtomic(Expr) => Value
    The AttributeValue in the conclusion wants a SimpleValue, for which
    Value is too general.  But we know that item-sequence-to-untypedAtomic
    will return an atomic value, so rename "Value" as "AtomicValue"
    (which satisfies the need for a SimpleValue).

DEv / rule 1 / conclusion
attribute expanded-QName of type xdt:untypedAtomic { Value }
    The EBNF for AttributeValue says that the thing after the "attribute"
    keyword is an AttributeName (i.e., QName), not an expanded-QName.
(leftover from last year, comment #077)

DEv / rule 2
"statEnv |- QName1 = xs:QName(Value1)"
    The xs:QName constructor function returns a value from the value space
    of xs:QName, which in the Formal Value syntax is denoted by
    'expanded-QName', so change "QName1" to "expanded-QName".

    This then also runs afoul of the AttributeValue EBNF. So perhaps
    the EBNF should be changed, from "QName" to "expanded-QName".

DEv / rule 2 / premise 3
"statEnv |- QName1 = xs:QName(Value1)"
    You don't need a static environment for such a judgment.

DErr / para 1
"not a xs:QName. the xmlns namespace."
    Delete "the xmlns namespace."
Received on Saturday, 16 July 2005 07:19:18 UTC

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