[Specs-cx] The remaining items

[hideki nara]

Topics can be the followings:

 - Multiple tokens for a single Connect session :  may be covered in "to
define the claims structure only".
 - Token validation by  the Protected Resources other than OAuth Servers :
UMA may cover this.
 - Delegations(?) ( Delivering access tokens to Clients other than RP which
initiates a Connect session )
 - Notification..

Any others ?
--
hdknr

2011/10/22 Nat Sakimura <sakimura at gmail.com>

> So, much of the earlier Contract Exchange work (underlying protocol) were
> taken up by the new Connect protocol.
> This means that the remaining bit of things that this working group has to
> do is to define the claims structure only, which is good.
> In the past, we have been talking about it in XML but as Connect is
> completely JSON based, perhaps we should try to convert it to JSON as well.
>
> It should not be too difficult to do.
>
> Also, there are related protocols like open-transact being proposed
> elsewhere. Perhaps we shall look at it as well.
>
> Thoughts?
>
> --
> Nat Sakimura (=nat)
> Chairman, OpenID Foundation
> http://nat.sakimura.org/
> @_nat_en
>
>
> _______________________________________________
> Specs-cx mailing list
> Specs-cx at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-cx
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-cx/attachments/20111026/e42120bb/attachment.html>