Re: URI Templates - optional variables?

Am 30.07.2007 um 19:55 schrieb Mike Schinkel:
> 1.) http://www.example.com/{foo?}/
>
> For foo="bar", URL=  http://www.example.com/bar/
> For foo="" or foo=null, URL=  http://www.example.com/  (no double
> forward-slash)

I think it would make sense to say that a template to uri converter  
MUST perform path resolution as described in RFC 3986 ch. 5.2.3 and  
5.2.4. That will also stop some injections of "." and ".." into URIs  
while saving the client from worrying to much about double "/" and such.

> 2.) http://www.example.com/?foo={foo?}
>
> For foo="bar", URL=  http://www.example.com/?foo=bar
> For foo="" or foo=null, URL=  http://www.example.com/  (no question  
> mark)

This alone will not work. There is a difference between an absent and  
an empty parameter for some applications (e.g. they want to see  
"http://www.example.com/?foo=" ).

Cheers,

Stefan