Re: Mixing template variable vocabularies?

Joe Gregorio scripsit:

> > > {,&|name,"http://example.com/location",age}
> > >
> > > Simple, and gives us some wriggle room down the road.
> 
> -1
> 
> It makes the parser way more complicated than it needs to be.
> Even if it didn't make the parser more complicated
> I don't believe "wriggle room down the road" is a compelling
> reason to add something to a specification.

I agree with Joe.  URIs are meant to have absolute meaning, which is
why they need to be absolute names, the same in every context.
Template variable names only make sense in the local context of
the template or set of templates which are evaluated against them.
Local names are plenty good enough.

For IRI templates, we could allow iunreserved characters in
the variable names, which would allow for internationalized identifiers.

-- 
What is the sound of Perl?  Is it not the       John Cowan
sound of a [Ww]all that people have stopped     cowan@ccil.org
banging their head against?  --Larry            http://www.ccil.org/~cowan

Received on Saturday, 20 October 2007 18:41:59 UTC