This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
7.2.4 The fn:boolean function "a sequence of one or more nodes" Actually, F+O 15.1.1 indicates that a sequence consisting of a node followed by atomic values should not raise a type error, whereas this rule would reject it. "or a singleton value of type ..." Missed xs:boolean.
F+O describes the dynamic semantics. The static semantics is designed to disallow any heterogeneous node/atomic value sequence. Best regards Michael (speaking for myself, but also as the original proposer of the semantics)
Fixed the second comment, without changing the intended semantics of fn:boolean. - Jerome
"The fn:boolean function as described in the [Functions and Operators] document takes an empty sequence, a sequence of one or more nodes, or a singleton value of type .... All other values are illegal." No, fn:boolean <em>as described in the F+O doc</em> handles a wider set of inputs. If you want the static typing to accept a narrower set of types, fine, but don't make it sound like they're in agreement. Also, the list of singleton types is missing xs:anyURI. Also, NodeType+ probably isn't what you want. See Bug 1747, comment #3.
(In reply to comment #3) > "The fn:boolean function as described in the [Functions and Operators] > document takes an empty sequence, a sequence of one or more nodes, or a > singleton value of type .... All other values are illegal." > No, fn:boolean <em>as described in the F+O doc</em> handles a wider > set of inputs. If you want the static typing to accept a narrower set > of types, fine, but don't make it sound like they're in agreement. I have clarified the distinction between the dynamic and static type restrictions. > Also, the list of singleton types is missing xs:anyURI. The Rec fixed this in the inference rule, but not in the preceding prose. > Also, NodeType+ probably isn't what you want. See Bug 1747, comment #3. Changed to [[ node()+ ]]_sequencetype.
These remaining points have been entered as FS erratum E026, and the fixes have been committed to the source files for the next edition of the FS document. Consequently, I'm marking this issue resolved-fixed, and closed.