Lists Home |
Date Index |
Er, I confess to not having read the RDDL spec all that carefully.
Nonetheless, if I want a URI merely to identify my namespace, I shouldn't
have to resolve to something first. It's only an identifier, existing unto
I have read the Namespaces rec, and this problem of overloading URIs
occurred to me back then, as I read it. So it's not an RDDL problem, its the
overloaded usage problem that's quite classic and always leads to trouble
Hence, the long RDDL and namespace threads. URI mean too many (conflicting)
things to too many people.
> -----Original Message-----
> From: Leigh Dodds [mailto:email@example.com]
> Sent: Friday, January 18, 2002 1:22 PM
> To: Jeff Lowery; firstname.lastname@example.org
> Subject: RE: [xml-dev] URI intents? (was: RDDL: Negotiate out
> the Noise)
> > It seems that the basic problem is not what URIs point too,
> but that they
> > are being overloaded (points to a web page, identifies a
> namespace, points
> > to resource definition, etc, etc.)
> > Should URI's be extended to include intent?
> Isn't this what xlink:role and xlink:arcrole are already
> providing? Hence
> RDDL 'nature' and 'purpose'.