[Openid-specs-ab] Framework: 3.1.1. OpenID Request Object clarification

Nat Sakimura sakimura at gmail.com
Mon Jul 11 15:42:13 UTC 2011


Attached please find the edited XML.

=nat

On Fri, Jul 8, 2011 at 7:26 PM, Mike Jones <Michael.Jones at microsoft.com>wrote:

>  I agree with all of these changes.  Thanks for volunteering to do the XML
> edits!****
>
> ** **
>
>                                                             Cheers,****
>
>                                                             -- Mike****
>
> ** **
>
> *From:* openid-specs-ab-bounces at lists.openid.net [mailto:
> openid-specs-ab-bounces at lists.openid.net] *On Behalf Of *sakimura
> *Sent:* Friday, July 08, 2011 2:12 AM
> *To:* openid-specs-ab at lists.openid.net
> *Subject:* [Openid-specs-ab] Framework: 3.1.1. OpenID Request Object
> clarification****
>
> ** **
>
> *3.1.1.  OpenID Request Object*****
>
> ** **
>
> It is not clear if "idt" member may include "fmt" sub-member. ****
>
> I think the intent of the following paragraph is "yes", but is vague. We should clarify the para. ****
>
> ** **
>
> Draft 02: ****
>
> ** **
>
> The structure and function of the "idt" (ID Token request) member of the OpenID Request object is similar to that of the "inf" member. It also contains an optional "clm" member, with the same structure as that for the "inf" member. If the "clm" member is present in the "idt" object, the claims requested within it modify the default claim set that would otherwise be returned in the ID Token. Unlike for the "inf" member, typically these claims will augment, rather than override the default set.****
>
> ** **
>
> Rewrite proposal: ****
>
> ** **
>
> The structure and function of the "idt" (ID Token request) member of the OpenID Request object is similar to that of the "inf" member. It MAY include "clm", "fmt", "loc". The same structure of these members are the same as that for the "inf" member. If the "clm" member is present in the "idt" object, the claims requested within it modify the default claim set that would otherwise be returned in the ID Token. Unlike for the "inf" member, typically these claims will augment, rather than override the default set.****
>
> ** **
>
> If it is the intent, I will provide the XML edit. ****
>
> ** **
>
> Also, if a little more extensive edit is allowed at this time, I would like to propose sub-sectioning 3.1.1 so that it will look like: ****
>
> ** **
>
> *3.1.1. OpenID Request Object*****
>
> *3.1.1.1. "inf" member*****
>
> *3.1.1.2. "idt" member*****
>
> ** **
>
> It should make the section much more readable. ****
>
> ** **
>
> If the working group agrees, I will also provide the edit. ****
>
> ** **
>
> =nat****
>
>


-- 
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/26eedc7d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openid-connect-framework-1_0.xml
Type: text/xml
Size: 47977 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20110712/26eedc7d/attachment-0001.xml>


More information about the Openid-specs-ab mailing list