Tag Archives: hcard

try { reuse; } catch (Ex) { reinvent; }

Earlier today, I wrote about the limitations of hCard primarily in regards to private data. After talking with Chris briefly and then reading Tantek’s thoughts on the topic, it clicked with me. I wouldn’t normally make two posts so close together about such similar topics, but I realize now these really are two different topics. […]

hCard is not a provisioning engine (for private data)

Last week I wrote about how hCard is much more appropriate than OpenID for the provisioning use-case and Chris continued that discussion, questioning why we need SREG and Attribute Exchange when hCard works just fine. So the question is, when OpenID is clearly a player in the future and part of that promise is about […]

OpenID is not a provisioning engine

In talking about the future possibilities of OpenID 2.0 and the Attribute Exchange extension, James Henstridge mentions, Imagine being able to update your shipping address in one place when you move house and having all the online retailers you use receive the updated address immediately. Or changing your email address and having all the bugzilla […]