Re: [webfinger] feedback for multiple "rel"

Understood.
I saw the same debate in OAuth2 ML and saw opposite result :p

I, as a ruby library developer, prefer single "rel" because parsing double encoded values in library is easier than modifying developer's application framework.
But at same time, as OpenID Connect library developer, it's probably too late to change webfinger spec ... :(

On 2012/12/22, at 14:18, Paul E. Jones <paulej@packetizer.com> wrote:

> Nov,
> 
> It used to base space-delimited in the -02 draft:
> http://tools.ietf.org/html/draft-ietf-appsawg-webfinger-02#section-5.3
> 
> We had a debate over this and, as usual, I lost. :-)
> 
> Some people expressed concerns that there might be spaces in the URL, so
> taking two URLs like this:
> 
> http://example.com/this one
> http://example.com/that one
> 
> And then putting them into the "rel" parameter like this:
> 
> http%3A%2F%2Fexample.com%2Fthis%20one%20http%3A%2F%2Fexample.com%2Fthat%20on
> e
>                               ^^^   ^^^
> 
> The ^^^ denotes the problem.
> 
> Unescaping and splitting on spaces would give you 4 values.
> 
> So, one has to do this:
> encodeURIComponent(
>   encodeURIComponent ("http://example.com/this one") + " " +
>   encodeURIComponent ("http://example.com/that one") )
> 
> And put that into the "rel" parameter.
> 
> That can get a bit ugly.  I personally preferred the single rel parameter,
> though.  I was overruled.
> 
> Perhaps you might be more persuasive than I was.
> 
> Paul
> 
>> -----Original Message-----
>> From: webfinger-bounces@ietf.org [mailto:webfinger-bounces@ietf.org] On
>> Behalf Of nov matake
>> Sent: Friday, December 21, 2012 11:49 PM
>> To: webfinger@ietf.org
>> Subject: [webfinger] feedback for multiple "rel"
>> 
>> Hi,
>> 
>> I have a comment for they way to specify multiple "rel" values.
>> 
>> As a ruby library developer, my main target is rails developers.
>> Since rails can't handle multiple same query keys, developers will need
>> to hack query params parser in rails middleware layer.
>> I can easily imagine it'll be an annoying part to support webfinger in
>> rails.
>> 
>> Is the multiple "rel" case can be a space-delimitered (or some other
>> character) strings like multiple redirect_uri in OAuth2?
>> Or any reason for putting multiple same keys in query parameters?
>> 
>> Cheers,
>> 
>> Nov Matake
>> _______________________________________________
>> webfinger mailing list
>> webfinger@ietf.org
>> https://www.ietf.org/mailman/listinfo/webfinger
> 