- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 19 Jul 2005 22:35:26 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1758
Summary: [FS] editorial: 7.2.5 The fn:collection and fn:doc
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.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)
Received on Tuesday, 19 July 2005 22:35:29 UTC