[Openid-specs-ab] Developer Feedback
Nat Sakimura
sakimura at gmail.com
Mon Jul 11 22:23:04 UTC 2011
On Tue, Jul 12, 2011 at 5:05 AM, Johnny Bufu <jbufu at janrain.com> wrote:
> On 11-07-11 10:16 AM, Nat Sakimura wrote:
>
>> 1. We should make sure to place HTTP Redirect Binding as the Center Piece.
>> This actually is the confusion that even Breno was falling into. He
>> was thinking that Core was something to be implemented.
>> It is not. It is the HTTP Redirect Binding that the developers
>> should read. We may want to rename it to something more
>> attractive and feel as the main spec. (Perhaps rename core as
>> "Messages" and let the HTTP Binding assume the name
>> "Core" etc.?)
>>
>
Just for the sake of the call:
Mike's suggestion:
Core Messages
Core Bindings
Framework Messages
Framework Bindings
My suggestions are
Basic Messages (for Connect)
Advanced Messages (for Connect)
Basic (HTTP bindings)
Advanced
>
> I too feel that the current number of separate documents makes it harder to
> get the big picture, even though I like modular specs. I guess the
> modularization is not laid out in a way that's easy to get. For example:
>
> - The separation between what is an "abstract" message and what a binding
> is required/allowed to define is not very clear.
>
> - ID Tokens are needed, one way or another (JWT encoded or not) to complete
> a full OpenID-Connect authentication. I'd rather learn about them from Core.
>
> - UserInfo endpoint seems to be covered by both UserInfo and Framework
> specs.
>
>
> 2. Short names are unpopular.
>>
> [...]
>
> Here are my suggestions:
>> inf -> userinfo
>> idt -> id_token
>> clm -> claims
>> fmt -> format
>> mxa -> max_age
>> eaa -> iso29115
>> nor -> unsigned
>> sig -> signed
>> enc -> encrypted
>> aat -> auth_time
>> loc -> locale
>> opt -> optional
>>
>
> +1 if there's no clear technical reason that prevents using these slightly
> longer names.
>
> Johnny
>
--
Nat Sakimura (=nat)
http://www.sakimura.org/en/
http://twitter.com/_nat_en
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20110712/aa825d2e/attachment.html>
More information about the Openid-specs-ab
mailing list