W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > October to December 2010

Re: what functions should we include in SPARQL 1.1?

From: Steve Harris <steve.harris@garlik.com>
Date: Wed, 3 Nov 2010 11:06:22 +0000
Cc: Lee Feigenbaum <lee@thefigtrees.net>, SPARQL Working Group <public-rdf-dawg@w3.org>
Message-Id: <E052ECA4-9926-4E7E-AEAC-3A7A18EF383E@garlik.com>
To: Andy Seaborne <andy.seaborne@epimorphics.com>
On 2010-11-03, at 10:23, Andy Seaborne wrote:

> Fine tuning.
> fn:concat
> http://www.w3.org/TR/xpath-functions/#func-concat
> [[
> The fn:concat function is specified to allow an two or more arguments that are concatenated together. This is the only function specified in this document that allows a variable number of arguments. This capability is retained for compatibility with [XML Path Language (XPath) Version 1.0].
> ]]
> As Steve pointed out, fn:concat casts to string (and empty sequences go to empty string) but also it's the only function in F&O that takes a variable number of arguments; others take sequences e.g. fn:string-join.
> If we wish to be more conservative, we could provide own binary string concatenation operation (tighter signature, can devolves to fn:concat for the functionality).

OK, but I think we should also expose a CONCAT() function that's fn:concat underneath. The variadic nature is useful, as is the implicit cast to xsd:string.

- Steve 

Steve Harris, CTO, Garlik Limited
1-3 Halford Road, Richmond, TW10 6AW, UK
+44 20 8439 8203  http://www.garlik.com/
Registered in England and Wales 535 7233 VAT # 849 0517 11
Registered office: Thames House, Portsmouth Road, Esher, Surrey, KT10 9AD
Received on Wednesday, 3 November 2010 11:06:56 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:02 UTC