Re: URIs for huge literals

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..

c