- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 04 Feb 2009 17:13:48 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6531 Summary: [FOerrata] fn:concat and '...' not defined Product: XPath / XQuery / XSLT Version: Recommendation Platform: All OS/Version: All Status: NEW Severity: minor Priority: P3 Component: Functions and Operators AssignedTo: mike@saxonica.com ReportedBy: bungeman@gmail.com QAContact: public-qt-comments@w3.org This is somewhat nit-picky but fn:concat is specified as fn:concat($arg1 as xs:anyAtomicType?, $arg2 as xs:anyAtomicType?, ... ) as xs:string but the meaning and usage of '...' is never defined. This should be defined in section 1.4. Also, the base type of these optional arguments should be stated explicitly, like fn:concat($arg1 as xs:anyAtomicType?, $arg2 as xs:anyAtomicType?, ... as xs:anyAtomicType?) as xs:string instead of implicitly by stating this only in the text following. I realize that fn:concat is the only vararg function and is rather special cased, but I believe that making such changes would make the meaning far more explicit. So the proposal is to add to section 1.4 wording to the effect of "The last parameter declaration of a function signature may specify '...' instead of a $parameter-name. This indicates that there may be a variable number of arguments passed to the function. The type of these arguments must match the type specified by the parameter-type of the parameter declaration." and change the fn:concat signature as described above. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 4 February 2009 17:13:57 UTC