Re: Namespaces wihtout "#" Was: Few CWM Bugs

Hi Tom,

> This is what RDDL was trying to address, in a restricted
> domain.

Hmm... RDDL is there to provide a human and machine "readable" neutral
catalogue langauge for pointing at various resources related to a
namespace. It does not really address the question of what a URI
denotes, IMO, although the fields are related ("what should be at the
end of a namespace?" vs. "what does an HTTP URI necessarily denote?").
There was tremendous excitement on XML-Dev when Tim Bray started
talking about a solution for the former question, and Jonathan quickly
hacked up the proposal which became RDDL. I wonder if a similar thing
will ever happen for the latter question :-)

> Is there a basic, conceptual difference between:
>
> 1) Meta data about a resource (like the distinction between a
> book and one specific copy of it - as in Sean's post: "But
> whoops... Aaron is already using that URI to identify his copy
> of Weaving The Web"),

Sidenote: this is not the point that I was making. Aaron claims that
his URI denotes his copy of Weaving The Web. TimBL appears to claim
otherwise, i.e. that the URI actually denotes the "document" as a set
of entities over time on Aaron's server. The assertion was that we
need a URI to identify the "document", parried by the introduction of
a predicate relationship that allows us to identify just that.

> 2) Different predicates for asserting such distinctions, or
> 3) Special headers for announcing such a distinction

As long as you can send the metadata (or a pointer back to the
metadata) back over HTTP, and therefore be (in some sense of the word)
definitive about what is being identified, then it's probably just a
matter of utility.

Cheers,

--
Kindest Regards,
Sean B. Palmer
@prefix : <http://webns.net/roughterms/> .
:Sean :hasHomepage <http://purl.org/net/sbp/> .

Received on Monday, 26 November 2001 18:44:31 UTC