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

[sakimura]

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
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20110708/7421c489/attachment.html>