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

[Bug 1768] New: [FS] editorial: 7.2.16 The fn:zero-or-one, fn:one-or-more, and fn:exactly-one functions

From: <bugzilla@wiggum.w3.org>
Date: Wed, 20 Jul 2005 00:03:39 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1Dv23n-0008P7-Da@wiggum.w3.org>

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

           Summary: [FS] editorial: 7.2.16 The fn:zero-or-one, fn:one-or-
                    more, and fn:exactly-one functions
           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


7.2.16 The fn:zero-or-one, fn:one-or-more, and fn:exactly-one functions

"For example"
    Start a new para with this sentence?

"the function always return at most one book element"
    s/return/returns/

"However, the static typing feature cannot infers"
    s/infers/infer/

"will return a static type error at compile time"
    1) You don't "return" an error, you "raise" it.
    2) 'static error' and 'type error' are distinct.
    3) "compile time" is not defined.
    So change to:
        "will raise a type error during static type analysis"
Received on Wednesday, 20 July 2005 00:03:45 UTC

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