[OpenID] SREG 1.x attributes

[Eddy Nigg (StartCom Ltd.)]

On 11/29/2008 11:39 AM, Shane B Weeden:
>
> Can anyone explain why the SREG 1.x specifications state:
>
> /A single field MUST NOT be repeated in the response, and all included 
> fields MUST be taken from the set of fields defined in this 
> specification./
>
> In particular I can't see the reasoning behind the "all included 
> fields MUST be taken from the set of fields defined in this 
> specification". Why not allow the set of attributes to be extended 
> arbitrarily if parties so desire, e.g.
>
> openid.sreg.hertz.goldnumber
>
> Now that's just an example, but I see no reason for the specification 
> to dictate the set of allowable attributes when it's quite a simple 
> matter to make it extensible. I realize that efforts are made to 
> define a common schema, and that's great, but the spec shouldn't limit 
> itself to that schema.
>

Which is probably because AX was supposed to take care of it. However 
SREG is widely implemented and I agree that we should make it possible 
to easily extend SREG.

+1


Regards
Signer: 	Eddy Nigg, StartCom Ltd. <http://www.startcom.org>
Jabber: 	startcom at startcom.org <xmpp:startcom at startcom.org>
Blog: 	Join the Revolution! <http://blog.startcom.org>
Phone: 	+1.213.341.0390


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20081129/215aa4d4/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6724 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20081129/215aa4d4/attachment-0002.bin>