Re: [namespaceDocument-8] RDDL wishlist

In general, it is very useful to be able to make
information available about other things.
I don't see why a document in any *general*
language should be restrained from
including FYIs.  In fact, that is the way we find
information on the web.  Think of a semantic web link
as being a reference to something in  a new
namespace, which has definitive material
available on the web which can be found by dereferencing
its URI.  An option way of processing it is to pick up the
new information.  It is just what people do when they follow links,
but in this case it can be done, for example, in a recursive
attempt to resolve a query.

If you say that a namespace file should *only* contain pointers,
then you may impede a perfectly goo application which has
a bunch of useful stuff in a single language
(e.g. RDF with a style sheet) and make such applications work at
half speed because you force an extra indirection.


----- Original Message -----
From: "Tim Bray" <>
To: "Jonathan Borden" <>; "Patrick Stickler"
<>; "TAG" <>
Sent: Thursday, February 21, 2002 2:25 PM
Subject: Re: [namespaceDocument-8] RDDL wishlist

> At 08:14 AM 21/02/02 -0500, Jonathan Borden wrote:
> >Patrick Sticker wrote:
> >> 1. I want to be able to use any URI whatsoever to name each
> >> RDDL resource. Not an ID. Not an http: href/URL. Any URI.
> >> Something equivalent to rdf:about.
> >
> >This is an interesting question: should a namespace document be able to
> >statements about URIs not within the namespace?
> Can you guys try again?  I'm missing the point.  The RDDL idea is
> you dereference a namespace URI to get a resource that contains
> description of the namespace as a whole, plus descriptions of
> useful resources each xlinked to the resource itself.  The
> linked-to resources can have any old kind of URI you want...
> what am I missing? -Tim

Received on Wednesday, 27 February 2002 14:35:47 UTC