- From: James M Snell <jasnell@gmail.com>
- Date: Wed, 07 Nov 2007 12:19:09 -0800
- To: John Cowan <cowan@ccil.org>
- CC: Joe Gregorio <joe@bitworking.org>, URI <uri@w3.org>
The main use case is to allow standardization and disambiguation of
varnames. You can look at OpenSearch for an example of this in the real
world. Local names are indeed more readable, but they can be ambiguous.
For instance, suppose we want to standardize an approach for searching
in feeds. As part of that, we want to define querystring params with
defined semantics: q, start and count. I want to be able to indicate,
unambiguously, that the query params I want the user to pass in are the
"q", "start" and "count" params as defined by the standard.
What needs to be decided now is whether or not this is a problem we need
to solve. If not, local names are perfectly fine.
- James
John Cowan wrote:
>>[snip]
>> For instance, allowing : and / would allow us to do...
>>
>> {-prefix|foo/|http://example.org/text/username}
>
> I don't understand what application scenario would call for
> the use of universal names in templates. It seems to me
> that local names are sufficient (and more readable; it's
> much easier to see where the varname stops if it looks
> like an identifier).
>
>> Also, there had been mention of an escape/quote character for varnames,
>
> I have the same question: for what?
>
Received on Wednesday, 7 November 2007 20:19:23 UTC