- From: Andy Seaborne <andy.seaborne@epimorphics.com>
- Date: Mon, 07 Mar 2011 10:12:19 +0000
- To: Ivan Herman <ivan@w3.org>
- CC: Steve Harris <steve.harris@garlik.com>, Sandro Hawke <sandro@w3.org>, Pat Hayes <phayes@ihmc.us>, RDF Working Group WG <public-rdf-wg@w3.org>
On 07/03/11 09:06, Ivan Herman wrote: > > On Mar 6, 2011, at 19:32 , Steve Harris wrote: > >> On 2011-03-06, at 16:37, Andy Seaborne wrote: >>> On 06/03/11 08:12, Steve Harris wrote: >>>>> What about just saying, "please don't use xs:string any more", and >>>>> "if >>>>>> you (some RDF software) find an xs:string, you SHOULD convert it >>>>>> to a plain literal". Would that pretty much solve the problem? >>>> That's the inverse of what I suggested just before I read this mail. >>>> It works for me (from a storage point of view it's probably simpler), >>>> but I understand that it's not ideal for some reasoning systems? >>> >>> the inverse was: >>> On 06/03/11 07:59, Steve Harris wrote: >>>> "foo"^^xsd:string -> "foo"^^xsd:string >>>> "foo" -> "foo"^^xsd:string >>>> "foo"@de -> "foo"^^xsd:string @de >>> >>> >>> I think it works better as >>> >>> "foo"^^xsd:string -> "foo" >>> "foo"@de -> "foo"@de >> >> I agree, but someone, possibly Pat said there was an issue with untyped literals and reasoning. >> > > AFAIK, no reasoning is defined on non-datatyped literals... Agreed (mod RDFS rules XSD1a and XSD 1b) but isn't that a matter of the value-space? This is all in syntax space in a way that enables direct RDF manipulation to be as it is. Andy
Received on Monday, 7 March 2011 10:12:59 UTC