This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1768 - [FS] editorial: 7.2.16 The fn:zero-or-one, fn:one-or-more, and fn:exactly-one functions
Summary: [FS] editorial: 7.2.16 The fn:zero-or-one, fn:one-or-more, and fn:exactly-one...
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Last Call drafts
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: Jerome Simeon
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-20 00:03 UTC by Michael Dyck
Modified: 2007-01-16 17:42 UTC (History)
0 users

See Also:


Attachments

Description Michael Dyck 2005-07-20 00:03:39 UTC
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"
Comment 1 Jerome Simeon 2006-03-30 00:49:16 UTC
Fixed as suggested.
- Jerome