Re: Literals (Re: model theory for RDF/S)

Patrick.Stickler@nokia.com wrote:

> > Also, as written literals can't include spaces.  The literal should be
> > enclosed in doublequotes, with a universal convention about how
> > to put unusual characters (such as " itself) inside doublequotes.
> 
> Well, they'd be resources, encoded via URIs, not literals. So no quotes
> are needed. The idea is to eliminate the need for the concept of literals
> entirely from RDF, such that *everything* is a resource, period. 

You still need to be able to encode arbitrary strings, including spaces,
into your new URIs.

Let's say I currently have MyResource--hasProperty-->"Some
human-readable notes about it" where the object of this triple is a
literal.

If I then change that literal into some form of URI, we have to be able
to preserve the spaces, encoded in some way that is URI-legal.

e.g. dt:string:Some+human+readable+notes+about+it (with some suitable
way of escaping special characters).

Cheers,

David Allsopp
QinetiQ
UK

-- 
/d{def}def/u{dup}d[0 -185 u 0 300 u]concat/q 5e-3 d/m{mul}d/z{A u m B u
m}d/r{rlineto}d/X -2 q 1{d/Y -2 q 2{d/A 0 d/B 0 d 64 -1 1{/f exch d/B
A/A z sub X add d B 2 m m Y add d z add 4 gt{exit}if/f 64 d}for f 64 div
setgray X Y moveto 0 q neg u 0 0 q u 0 r r r r fill/Y}for/X}for showpage

Received on Tuesday, 2 October 2001 06:37:08 UTC