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

Re: rq25.xml String functions definitions - first shot (ACTION-350)

From: Steve Harris <steve.harris@garlik.com>
Date: Tue, 21 Dec 2010 14:07:38 +0000
Cc: "SPARQL Working Group" <public-rdf-dawg@w3.org>
Message-Id: <A0B9F324-6468-4276-9B50-D91048193114@garlik.com>
To: Axel Polleres <axel.polleres@deri.org>
On 2010-12-21, at 13:49, Axel Polleres wrote:

> Hi Steve,
> 
> I took http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0361.html as a basis, where the following was suggested:
> 
> "
> ENCODES(string)
>   Result is a simple literal regardless of string.
>   string can be simple, or xsd:string
>   Not clear to me it should apply to LitLang
>     proposal: it does not (it is an error).
> "
> 
> and I hadn't heard objections raised against this as of yet.
> Is your proposal to extend encode() towards accepting plain literals with lang tags?

Yes.

N.B. it's encode_for_uri() in the current text, matching the F&O name.

> (would look ok from my side, and consistent with the remaining string functions that also allow this...)
> 
> Actually, I guess I even have a use case for this, i.e. URIs can also use language, e.g.
> 
> http://www.weihnachten.at/
> http://www.christmas.co.uk/
> 
> If you want to create such language dependent URIs from text, you may want encode() to work on language tagged literals...

Exactly.

- 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 Tuesday, 21 December 2010 14:08:14 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:44 GMT