OpenID 2.0 finalization progress

[Johannes Ernst]

My understanding is that we need to get the IPR process finalized,  
then cross all the t's and dot the i's from the intellectual property  
perspective for the 2.0 spec(s), and then declare 2.0 to be final.

Would be too embarrassing if we declared a spec final and then  
discovered that it did not meet our own IPR requirements re patents,  
for example, wouldn't it?


On Oct 15, 2007, at 16:00, Dick Hardt wrote:

> +1
>
> On 15-Oct-07, at 3:02 PM, Josh Hoyt wrote:
>
>> Hello fellow OpenID spec participants,
>>
>> As I wrote in August [1], it's time to get the specification declared
>> final. We've had quite a while now for implementations and
>> specification feedback. Here at JanRain, we've implemented the draft
>> specification in Python [2] and PHP [3], and I know that the folks at
>> Sxip have implemented and deployed it in Java [4]. I know that at
>> least those implementations have beed tested against each other, and
>> worked successfully. I haven't heard of any new spec issues raised
>> from implementation.
>>
>> As such, I am in favor of declaring Draft 12 the final draft and
>> blessing it as OpenID 2.0.
>>
>> Do the other specification editors agree that now is the time to
>> declare OpenID 2.0 finished?
>>
>> Josh Hoyt <josh at janrain.com>
>> OpenID: http://j3h.us/
>>
>> 1. http://openid.net/pipermail/specs/2007-August/001953.html
>> 2. http://openidenabled.com/python-openid/
>> 3. http://openidenabled.com/php-openid/
>> 4. http://code.google.com/p/openid4java/
>> _______________________________________________
>> specs mailing list
>> specs at openid.net
>> http://openid.net/mailman/listinfo/specs
>>
>>
>
> _______________________________________________
> specs mailing list
> specs at openid.net
> http://openid.net/mailman/listinfo/specs