<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:Courier New,courier,monaco,monospace,sans-serif;font-size:10pt"><div style="font-family: tahoma,new york,times,serif;">It was decided in the last conference call, that the current schema will remain unchanged until we have further feedback and information.<br>But as question to the WG, should we make a suggestion/recommendation in the spec for authorization servers to implement the profile picture retrieval URL to implement functionality as Allen describes?<br>An issue was brought up in the conference all that this will only work if the authorization servers hosted the pictures. If the URL points to a third party site, it is unknown what you will get back.<br>Perhaps, this field should not be a user update-able field and the URL is generated by the server from user's uploaded profile pictures?<br><br><br>-- Edmund<br><br><br></div><div
style="font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:10pt"><br><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Allen Tom <allentomdude@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> Andreas Åkre Solberg <andreas.solberg@uninett.no><br><b><span style="font-weight: bold;">Cc:</span></b> openid-specs-ab@lists.openid.net<br><b><span style="font-weight: bold;">Sent:</span></b> Fri, August 26, 2011 11:33:18 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [Openid-specs-ab] Spec call notes 25-Aug-11<br></font><br>Hi Andres,<div><br></div><div>I think it is important that the user's profile picture be available in multiple sizes, so I'm glad that the WG is considering this.</div><div><br></div><div>I don't think that clients should specify the size using the
Accept HTTP header, since some clients (like javascript clients) may not be able to easily set the header. It looks like Gravatar, Twitter, and Facebook all use the technique of specifying a base image URL, with an optional size parameter. This sounds like a reasonable approach.</div>
<div><br></div><div>Gravatar </div><div>(default: 80x80) <a rel="nofollow" target="_blank" href="http://www.gravatar.com/avatar/2c421806d83cb83b2981933e8efa6e8e">http://www.gravatar.com/avatar/2c421806d83cb83b2981933e8efa6e8e</a></div><div>(arbitary size - always square format though) <a rel="nofollow" target="_blank" href="http://www.gravatar.com/avatar/2c421806d83cb83b2981933e8efa6e8e?s=250">http://www.gravatar.com/avatar/2c421806d83cb83b2981933e8efa6e8e?s=250</a></div>
<div><br></div><div>Twitter</div><div><a rel="nofollow" target="_blank" href="http://api.twitter.com/1/users/profile_image?screen_name=atom">http://api.twitter.com/1/users/profile_image?screen_name=atom</a></div><div><a rel="nofollow" target="_blank" href="http://api.twitter.com/1/users/profile_image?screen_name=atom&size=original">http://api.twitter.com/1/users/profile_image?screen_name=atom&size=original</a></div>
<div><br></div><div>Facebook</div><div><a rel="nofollow" target="_blank" href="https://graph.facebook.com/allentom/picture">https://graph.facebook.com/allentom/picture</a></div><div><a rel="nofollow" target="_blank" href="https://graph.facebook.com/allentom/picture?type=large">https://graph.facebook.com/allentom/picture?type=large</a></div>
<div><br></div><div>I had proposed that the OpenID Connect profile picture be returned using a base URL. The default size can be left undefined, but clients are able to optionally specify the desired size using an optional parameter. In order to avoid having to specify what "small/medium/large/x-large" means, we can do something like gravitar and let the client specify the size in pixels.</div>
<div><br></div><div>Allen</div><div><br></div><div><br></div><div><br></div><div><br><br><div class="gmail_quote">2011/8/26 Andreas Åkre Solberg <span dir="ltr"><<a rel="nofollow" ymailto="mailto:andreas.solberg@uninett.no" target="_blank" href="mailto:andreas.solberg@uninett.no">andreas.solberg@uninett.no</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word;"><div class="im"><br><div><div>On 26. aug.2011, at 03:19, Edmund Jay wrote:</div><br>
<blockquote type="cite"><span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium;"><span style="font-family:tahoma,;font-size:13px;">John offered the following options:<br>
a) new scope for requesting picture sizes<br>b) RP makes explicit claim request<br>c) Expand schema to include "small", "medium", and "large"<br></span></span></blockquote></div><br></div><div>
BTW, here is how gravatar is doing this:</div><div><br></div><div><span style="white-space:pre-wrap;"> <a rel="nofollow" target="_blank" href="http://en.gravatar.com/site/implement/images/#size">http://en.gravatar.com/site/implement/images/#size</a></span></div>
<div><br></div><div>(I'm not saying that I neccessary like it, I just include it as an example).</div><div><br></div><div>A related topic, is content type negotiation. Would it be an idea to suggest to use 'Accept' header as the reccomended way of negotiating which image format that is presented?</div>
<div><br></div><div><div> Accept: image/gif;q=0.5, image/jpeg;q=0.8, image/png;q=0.9, image/svg+xml;q=1.0</div><div><br></div><div>I would propose that if we say anything about accept parameters and/or size parameters, it would just be reccomendations to providers that would like to offer multiple formats and sizes; and not a requirement.</div>
<div><br></div><font color="#888888"><div>Andreas</div><div><br></div></font></div></div><br>_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a rel="nofollow" ymailto="mailto:Openid-specs-ab@lists.openid.net" target="_blank" href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><br>
<a rel="nofollow" target="_blank" href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
<br></blockquote></div><br></div>
</div></div>
</div></body></html>