Re: RDF's curious literals

cr wrote:
> theres a few issues in terms of topography - when to use the resource as the uri (123 or :cat), when to use a 'value' property on the resource (eg URI is a hash of a larger string value), and when to you use the dereferenced content of the URI as the value..

Ah, but be careful here. The "dereferenced content" of the resource 
identified by the URI <rdfliteral:123;xsd:literal> is the value 123, 
*not* the string "123". The "dereferenced content" of the resource 
identified by the URI <http://example.org/presidents/GeorgeWBush> is the 
person currently in the White House, *not* the string "George W. Bush".

When talking about Resources Formerly Known as Literals, it doesn't make 
any sense to say "dereferenced content". The lexical form you might have 
used in some particular serialization as a shortcut to the resource's 
URI is not the "dereferenced content" of the identified resource (except 
in a singular case: all resources with rdf:type xsd:String, formally 
known as rdf:datatype xsd:string).

Garret

Received on Tuesday, 31 July 2007 22:36:49 UTC