W3C home > Mailing lists > Public > semantic-web@w3.org > August 2007

Re: URIs for huge literals

From: cr <_@whats-your.name>
Date: Wed, 1 Aug 2007 12:06:24 -0400
To: Semantic Web <semantic-web@w3.org>
Message-ID: <20070801160624.GB1822@replic.net>

agree that treating literals as first class resources simplifies many things in API / implementation in engine as well as UI,
but there are some tradeoffs...

i'm pretty sure converting <http://data.info/integer/12> to 12 is more expensive since it involves some string parsing  - unless you store the plain value too in the backend - at which point you have a URI _and_ a literal anyways.. - overall i favor is_literal? and to/from_string  methods on a resource class than have extra literal classes and branched code everywhere, but its something to think about

we'd need a way to refer to strings too large to fit into URIs:

http://data.info/UTF-8/SHA1/e639ea194606d69fb6e0451b1d0ab552dc5ca398 ? 

RDF should be renamed RLDF..

Received on Wednesday, 1 August 2007 20:07:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:47:26 UTC