W3C home > Mailing lists > Public > uri@w3.org > November 2007

Re: Updated URI Template proposal

From: Joe Gregorio <joe@bitworking.org>
Date: Thu, 8 Nov 2007 12:59:46 -0500
Message-ID: <3f1451f50711080959o46643a24v630c0a1131d3b22a@mail.gmail.com>
To: "DeWitt Clinton" <dewitt@unto.net>
Cc: "James M Snell" <jasnell@gmail.com>, "John Cowan" <cowan@ccil.org>, URI <uri@w3.org>

On 11/7/07, DeWitt Clinton <dewitt@unto.net> wrote:
>That it to say, clients and servers assign semantic meaning to the
qualified name
> around the fully qualified name based in the XML namespace declaration.
> And to be really accurate, even the default semantic context (for "searchTerms",
> "count", etc.) comes from the container's default namespace ( i.e.,
> "http://a9.com/-/spec/opensearch/1.1/"), so it really isn't "universally" meaningful
> at all.

Right, which makes me doubt the utility of the namespace prefix. What is
the difference between mapping the "yahoo:" prefix to a namespace
URI and mapping the whole variable name "yahoo_appid" to
a namespace URI? Since one of the design goals is to put control
of the structure of the final URI firmly in the hands of the URI Template
writer I don't think this would cause a problem.

> Joe, please note that, if we agree on this, then the production of
> "template-char" should include the ":" character.

If we do, and to be clear I am biased against it, how should that
be resolved against the 'join' operator?

   yahoo:appid := 123456



> ...
> Hmm, that was a long winded way of saying that qualified names, prefixes,
> and whatnot, are all out of scope.   I just can't see a way to include it
> all elegantly in a single string.  (But would certainly enjoy being shown
> otherwise.)



Joe Gregorio        http://bitworking.org
Received on Thursday, 8 November 2007 17:59:54 UTC

This archive was generated by hypermail 2.4.0 : Sunday, 10 October 2021 22:17:50 UTC