- From: Nathan <nathan@webr3.org>
- Date: Mon, 18 Apr 2011 00:25:22 +0100
- To: Steve Harris <steve.harris@garlik.com>
- CC: Sandro Hawke <sandro@w3.org>, Ivan Herman <ivan@w3.org>, Richard Cyganiak <richard@cyganiak.de>, Lee Feigenbaum <lee@thefigtrees.net>, antoine.zimmermann@insa-lyon.fr, public-rdf-wg <public-rdf-wg@w3.org>
Steve Harris wrote:
> On 2011-04-17, at 19:16, Nathan wrote:
>
>> Steve Harris wrote:
>>> On 2011-04-17, at 17:55, Sandro Hawke wrote:
>>>> Of course, this is OWL not SPARQL. I don't see any good way to deal
>>>> with this in SPARQL. I don't really understand how datatype() and
>>>> such are supposed to work in SPARQL -- are stores really supposed to
>>>> remember which values came in as xs:int vs xs:integer?
>>> Yes.
>> Out of interest, what practical difference does it make? I'm racking my brains but struggling to think of one, other than perhaps a graph signing / encryption case for ground graphs?
>
> Well, one matches { ?x ?y "3"^^xsd:int } and one doesn't. Both match { ?y ?y ?z . FILTER(?z = 3) }.
Yes, but what practical value does anybody in the world get from
"3"^^xsd:integer being different to "3"^^xsd:int?
Who is the person that doesn't want the 3 if some(body/machine)
somewhere once said it's an xsd:int, but does want the 3 if it was said
to be an xsd:integer?
Received on Sunday, 17 April 2011 23:26:00 UTC