<br><font size=2 face="sans-serif">Andrew - understand your points, but
that can be argued both ways. If I *want* to use SREG, and *want* to advertise
my headphone preference and cannot extend the spec, I am forced to overload
an existing attribute name rather than advertise a more meaningful alternative.
This is exactly what happened in many early deployments of LDAP. And you're
right - no one will care that my implementation doesn't enforce that element
of the spec, and it won't. It's a shame though that some others might,
when that could simply be a deployment-time decision.</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Andrew Arnott"
<andrewarnott@gmail.com></b> </font>
<p><font size=1 face="sans-serif">02/12/2008 07:31 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">Shane B Weeden/Australia/IBM@IBMAU</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">"Eddy Nigg (StartCom Ltd.)"
<eddy_nigg@startcom.org>, general-bounces@openid.net, "general@openid.net"
<general@openid.net></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [OpenID] SREG 1.x attributes</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=3>Shane,<br>
<br>
To limit it explicitly prevents the erosion of the spec by people randomly
making up additional field names and starting to use them in conflict with
each other. If I come up with a "phone" field referring
to headphone preference and you decide to add "phone" and use
it for cell phones then we're obviously in conflict with each other and
our OP/RP will not get along. I like that SREG guarantees this won't
happen by closing itself to extensibility. <br>
<br>
If you are thinking about closed-house special cases where you control
both parties, then party on and extend it if you so desire. No one
else will ever know or care that you aren't implementing SREG according
to the spec. :)<br>
<br>
--<br>
Andrew Arnott<br>
"I [may] not agree with what you have to say, but I'll defend to the
death your right to say it." - Voltaire<br>
<br>
</font>
<br><font size=3>On Mon, Dec 1, 2008 at 1:20 PM, Shane B Weeden <</font><a href=mailto:sweeden@au1.ibm.com><font size=3 color=blue><u>sweeden@au1.ibm.com</u></font></a><font size=3>>
wrote:</font>
<br><font size=2 face="sans-serif"><br>
Just to be clear - I am not asking for more work to be done on defining
other SREG attribute types and names, I am simply asking for the spec not
to dictate that the listed attributes in section 4 are the ONLY allowed
attributes. There seems no logical reason to do so and it may result in
open source (and other) libraries implementing restrictions which offer
no benefits to consumers and may make some deployments harder. I really
didn't think it would be a big deal.</font><font size=3> <br>
<br>
<br>
<br>
</font>
<table width=100%>
<tr valign=top>
<td width=54%><font size=1 face="sans-serif"><b>"Eddy Nigg (StartCom
Ltd.)" <</b></font><a href=mailto:eddy_nigg@startcom.org target=_blank><font size=1 color=blue face="sans-serif"><b><u>eddy_nigg@startcom.org</u></b></font></a><font size=1 face="sans-serif"><b>></b>
</font>
<br><font size=1 face="sans-serif">Sent by: </font><a href="mailto:general-bounces@openid.net" target=_blank><font size=1 color=blue face="sans-serif"><u>general-bounces@openid.net</u></font></a><font size=3>
</font>
<p><font size=1 face="sans-serif">02/12/2008 05:33 AM</font><font size=3>
</font>
<td width=45%>
<br>
<table width=100%>
<tr valign=top>
<td width=14%>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td width=85%><font size=1 face="sans-serif">"</font><a href=mailto:general@openid.net target=_blank><font size=1 color=blue face="sans-serif"><u>general@openid.net</u></font></a><font size=1 face="sans-serif">"
<</font><a href=mailto:general@openid.net target=_blank><font size=1 color=blue face="sans-serif"><u>general@openid.net</u></font></a><font size=1 face="sans-serif">></font><font size=3>
</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [OpenID] SREG 1.x attributes</font></table>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=50%>
<td width=50%></table>
<br></table>
<br><font size=3><br>
<br>
</font>
<br><tt><font size=2>On 12/01/2008 09:02 PM, Martin Atkins:<br>
> Eddy Nigg (StartCom Ltd.) wrote:<br>
>><br>
>> On 12/01/2008 07:58 PM, David Recordon:<br>
>>> </font></tt><a href=http://www.axschema.org/types/ target=_blank><tt><font size=2 color=blue><u>http://www.axschema.org/types/</u></font></tt></a><tt><font size=2><br>
>>><br>
>>><br>
>><br>
>> So it would be fairly easy to extend exactly according to these
types <br>
>> and everybody is happy....or am I missing something?<br>
>><br>
><br>
> It already has been extended according to these types. We called it
<br>
> Attribute Exchange. :)<br>
<br>
Can you explain the call for extending SREG then and why AX isn't widely
<br>
implemented anywhere as far as I can tell? Or maybe that's the wrong <br>
conclusion?<br>
<br>
<br>
</font></tt>
<br><tt><font size=2>[attachment "smime.p7s" deleted by Shane
B Weeden/Australia/IBM] _______________________________________________</font></tt>
<br><tt><font size=2><br>
general mailing list</font></tt><tt><font size=2 color=blue><u><br>
</u></font></tt><a href=mailto:general@openid.net target=_blank><tt><font size=2 color=blue><u>general@openid.net</u></font></tt></a><tt><font size=2 color=blue><u><br>
</u></font></tt><a href=http://openid.net/mailman/listinfo/general target=_blank><tt><font size=2 color=blue><u>http://openid.net/mailman/listinfo/general</u></font></tt></a>
<br><font size=3><br>
<br>
_______________________________________________<br>
general mailing list</font><font size=3 color=blue><u><br>
</u></font><a href=mailto:general@openid.net><font size=3 color=blue><u>general@openid.net</u></font></a><font size=3 color=blue><u><br>
</u></font><a href=http://openid.net/mailman/listinfo/general target=_blank><font size=3 color=blue><u>http://openid.net/mailman/listinfo/general</u></font></a><font size=3><br>
</font>
<br>
<br>