W3C home > Mailing lists > Public > www-rdf-interest@w3.org > September 2000

Re: Referencing items in RDF

From: Dan Brickley <danbri@w3.org>
Date: Sun, 3 Sep 2000 09:15:30 -0400 (EDT)
To: Aaron Swartz <aswartz@swartzfam.com>
cc: RDF Interest <www-rdf-interest@w3.org>
Message-ID: <Pine.LNX.4.21.0009030855410.29646-100000@tux.w3.org>
On Sun, 3 Sep 2000, Aaron Swartz wrote:

> Is there a way, or a URI format, to represent the value of an RDF statement.
> That is, given these two URIs:
> http://www.w3.org/Home/Lassila
> http://xmlns.com/example/1.0/Creator
> How do I represent the value "Ora Lassila"?

One way is like this: "Ora Lassila". The value represents itself quite

Literal strings are something like un-named resources, you identify them
through providing their content, since they
don't themselves have Web names (URIs). Like other resources, you might
also identify them through description. Just as we might say "the company
whose homepage is xxx" or "the person whose personalMailbox if yyy", we
might say "the chunk of nameless data whose foo-checksum is zzz". This
kind of strategy can uniquely pick out something without using/needing a
URI for it.

If you're after a way of representing literal data within a URI,
that's been done (and to my suprise implemented in browsers). You're after
the data: URI scheme. This is a way of tunnelling blobs of mime-typed data
through URI syntax.

Netscape browser for example seems to understand this (try pasting into a
Web page somewhere).

<img src="data:image/gif;base64,R0lGODdhIAAgAIAAAAAAAPj8+CwAAAAAI
    JtnE2KizVUkYJVZZ1nczBxXlFopZBtoJ2diXGdNUymmJdFMAADs=" /> 

There's some support for this in the Perl URI module too (which was what I
found when I went Googling to find you a citatation)

see also:

here's the path to the rfc:


	 The "data" URL scheme

	1. Abstract
	   A new URL scheme, "data", is defined. It allows inclusion of small
	   data items as "immediate" data, as if it had been included

Here's another one to play with:


> **Has it been done?

sort of (see above)

> I assume that the benefits of having a URI to represent RDF values would be
> obvious -- URIs are extremely useful and are supposedly extensible to
> represent anything with identity.

Yes... the data-aggregating power of RDF largely comes from having
piggybacked on the Web naming system. That said, I think sometimes in RDF
land we've over emphasised the need to have URIs for
everything. Oftentimes we'll be able to get by through identifying
resources by description rather than by name (now we've got a framework
for describing resources!). It's a bootstrapping thing...

Not sure if this answers your question!

Received on Sunday, 3 September 2000 09:15:31 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:07:31 UTC