W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > July to September 2006

Re: DISTINCTness of literals

From: Bijan Parsia <bparsia@cs.man.ac.uk>
Date: Mon, 25 Sep 2006 15:01:20 +0100
Message-Id: <6A9182BF-CE46-4D7D-92D0-3DA2D7D97D9B@cs.man.ac.uk>
Cc: RDF Data Access Working Group <public-rdf-dawg@w3.org>
To: andy.seaborne@hp.com

On Sep 25, 2006, at 11:22 AM, Seaborne, Andy wrote:

> We left open what to do about literals of the same value in  
> DISTINCT results.
> I propose that term-distinct apply to literals, and not a form of  
> value-distinct.
> SPARQL is defined for simple entailment anyway so for this  
> entailment regime it would be term-distinct for literals.

While this is a coherent view, it's not quite nailed down that  
comparison for the purpose of distinctness is tied to the entailment  
regime. Value testing, as I understand Eric, is not.

> I propose that rq24 only talk about this.
> Some considerations:
> 1/  It's terms that are returned, not values, when encoded into the  
> result set.  But which term should be returned if two literals are  
> value-distinct and not term-distinct?
> e.g.
> "1"^^xsd:integer
> "01"^^xsd:integer
> "1.0"^^xsd:decimal

I would give either the first in sort order or any (implementation  
defined), with a preference for the latter..

> The SPARQL test suite is based on RDF graph equality [1] which uses  
> term equality for literals.
> 2/ XPath/XQuery Functions&Operators [2] allows numeric type  
> promotion - but XML schema datatypes does not and double/float/ 
> decimal have different value spaces.  See [3].

One word, ew.

> "1.3"^^xsd:double != "1.3"^^decimal

This would indeed have to be decided. Of course, per usual, we could  
allow for parameterization.

Received on Monday, 25 September 2006 14:02:15 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:00:51 UTC