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.5 The fn:collection and fn:doc functions "if the argument is not a literal string or is a string but not defined in statEnv.collectionType" The corresponding rules are given in the opposite order. Swap the order in the prose, I think. STA / rule 3 / conclusion "fn:collection(Expr)" s/Expr/StringLiteral/ STA / rule 4 / premise 1 "statEnv |- Expr is not a StringLiteral" Delete "statEnv |-". STA / rule [34] / conclusion "... | processing-intruction | ..." s/intr/instr/ STA / rule 5 / premise 1 "statEnv |- statEnv.docType(StringLiteral) = ..." Delete "statEnv |-". "if the argument is not a literal string or is not defined in the domain of statEnv.docType" Again, the corresponding rules are given in the opposite order. Swap the order in the prose, I think. STA / rule 6 / conclusion "fn:doc(Expr)" s/Expr/StringLiteral/ STA / rule 7 / premise 1 not(Expr = StringLiteral) Regardless of statEnv and Expr, you can always find a binding for 'StringLiteral' such that the premise holds (i.e., even if Expr *is* a StringLiteral) which is not what you want. Change to: "Expr is not a StringLiteral" as in rule 4. (leftover from last year, comment #188)
Fixed as suggested. Some editorial discretion necessary as the section had already been changed. - Jerome
STA / rule 7 / premise 2 statEnv |- Expr is not a URILiteral Delete "statEnv |-".
Fixed. - Jerome
Closing bug because commenter has not objected to the resolution posted on 2007-01-16