<br><font size=2 face="sans-serif">I don't have any problem with the development
and promotion of AX. The point was simply that we have an SREG 1.1 spec
in draft, and I can't see any good reason for it to include in the 6th
paragraph of section 4 ", and all included fields MUST be taken from
the set of fields defined in this specification." It appears to be
boxing something in that simply doesn't require a box. There are plenty
of intranet or 1:1 partner scenarios where OpenID with flexible SREG is
an equally viable, and arguably simpler solution. </font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br><font size=2 face="sans-serif">Shane.</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>David Recordon <drecordon@sixapart.com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: general-bounces@openid.net</font>
<p><font size=1 face="sans-serif">01/12/2008 07:29 AM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
david@sixapart.com</font></div></table>
<br>
<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">Peter Williams <pwilliams@rapattoni.com>,
"Eddy Nigg (StartCom Ltd.)" <eddy_nigg@startcom.org>, "general@openid.net
>> general@openid.net" <general@openid.net></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>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>I think it's far more of a timing thing. SREG
has been supported by <br>
the majority of smaller OpenID Providers and thus some Relying <br>
Parties. The large Providers (AOL and Yahoo!) didn't provide support
<br>
for either spec. Google now supports AX and MySpace is planning to
as <br>
well. AX will overtime become prevalent as more OPs provide data
via <br>
it.<br>
<br>
This is why I believe that we should fix SREG to work with 2.0 though <br>
focus effort on adoption of AX.<br>
<br>
--David<br>
<br>
On Nov 30, 2008, at 1:13 PM, Peter Williams wrote:<br>
<br>
> I suspect ax is not too popular as it competes with ldap/ldif - and
<br>
> has no real reason to exist. The pain of making yet another <br>
> attribute schema (for what?) is high.<br>
><br>
> Best if one extends sreg - one field that can deliver an lidf <br>
> stream. Ldif is the sytax, and existing ldap schemas can be used.
<br>
> Extensibility is then handled within the ldap world.<br>
><br>
> -----Original Message-----<br>
> From: Eddy Nigg (StartCom Ltd.) <eddy_nigg@startcom.org><br>
> Sent: Sunday, November 30, 2008 1:09 PM<br>
> To: general@openid.net >> general@openid.net <general@openid.net><br>
> Subject: Re: [OpenID] SREG 1.x attributes<br>
><br>
> On 11/30/2008 12:39 AM, Martin Atkins:<br>
> Eddy Nigg (StartCom Ltd.) wrote:<br>
><br>
> Which is probably because AX was supposed to take care of it. However<br>
> SREG is widely implemented and I agree that we should make it possible<br>
> to easily extend SREG.<br>
><br>
><br>
> If you make it possible to extend SREG, what you end up with is AX
<br>
> with<br>
> a few predefined attributes baked into the spec and no ability for
<br>
> those<br>
> attribute to be updated by third-parties.<br>
><br>
> I'm not sure anyone actually uses the ability for the attributes to
be<br>
> updated by third-parties, so for all intents and purposes you'd just
<br>
> be<br>
> reinventing AX as far as I can tell.<br>
><br>
> Yes, I mentioned that AX is supposed to take care of this.<br>
><br>
> What do you see as the value of having two parallel specs that both
<br>
> have<br>
> the same functionality apart from one having a feature that no-one
<br>
> uses?<br>
> (or are you proposing that SREG would replace AX altogether?)<br>
><br>
> But one might ask, why SREG has become popular (if we can speak <br>
> about popularity in terms of OpenID ;-) ), whereas AX isn't widely
<br>
> implemented as far as I can tell. Maybe it's because of the pre- <br>
> defined fields or because of its simplicity, I don't know. But <br>
> something tells me that SREG has been successful, why not extend it
<br>
> in some form.<br>
><br>
><br>
> Regards<br>
><br>
> Signer:<br>
> Eddy Nigg, StartCom Ltd.<br>
> Jabber:<br>
> startcom@startcom.org<br>
> Blog:<br>
> Join the Revolution!<br>
> Phon<br>
><br>
> [The entire original message is not included]<br>
> _______________________________________________<br>
> general mailing list<br>
> general@openid.net<br>
> http://openid.net/mailman/listinfo/general<br>
<br>
<br>
_______________________________________________<br>
general mailing list<br>
general@openid.net<br>
http://openid.net/mailman/listinfo/general<br>
</font></tt>
<br>