The Progress Bar read by people interested in emerging Internet marketing, technology, social media, reputation, virtual environments, blogs, the Boston Internet scene and much more. If you like what you see you should subscribe to my RSS feed or via email in the sidebar. Thanks for visiting!
Johan mentions conceptual models for storing identity data, which got me thinking about where all my data is going to be stored. Right now it’s a poorly-distributed hogepodge strewn all over the net.
Hans Gerwitz envisions asking another website for access to a third-party ID nuggets. He see publishing his PersonCode in Plazes, and then having his Yelp profile ask Plazes for his PersonCode. This seems a bit too distributed to me.
If I tag all of my Plazes and Flickr stuff with my MicroID and/or ClaimID, they could expose either via their API. Why not parse an extended FOAF file in a centralized or distributed silo?
It seems like to much work to have all these chained requests. Easier to make requests from a hub like PA or Ikarma or Opinity or Trufina for that matter.
PeopleAggregator is leaning in this direction, the beta is a few weeks away. PA has been going since 2003 and it looks like something is about to be actually deployed. Appears they are going to support everything under sun, which makes good copy yet the devil is in the integration.
