Group items tagged

I’m sure some folks are wondering exactly what this means. Even though I was close to the decision making around this, I believe it is still too early to tell. Personally, I share Marc Canter’s skepticism about Dataportability.org given that so far there’s been a lot of hype but no real meat.

As far as I can tell, Dataportability.org seems like a good forum for various social software vendors to start talking about how we can get to a world where there is actual interoperability between social software applications. I’d like to see real meat fall out of this effort not fluff. One of the representatives Microsoft has chosen is the dev lead from the product team I am on (Inder Sethi) which implies we want technical discussion of protocols and technologies not just feel good jive. We’ll also be sending a product planning/marketing type as well (John Richards) to make sure the end user perspective is also being covered. You can assume that even though I am not on the working group in person, I will be there in spirit since I communicate with both John and Inder on a regular basis.

All very wonderful, right? Well, maybe not - as some SEOs and webmasters say. Their main concern is that by providing such a structured format of their content - content scrapers will need very little skill in stealing their content and repurposing it in a useful manner. SEOs and webmasters don't mind Yahoo getting this data from them, but they know that leaving this easy to use and structured format open to Yahoo will also give anyone else access to their data. Same issue with XML but this is even more fine tuned data, because webmasters can detail minute details about their content

The next trick will be building awareness and adoption. When you consider that 0% of all websites (or enterprise apps) accept i-cards or OpenID, and 0% of sites issue cards, it’s small wonder that 0% of users today even know what an identity selector is. We’ve got our work cut out for us!

What is needed though is a discussion about this and what the best practices in these cases should be. One option would be the opt-in for such XFN-markup but of course those links would still be available although not that easily extractable. Making it more private would probably harm the site’s usefulness. Removing them might also harm social services such as dopplr which make good use of them to find your contacts on dopplr.

So it’s many questions to be answered and I wonder what a good process might be to answer them. Surely there is the  around but of course they cannot just publish guidelines and the problem is solved. A broader discussion is needed and for a start maybe an exact description of the problem and coming from these some proposals to solve it.