[Openid-specs-ab] Spec call notes 5-Jul-11

[Nat Sakimura]

I suppose it is a good time to start working on developer white paper as
well.

It should be very simple, like Facebook Canvas app developer page.

http://developers.facebook.com/docs/authentication/signed_request/
http://developers.facebook.com/docs/authentication/

I expect that is something most developers will be looking at when they are
writing code.

=nat

On Wed, Jul 6, 2011 at 8:16 AM, Mike Jones <Michael.Jones at microsoft.com>wrote:

>  Spec call notes 5-Jul-11****
>
> ** **
>
> Mike Jones****
>
> Edmund Jay****
>
> John Bradley****
>
> Johnny Bufu****
>
> Nat Sakimura****
>
> George Fletcher****
>
> ** **
>
> Agenda:****
>
>                 Discovery and Client Registration specs****
>
>                 Incorporating http binding into core/framework****
>
>                 Consistency pass****
>
>                 Contacting developers****
>
>                 Declaring implementers drafts****
>
>                 Encryption****
>
>                 IETF meeting****
>
>                 Spec primer****
>
> ** **
>
> Discovery and Simple Client Registration specs****
>
>                 John published these this afternoon****
>
>                 He needs to go over the specs to confirm that the term
> usage is consistent****
>
>                 Mike asked whether the comma separated lists should be
> space separated instead****
>
>                 George asked whether they should be JSON arrays****
>
>                 We agreed to make that change****
>
>                 Add openid_version string to provider configuration
> response****
>
>                                 Version string will be "3.0"****
>
>                 John asked whether the response should contain the issuer*
> ***
>
>                                 We thought yes****
>
>                 George asked whether the openid-configuration needs to be
> in .well-known, as adding these can be hard****
>
>                                 We decided to publish this with
> .well-known/openid-configuration, since that was the WG consensus****
>
>                 Change http://openid.net/specs/cc/1.0/issuer to
> http://openid.net/specs/connect/1.0/issuer****
>
>                 Change eaa to iso_29115****
>
>                 Change list of return_to URIs to a JSON array****
>
>                 We asked Nat to look at internationalization for the simple
> client registration spec****
>
>                 John will change the registration request to a JSON object
> ****
>
>                 Delete "to be" after "application_name"****
>
>                 Change example to a different endpoint - maybe including
> "/register"****
>
>                                 And make examples consistent with discovery
> spec as well****
>
>                 Mike will post docs as-is, John will produce updated
> versions****
>
> ** **
>
> Incorporating http binding into core/framework****
>
>                 Mike won't start this until after an encryption draft is
> done****
>
> ** **
>
> Consistency pass****
>
>                 We should all do a consistency pass over the specs before
> Thursday's call****
>
> ** **
>
> Contacting developers****
>
>                 After John's specs are posted and edited as above, it's
> time to contact friendly developers****
>
> ** **
>
> Declaring implementers drafts****
>
>                 We won't declare formal implementers drafts until
> implementers have beat on the specs a bit****
>
> ** **
>
> Encryption****
>
>                 Mike is working on a draft to begin receiving expert review
> feedback****
>
> ** **
>
> IETF meeting****
>
>                 We should have a face-to-face meeting in Quebec City****
>
> ** **
>
> Spec primer****
>
>                 We need a primer/overview on the set of specs****
>
>                                 Saying what order to read specs, what
> relationships between them are****
>
>                 Start with Core, UserInfo, Framework, then HTTP Redirect**
> **
>
>                                 Soon Discovery and Simple Client
> Registration as well****
>
> ** **
>
> Next call****
>
>                 The next call will be on Thursday (US) / Friday (Japan) at
> the regular time****
>
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-ab
>
>


-- 
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/20110706/e0958dc4/attachment.html>