Padraic Brady has an announcement posted to his blog today - his OpenID PEAR has officially been proposed to the PEAR group for consideration.

Yes, my OpenID 2.0 PHP5 Consumer has finally been proposed to PEAR. This brings the OpenID fanaticism on PEAR to four packages: OpenID_Consumer, Services_Yadis, Crypt_HMAC2, Crypt_DiffieHellman.

He'll be working to get the code "further up to par" including Nonce validation, more consistent error reporting and other operation modes (like check_immediate). He's also included a screencast in the post for those not familiar with OpenID to get their first dose.

Padraic Brady has an announcement posted to his blog today - his OpenID PEAR has officially been proposed to the PEAR group for consideration.

Yes, my OpenID 2.0 PHP5 Consumer has finally been proposed to PEAR. This brings the OpenID fanaticism on PEAR to four packages: OpenID_Consumer, Services_Yadis, Crypt_HMAC2, Crypt_DiffieHellman.

He'll be working to get the code "further up to par" including Nonce validation, more consistent error reporting and other operation modes (like check_immediate). He's also included a screencast in the post for those not familiar with OpenID to get their first dose.

Pádraic Brady has posted a two part look at a service discovery process as it pertains to things like OpenID via Yadis.

From part one:

This first entry is an examination of Yadis, a Specification which is relied upon by OpenID. Of course Yadis is a topic of its own, since it is also used by Light-Weight Identity (LID), sxip Identity, and mIDm. You can bet more will join in once Yadis becomes more firmly established.

In this first part, he talks about what Yadis is, how it can help with service discovery, and how it would follow a "breadcrumb trail" to get to the information it needs (like getting the actual Yadi slocation from the initial OpenID request).

From part two:

After all this fuss and running about, it's easy to miss the point of Yadis - getting that final Yadis XRD document that describes the Services associated with a given ID.

Part two looks more at working with the Yadis Resource Descriptor information to grap the Type information out of it for the actual locations you'll needed. He also links to some more information on the Yadis specification in PDF form.

Pádraic Brady has posted a two part look at a service discovery process as it pertains to things like OpenID via Yadis.

From part one:

This first entry is an examination of Yadis, a Specification which is relied upon by OpenID. Of course Yadis is a topic of its own, since it is also used by Light-Weight Identity (LID), sxip Identity, and mIDm. You can bet more will join in once Yadis becomes more firmly established.

In this first part, he talks about what Yadis is, how it can help with service discovery, and how it would follow a "breadcrumb trail" to get to the information it needs (like getting the actual Yadi slocation from the initial OpenID request).

From part two:

After all this fuss and running about, it's easy to miss the point of Yadis - getting that final Yadis XRD document that describes the Services associated with a given ID.

Part two looks more at working with the Yadis Resource Descriptor information to grap the Type information out of it for the actual locations you'll needed. He also links to some more information on the Yadis specification in PDF form.