- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 14 Jul 2005 04:12:36 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1580 Summary: [FS] technical: 4.1.5 Function Calls: complicated by pseudo-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 4.1.5 Function Calls "Otherwise, the function signatures matching the function name and arity are retrieved from the static environment." The XQuery and XPath specs both state: "Each function is uniquely identified by its expanded QName and its arity (number of parameters)." So am I correct in thinking that there would be *multiple* signatures only in the cases of the "arithmetic operator pseudo-functions" and the "comparison pseudo-functions"? Is it also true that the "union of atomic types" exceptions in the STA are only relevant to the pseudo-functions? (I.e., for any other call, you'd get the same result if those exceptions weren't there.) If so, then details that are only pertinent to pseudo-functions are being allowed to complicate the normal case. Why? It seems to me that this section would be much improved by banishing those details to B.2.
Received on Thursday, 14 July 2005 04:12:39 UTC