W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > April to June 2011

Re: Plain literals and xsd:string

From: Axel Polleres <axel.polleres@deri.org>
Date: Wed, 20 Apr 2011 17:57:52 +0100
Cc: public-rdf-dawg@w3.org
Message-Id: <A61E7A39-47AC-486C-94CA-871A947F7D6B@deri.org>
To: Andy Seaborne <andy.seaborne@epimorphics.com>
hmmmmmm, potential effects of RDF decisions on Update or Query at this stage worry me... is there a way we can get around such effects 
easily without just ignoring the movements in the RDF WG?

Axel
  
On 20 Apr 2011, at 09:47, Andy Seaborne wrote:

> 
> 
> On 19/04/11 23:17, Steve Harris wrote:
>> Hi all,
>> 
>> The RDF WG intends to recommend that xsd:strings be silently
>> converted to RDF plain literals internally. See Resolution 1 in
>> http://www.w3.org/2011/rdf-wg/meeting/2011-04-13.
>> 
>> This would have some impact on SPARQL deployments, as we go to some
>> lengths in a few places to preserve the differences. I'm not sure it
>> should necessarily affect the wording of any of the SPARQL texts, but
>> it's probably worth bearing in mind. It could be that we can simplify
>> some wording, but we should take care not to become dependent on a
>> new RDF rec. for publication.
>> 
>> - Steve
>> 
> 
> What should update do?
> 
> INSERT DATA { :s :p "foo"^^xsd:string }
> 
> 
> It affects query.  BGP matching is simple entailment.
> The wording must change there surely?
> 
> Either that or
> 
> SELECT * { ?s ?p "foo"^^xsd:string }
> 
> will stop matching on data now converted to "foo" without a software change to the query engine.
> 
> Existing databases + new software will see a change.
> 
> In my experience, it is OWL tools that will be affected as they like to use xsd:string in RDF for ontologies.
> 
> 	Andy
> 
> 
Received on Wednesday, 20 April 2011 16:58:20 GMT

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