Lists Home |
Date Index |
I was attempting to make a pragmatic point, not a criticism of the RDDL
language. If I deference a namespace URI and find nothing, I don't know
whether it was intended by the doc author that there be nothing there, or
there was supposed to be something there but the URI had a typo. If the
host mentioned in that namespace URI is down and I'm hoping to find, say, a
collection of stylesheet resources, or a jar file to use to process the
original document, I don't know whether to try again later or look somewhere
else. If I never dereference the namespace URI, I won't know what useful
things I might have missed. That's why I'd like to know whether to expect
to find something or not, perhaps by some additional attributes, by some
convention involving the URI type, or something else.
----- Original Message -----
From: "Jonathan Borden" <email@example.com>
To: "Jeff Greif" <firstname.lastname@example.org>; "Leigh Dodds"
<email@example.com>; "Bullard, Claude L (Len)" <firstname.lastname@example.org>
Sent: Friday, January 18, 2002 12:22 PM
Subject: Re: [xml-dev] RDDL (was RE: [xml-dev] Negotiate Out The Noise)
> Jeff Greif wrote:
> > The unfortunate problem with RDDL and all the alternatives except (1) is
> > that you cannot tell without looking whether there will be something at
> > NS URI, and if there is, whether you need to know about it.
> Suppose you simply decide never to dereference a URI regardless of what it
> looks like. How does the existence of a document which _can_ be
> affect your life? As has already been said, you can always use google.
> Indeed a tenet of the RDF framework is that URIs are opaque. One derives
> properties of a resource by what is said "about" the resource, not by
> dereferencing its URI. One never _has_ to dereference a URI to use RDF.
> does one have to dereference a namespace URI _ever_ if all one want to do
> use XML namespaces as a way to disambiguate element names. What could you
> "need to know about"?