Re: URI etymology

> > that when you attach other strings to it, comes up with
> > URIs or URI-References that identify terms that your
> > processor may or may not understand to some certain
> > context.
>
> Oops. Nope. Can't do that.

I agree that outside of RDF, the {namespace}name construct is broken
insofar as transformation from QName => URI-ref for use in RDF is
concerned. and yes, perhaps there should be a standard mapping from
one to the other, but perhaps it is too late.

I don't agree that you can't do that in RDF, because in RDF language
specifications (i.e. RDF schemata), there are no QName mappings, so it
works perfectly!

> Namespace URI refs such as "http://.../foo#" that enable one
> to get RDF resource URI refs such as "http://...foo#bar" are
> hacks. Period.

I agree, but only as far as namespaces for use as QNames are
concerned. But then, look at XSD: they don't use a "#" on the end, but
they do define standard mappings from the QNames to URIs, which are
made by:-

   {NS}name => NS#name

As defined in the XSD specification. A new URN space may well clear
this up, but it's pointless as far as RDF specific applications are
concerned. The RDF, RDF Schema, DAML, EARL, Annotea, FOAF, Dublin Core
and DCT namespaces etc. are not broken.

> What is also being forgotten or missed entirely is the fact that
> syntactic forms as defined by XML and XML Namespaces
> do not automagically map to RDF resource identities. [...]

Not forgotten or missed, just talinig past one another, I think.

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

Received on Tuesday, 12 June 2001 11:39:19 UTC