On Mar 6, 2011, at 17:37 , Andy Seaborne wrote: [snip] > > If we had that > > "foo" -> "foo"^^xsd:string > "foo"@de -> "foo"^^xsd:lang-de > "foo"^^xsd:string -> "foo"^^xsd:string > > i.e a datatype per language tag, I would not go there. The varieties of legal language tags is huge, and if anyone wanted to do some sort of a datatype reasoning with those, implementers may go mad:-) See: http://www.w3.org/International/questions/qa-choosing-language-tags for some niceties... Ivan > that might work but it is still assuming re-tooling of RDF processors and RDF-driven application to handle properly. > > "foo"^^xsd:string -> "foo" > > seems to be best for backwards compatibility. > > The value space of plain literal without language tag (SPARQL:simple literals) is xsd:string. > > The value space*s* of plain literal with language tag needs sorting out. > > A simple RDF processor can work by xsd:string -> simple literal. Current systems and applications continue to work. > > Andy > > ---- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 PGP Key: http://www.ivan-herman.net/pgpkey.html FOAF: http://www.ivan-herman.net/foaf.rdf
Received on Monday, 7 March 2011 09:03:42 UTC