Comments on: hCard Overflow: Could We Use rel-hcard?

By: Adam Darowski

Adam Darowski — Sun, 28 Jan 2007 00:27:25 +0000

Hey Stephen… I wasn’t familiar with Wikidentity… looks pretty cool. I guess as apps start being developed, they will become even smarter in terms of combining data. Perhaps checking timestamps to find the most recent data, etc.

By: Stephen Paul Weber

Stephen Paul Weber — Sat, 27 Jan 2007 16:19:24 +0000

Some services (such as Wikidentity) also intelligently determine if two hCards are the same person and combine them in the search results (ie, searching for people instead of single hCards)

By: Adam Darowski

Adam Darowski — Thu, 25 Jan 2007 19:55:08 +0000

Hey Nick, thanks for stopping by. Did you see Brian’s link at the end of my post? He not only presents a very elegant solution, but also has a series of links for more research.

By: Nick Peters

Nick Peters — Thu, 25 Jan 2007 19:26:26 +0000

I agree 100% with you! I think that over-hcarding leaves for a lot of incomplete and inconsistent data. In order to solve this, a person’s information has to be consolidated to one source. I also had the idea of using a rel-hcard, but I feel that the use of OpenID is the way to go. I’m currently researching it, but I think you can store personal information about yourself on the OpenID server, retrieve that information and then turn that into an hCard.

By: OpenID, Portable Social Networks and the Darowski Problem at Like It Matters

OpenID, Portable Social Networks and the Darowski Problem at Like It Matters — Tue, 23 Jan 2007 19:14:42 +0000

[...] I can also use OpenID to overcome what I’ll call the Darowski problem, after Adam’s post on this. The problem is managing the proliferation of identity information. Adam gives the example of finding 258 hCard listings for me using Technorati’s microformats search engine. With OpenID, I could anchor an hCard on my site and tell search engines and other services that this is the ‘gold’ hCard I want used for my contact information. What I change here should be thought of as current, and I want all services to pull from that. [...]