<HTML>
<HEAD>
<TITLE>Re: Requiring Pseudonymous Identifier</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Agreed. If all you want is a group, then I’d think that the response would just not include an identifier.<BR>
<BR>
You could use an extension, perhaps AX, to request information about the group a user belongs to.<BR>
<BR>
For example, if you wanted to understand company membership, you could request and return only <a href="http://axschema.org/company/name">http://axschema.org/company/name</a>. <BR>
<BR>
On 5/12/09 11:08 PM, "Martin Atkins" <<a href="mart@degeneration.co.uk">mart@degeneration.co.uk</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Chris Messina wrote:<BR>
><BR>
> So, imagine I use directed identity in a school application... when I sign<BR>
> in to the OP, it will return something like schoolname.edu/student as the<BR>
> identifier.<BR>
><BR>
<BR>
Overloading our existing concept of an identifier to support identifying<BR>
a group worries me. Most consumers expect an identifier to be for a<BR>
person and are designed around this principle.<BR>
<BR>
I think if groups are useful their design should be different such that<BR>
consumers are able to distinguish between a user and a group.<BR>
<BR>
_______________________________________________<BR>
specs mailing list<BR>
<a href="specs@openid.net">specs@openid.net</a><BR>
<a href="http://openid.net/mailman/listinfo/specs">http://openid.net/mailman/listinfo/specs</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>