Group items matching

in title, tags, annotations or url

The DataPortability initiative just released their report for the month of January. I love the open approach the group has embraced to share the issues, highlights, and progress with the community.

The Good: The work is being broken down into a bunch of action groups to help get the teams organized and break the work into manageable chunks.

The Bad: Like many similar efforts, the big vendors agree to participate and make a lot of noise about it, but they haven’t all been doing the real work necessary to make it succeed. With any luck, this open approach will convince some of the vendors that they need to participate and contribute if they want to be part of the initiative.

Data portability is an idea long championed, and becoming more important all the time.  As we continue to load our online lives on to various social networking sites, the concept of making it easy to get that information back off again, and re-using the information on the next big site without having to start over from scratch are compelling, reasonable, and just plain logical.  Why would you want it any other way?.

It's a good sign that DataPortability.Org is gaining traction.  It's also a good sign that Microsoft has joined.  While Microsoft certainly can't be thought of as a leader in the move to open up our data, it has been making serious strides to open up a number of its platforms, and a common vision shared by the members of DataPortability.Org could make control of our own data something closer to a reality.

Digg has joined the DataPortability Project, a group of websites cooperating to help you securely use your data however you want. Why? Because you own your data. It’s that simple. From the start, Digg has supported the idea that you own your own data.

Digg already supports many of the open standards that let you use your data on sites other than Digg, including RSS, OPML, and hCard. We use RDF to embed the Creative Commons public domain dedication into each page. Just this week, we added MicroID, a Microformat that lets you prove to other services that you own your Digg user profile. We’ll be adding more open standards, such as openID, APML, OAuth, and XFN, in the coming months.

In a nutshell, OSocial lets you see your social data in an open, portable way and we are working on secure methods to allow friending between social networks ; and this without any new registration. OSocial can be seen as Meta Social Network - a way of joining together existing social networks by connecting profiles from different sites.

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

A few weeks ago, we began talking about the new Yahoo! Search open platform. Today, we're releasing more details about two important components of the initiative -- the developer platform as well as our support of a number of semantic web standards.

By supporting semantic web standards, Yahoo! Search and site owners can bring a far richer and more useful search experience to consumers. For example, by marking up its profile pages with microformats, LinkedIn can allow Yahoo! Search and others to understand the semantic content and the relationships of the many components of its site. With a richer understanding of LinkedIn's structured data included in our index, we will be able to present users with more compelling and useful search results for their site. The benefit to LinkedIn is, of course, increased traffic quality and quantity from sites like Yahoo! Search that utilize its structured data.

In the coming weeks, we'll be releasing more detailed specifications that will describe our support of semantic web standards. Initially, we plan to support a number of microformats, including hCard, hCalendar, hReview, hAtom, and XFN. Yahoo! Search will work with the web community to evolve the vocabulary framework for embedding structured data. For starters, we plan to support vocabulary components from Dublin Core, Creative Commons, FOAF, GeoRSS, MediaRSS, and others based on feedback. And, we will support RDFa and eRDF markup to embed these into existing HTML pages. Finally, we are announcing support for the OpenSearch specification, with extensions for structured queries to deep web data sources.

Who really owns your address book? Many Internet companies - like Google (GOOG, Fortune 500) and Yahoo (YHOO, Fortune 500) - say unequivocally that you do. If you sign up for free e-mail accounts on their services, you're free to take your friends with you and export your contact lists to any service that you like.

But Microsoft (MSFT, Fortune 500), while publicly embracing the idea of openness, has been saying something different behind the scenes. Since last summer, lawyers representing the company have been sending cease-and-desist letters to startups that offer new users the ability to import their Microsoft Hotmail contacts. In a move that Valley guys are deriding as ham-handed, Microsoft is offering a quid pro quo: Third-party sites can access Hotmail contacts if they make Microsoft's instant-messaging client available to their users - for 25 cents per user per year. Then the company says it will waive the fee if the sites make Messenger the exclusive in-network messaging client. Such a deal.

There is a better way, of course - though it remains to be seen whether it will work. A group of companies, aligned under the banner of the DataPortability Workgroup, is trying to craft standards that would make it easy for the data we collect online to move as freely and securely from one website to another as we do. As long as two sites abide by the DataPortability rules, they can effortlessly send anything back and forth between them - data, photos, address books. "It's safe, secure, painless," says Chris Saad, the Aussie who co-founded and chairs the DPW. Hundreds of individuals and several leading companies - including Yahoo, Facebook, Google, and even Microsoft - have signed on to the workgroup, and Saad says he's optimistic that we'll see a system in place later this year.

Anyone who has been involved in Open Source software development knows that you have to have a steering group, and there has to be some hierarchy. You can't get a ship moving in any direction with 50 oars in the water each rowing in their own direction. I understand that in order to have buy-in from so many different groups, no one wants to alienate anyone, but the reference made at the meeting (and I'm sorry I forgot who made it) to OpenID was a valid one. They developed the technology, then took it out to various companies and asked for buy-in. In order to "strike while the iron is hot," the luxury of having 100 people all defining things differently and addressing different concerns before there is even a rudimentary roadmap makes the scope of the project much larger than it has to be, and slows down progress.

As the web grows exponentially in scale and complexity, an issue that becomes increasingly pressing is data ownership. There has been a lot of noise lately about how Facebook Connect, Google Friend Connect, and even MySpace’s Data Availability.

The Data Portability Project is trying very, very hard to solve these serious issues. They’re seeking to unite the socio-rhetorico-legal precedent with the growing list of open technologies and specifications (openID, OAuth, RSS, OPML, MicroFormats, Creative Commons, to name a few) and make sure that these proprietary bits, bytes, friends, enemies, birthdays, activies, pictures, videos, lifestyles, etc. are made open to the content creators (read: YOU, not Mark Zuckerberg).

For website owners it only makes sense to support any kind of ” [Facebook/ Google/ Open] Connect” solution, if the majority of their user-base also maintains their social graph at one of those “Social Graph/Identity” providers. Speaking for Germany: that is neither for Facebooks Connect nor Googles Friend Connect (also with the Plaxo combo) the case yet!

We build a solution upon the OpenStack, because than it will work with much more websites, who support the OpenStack as well as a consumer

If you look at the rest of the world - outside of “Facebook-Land” - you also realize and understand much better, why it is so important to find an holistic solution approach - build on open standards - to solve the issue FB Connect addresses: we live in a very diversified world and if everybody comes up with a proprietary solution, it will be just a big mess in the end.