DataPortability

A lot of you emailed me asking where to find more videos, so I'm delivering the goods. I've expanded the previous list from a paltry 17 to a remarkable 302, and I've included podcasts this time! There were so many videos I had to break them up into different categories for easier skimming. There are no duplicates, however I did place some videos into more than one category when I felt it was appropriate. This list is monstrous, enjoy.

What does all this mean? It means we can expect the web to get itself organized, in a hurry. At stake is a significant amount of traffic from Yahoo search, and anyone else that may choose to build applications on top of this data.

Yahoo’s support for semantic web standards like RDF and microformats is exactly the incentive websites need to adopt them. Instead of semantic silos scattered across the Web (think Twine), Yahoo will be pulling all the semantic information together when available, as a search engine should. Until now, there were few applications that demanded properly structured data from third parties. That changes today.

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.

If you are anything like me (which I hope for your sake you’re not), you’ll be constantly tripping over the names of new data portability initiatives concerned with exchanging social information. Combine any of the following words and create a new name [‘Open’, ‘Social’, ‘Contacts’, ‘Data’, ‘ID’], I checked all the domains and guess what? They’re all taken. (No shit, Sherlock) I thought it would be helpful to list these initiatives and provide a quick comparison of what they do and why they exist. This is my current understanding of the various players. Please comment and correct me where I’m wrong or have omitted important initiatives.

Zuckerberg argues that Facebook provides something the larger web doesn’t — an undo button — which he feels is more important than data portability.

The example he offers is the Facebook news feed. As it stands if you publish something to your news feed and then decide that you want to limit who can see it by changing the privacy settings, that information is removed from your friend’s updates (assuming they no longer have the privileges necessary to access it). However, were the Facebook news feed offered as an RSS feed available outside Facebook (as we’ve often argued it should be), it would, because of the nature of RSS, no longer be retractable. Even if you changed the privacy settings and removed it from the feed, many RSS readers would already have cached or otherwise stored the post you’d like to retract.

Historically, online media tend to start this way. The early services, such as CompuServe, Prodigy or AOL, began as “walled gardens” before they opened up to become websites. The early e-mail services could send messages only within their own walls (rather as Facebook's messaging does today). Instant-messaging, too, started closed, but is gradually opening up. In social networking, this evolution is just beginning. Parts of the industry are collaborating in a “data portability workgroup” to let people move their friend lists and other information around the web. Others are pushing OpenID, a plan to create a single, federated sign-on system that people can use across many sites.

Social networks are becoming more open, more interconnected, and more distributed. Many of us in the web creation world are embracing and promoting web standards - both client-side and server-side. Microformats, standard apis, and open-source software are key building blocks of these technologies. This model can be described as having three sides/legs/arms/spokes - pick your connection: Information, Identity, and Interaction. DiSo (dee • zoh) is an umbrella project for a group of open source implementations of these distributed social networking concepts. or as Chris puts it: "to build a social network with its skin inside out". Our first target is Wordpress, bootstrapping on existing work and building out from there.

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

Search Monkey will be the first use of structured data by Yahoo, but they could potentially be used to affect other parts of the search results or ranking algorithms in the future, according to Kumar. Yahoo will provide more details at an upcoming developer conference it's planning in the coming weeks.

TeleBlog regular Branko Collin gave a nice explanation of how microformats could aid pickups of information from book reviews for Technorati. Josh Gay of the Free Software Foundation, whom I met Friday at a library conference in NYC, has also been a big booster of the concept. I  can see why. As described by Wikipedia, “any page created, or any content added to microformats is placed into the public domain for maximum possible reuse.”

That sounds anti-commerce. But actually microformats could help even commercial sites by, say, bringing more traffic to a book review magazine than it would receive otherwise. Theoretically Yahoo could create a page listing reviews for a certain book and automatically pick up ratings from each publication’s writeup. Such a capability, in turn, might just drive you to visit the sites and see how the reviewers justified the rating. What’s more, other sites could ride Yahoo’s coattails and reproduce the Yahoo page.

Up until today only a few technologies supported certain standards, the Operator extension for Firefox supports microformats, as will Firefox 3 when it is released, but none of these are big enough or important enough for the mainstream. Adding semantics to a website is a lot of hard work if no-one is around to use it.

This is why Yahoo!’s announcement is so big. Now there are machines reading that data and using it and enriching the web with it, do you, as a developer or site owner, want to miss out on that? Yahoo!’s search is to use microformats initially, to improve their understanding of the data to return more relevant results (and, from the looks of their example with LinkedIn add more detail to their search results). So, will other search engines, I’m looking at Google and Microsoft here, want to miss out on the wealth of data that they aren’t collecting and Yahoo! is?

What could be better, a reason to include semantic technologies in your site, better search results, new, intelligent services? I can only say thank you to Yahoo! for supporting this and giving it the much needed boost.

For users to have true data portability, there needs to be some consensus on both the APIs and the formats needed to transfer / represent this portable data. It may be that a number of APIs and formats are required for different scenarios. The Semantic Web is an ideal means for representing the data to be ported from social websites, in that is well suited (using vocabularies like SIOC and FOAF) to represent how people and all kinds of objects on these sites are connected together (documents, discussions, meetups, places, interests, media files - whatever). Of course other data formats may be used, but most importantly, it would be a waste of time to come up with a bunch of new formats for representing the data that needs to be portable, because a lot of work has been done on how to best provide interoperable, reusable and linked data through efforts like the Semantic Web, AtomPub and the microformats community.

using the superior spam blocking skills of services like Yahoo! and AIM

stopped issuing new user credentials last night and now requires new users to create a Ma.gnolia account using an OpenID from somewhere else.

One. DataPortability.org is a volunteer, community project.

Two. DataPortability.org takes nothing for granted and does not adhere to any one gospel of portability.

Three. Warning — this is a PSA. Let’s stop demonizing PR and using “PR” in place of moron, lightweight or unproductive.

You are at the center of the future internet, so it makes sense to begin by writing about Identity. It also makes sense because many of the participants in the modern identity movement are all connected through a single paper, which actually outlined a much more expansive vision than just Identity.

WordPress got into the social networking game by absorbing BuddyPress this month. BuddyPress is a WordPress plug in set that creates a social network out of a multiple user WordPress installation (WordPress MU). Adding BuddyPress to the WordPress family is a smart move on the part of WordPress to stay fresh and relevant.

In the meantime, people who have other, more valuable projects that have been ignored and fallen by the wayside in the great quest for something only the top ten percent of computer users want. One of the most vocal advocates for Data Portability is Chris Saad, the guy who brought us Particls - a great program. Or, it could be great, if his attention wasn't elsewhere, Twittering and blogging endlessly about Data Portability.

I always say that you have to manage you online indentity and that you have to put effort in gaining online authority. This because the online world is getting more and more integrated with the real world and as a person you have to have an online authority to become popular in networks. But there are so many social networks and it takes so much time. Well possible dataportability may help to manage all your profiles online! Just watch the video.

As you might know I attended the London DataPortability Lunch last week and met cool people like Chris Saad, Julian Bond, John Breslin, Tom Morris and others. Among other things we have been discussing the maybe first use case to tackle for Data Portability which is Discovery. As you also might know there was some discussion about how to approach the DataPortability problem space and one of the ideas which came out of that was my idea of dividing it into fields and levels. Now this general discovery use case nevertheless makes much sense because it seems to be a general starting point for every field we might address. So how does it work?