A few weeks ago, I emailed Johannes Ernst, asking him how (if at all) he saw lightweight URL-based ID management technologies like LID being used to express group membership semantics. As he promised, he’s put together a long post on group implementation in LID, which answers my questions.

On the plus side, I’m encouraged to see that this type of use case has been on the minds of the ID management players for at least a year, and that they recognize at least as clearly as I do how powerful this concept could be.

Another weekend project idea is to investigate the implementation of an ASP.NET Membership Provider that supports LID/OpenID/Yadis identities. There’s an existing OpenID implementation for .NET, implemented in Boo, but you have to wire it up to your app yourself. A membership provider would be more drop-in, assuming the lightweight URL-based identity idioms can be shoe-horned into the fairly narrow membership provider API.

In a previous post on emerging ID management technologies I came to a few conclusions about these lightweight URL-based technologies that were subsequently corrected in an email conversation with Johannes Ernst.