W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2006

[Bug 3205] [FS] editorial: 7.2.5 The fn:collection and fn:doc functions

From: <bugzilla@wiggum.w3.org>
Date: Tue, 09 May 2006 02:24:30 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1FdHtm-0004TY-3W@wiggum.w3.org>

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

           Summary: [FS] editorial: 7.2.5 The fn:collection and fn:doc
                    functions
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Formal Semantics
        AssignedTo: simeon@us.ibm.com
        ReportedBy: jmdyck@ibiblio.org
         QAContact: public-qt-comments@w3.org


7.2.5 The fn:collection and fn:doc functions

STA / rule 2 / premise 2
STA / rule 3 / premise 2
STA / rule 5 / premise 2
STA / rule 6 / premise 2
statEnv.collectionType(URILiteral) ...
statEnv.docType(URILiteral) ...
    The domain of collectionType() and docType() is URI (i.e., AnyURI),
    not URILiteral. Change 'URILiteral' to 'AnyURI', and add premise(s)
    to go from URILiteral to AnyURI (as in Bug 1796).

STA / rule 2 / conclusion
STA / rule 3 / conclusion
STA / rule 4 / premise 2
STA / rule 5 / conclusion
STA / rule 6 / conclusion
QName(URILiteral)
    ExprSingle does not derive URILiteral, so URILiteral is not
    syntactically valid as a function argument.
    Moreover, the use of URILiteral suggests (via section 3.4.5) that the
    argument must be a "statically known valid absolute URI", but the
    'absolute' requirement is presumably unwarranted in this context,
    since relative URIs can be resolved statically.
    Change 'URILiteral' to 'StringLiteral'.
Received on Tuesday, 9 May 2006 02:24:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:12 UTC