Group items tagged

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.

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.

Early adopters of the Web rolled up their sleeves to demonstrate what was possible on their own sites (even before animated gifs came along), so perhaps advocates of things like the Web of Data, opening the social graph and DataPortability should begin at home too…

As an example, the Dataportability movement has framed the problem in terms of Data and Portability. This brings to mind exporting and importing “my” data from vendor to vendor. That’s a start toward liberating users from vendor silos. However, I think the real win is in user-centric services, where the location of the “data” is essentially irrelevant–even as it is hosted under the control of the user–and all user-authorized vendors can access the data through approved services.

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.

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.

Time to continue the conversation about DataPortability... this time using video.We want to hear your thoughts about DataPortability recorded as a short video. We hope to share these videos individually as well as compile them into a single video to help the community understand expectations, goals and themes that are emerging in the discussion.

Despite the valid concerns that some have with Google’s Social Graph API, I thought I would talk about the technical possibilities. My social graph may be of particular interest becuase I had used my Wordpress blog’s XFN feature to mark up the blogs I read as “muse” and my profile on at least 10 social networks as “me.” Using the Google’s Social Graph API demo you can see my extensive list of FOAF and XFN URLs. There is also a machine readable format that could be fed into a new social network to find friends on that network. (click for a larger version)

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).

Beginning today, Windows Live™ ID is publicly committing to support the OpenID digital identity framework with the announcement of the public availability of a Community Technology Preview (CTP) of the Windows Live ID OpenID Provider.

Note that the Windows Live ID OP supports only the OpenID 2.0 protocol.

The current Technology Preview release is for testing purposes only