DataPortability

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.

Social networks are great: you can stay in touch with friends all across the world and find new ones based on your interests. But often, social networks serve a single purpose or interest. For instance photos, videos or classmates from school and university. This is not a problem by itself, but when you want to keep track of all your contacts in all these social networks, this is a lot of work for you to update your contacts list in all the social networks you are in. And you also might need to get a member of a social network, although you're not interesed in the subject, but only want to track your friends activities. NoseRub only defines the social network and some basic content types like media, links, micropublishing and text. You can now add all your contacts to a NoseRub network and aggregate several social networks into just one. And you always have full control of your data, as you can install NoseRub on your own server and have it connect to other servers out there.

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.

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.

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.

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.

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.

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.

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.

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.

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.