- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 24 Sep 2005 17:47:03 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2292
Summary: Editorial: why is fn:number in section "14 Functions and
Operators on Nodes"
Product: XPath / XQuery / XSLT
Version: Last Call drafts
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P2
Component: Functions and Operators
AssignedTo: ashok.malhotra@oracle.com
ReportedBy: frans.englich@telia.com
QAContact: public-qt-comments@w3.org
I don't know whether issues like these are too minor to spend the time on it(if
so, tell me), but:
Why is fn:number put in section 14 Functions and Operators on Nodes? All other
functions and operators in section 14 are from what I can tell clearly bound to
nodes by that they have nodes as argument(s) or return values. fn:number, on the
contrary, takes either the context item node or an atomic value(may be a node
via atomization, of course).
Wouldn't "15.1 General Functions and Operators on Sequences" be a better place?
For example, the fn:boolean function is there, which can be said to be
conceptually similar(it derives a value from a sequence).
This is of course only a minor, editorial issue. Perhaps the current layout have
a clear motivation, which in that case would be interesting to hear.
Cheers,
Frans
Received on Saturday, 24 September 2005 17:47:12 UTC