Group items matching

in title, tags, annotations or url

A few months ago, we announced that we were opening the social graph and invited others to join us. An effort like that encompasses many different technology projects and all kinds of different companies; in just a few months the idea of opening up social networks has received a lot of attention. Today we're excited to share an amazing new plugin for Movable Type that allows you to aggregate, control, and share your actions around the web and we're the first to bring this sort of functionality to free and open source blogging tools.

It's worth revisiting some of the successes the openness movement has accomplished in just the past few months: Google's OpenSocial released new versions of its APIs and we hosted a wildly successful hackathon to help support the creation of new widgets for the standard. OpenID 2.0 shipped and both Google and Yahoo! are now supporting OpenID, bringing hundreds of millions of new IDs to the community. The group DataPortability.org was formed and released a video reinforcing these themes around openness. And finally, we've made good on our promise to let you show off all the services you belong to, with TypePad and Vox automatically letting you list your accounts around the web on your blogs using Microformats to link to your profiles. And as of today, the same ability is available for Movable Type.

As we explained half a year ago, we're on a mission. Like we said then, blogs change the way we communicate. Just like with TrackBack, OpenID, opening the social graph, and so much else in blogging, we're hoping that we can influence everyone else to follow our lead and move blogging forward with us. Bringing your actions around the web under your control is a fundamental next step to making all of our blogs even more powerful and expressive.

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.

DataPortability.org is heading up a workgroup that will hopefully do just that. While many groups and companies are taking part in this effort, the recent addition of a few big name players has attracted a lot of attention.

WebProNews spoke with Chris Saad, the Co-Founder and Chairman of Data Portability.

Robert Scobles ban from Facebook early this month brought up the discussion again about ownership of user data in social networks such as MySpace, Facebook and others, as well as about data portability. Robert Scoble did violate the terms of service agreement with Facebook; so much seems to be clear. What his actual motivations were for his actions are not so clear though. You can check out his version of the story at Computerworld and also 1938 Media's Loren Feldman's takes one and two on this incident as well.

It does not matter what the actual reasons were and what exactly happened, but one thing is clear, it brought attention to an issue that everybody who uses social networking sites is just all very familiar with. I for myself consider it a pain to rebuild profiles and connections from scratch at every social media site again and again. It takes time and as most others, is time the only commodity I have always a shortage of. Then I look at my profiles at the different sites and how they developed over time to realize that they are all looking pretty much the same, I even hooked up with the same people at all those different sites again.

Hello DataPortability.org It is actually looking very promising that this initiative will result into a standard that will be adopted by many social media sites. They are not going to reinvent the wheel and start creating something from scratch, but use and "mash-up" existing standards and initiative to create something new specifically aimed to solve the data portability problem.

Whenever Microsoft Corp. eschews an open standard (think the OpenDocument Format, aka ODF), it gets pilloried. Whenever it embraces one, as it will soon do with DataPortability.org, fears rise that Redmond will twist it to its own advantage, (think Java) or, failing that, sabotage it. (ActiveX) So is the nascent DataPortability.org group at such risk from Redmond? Not according to a source inside the group. "The DataPortability group is made up of many voices - individuals who are passionate about solving the problem," the source said. "Microsoft's voice is a welcome addition but it is not the only voice in the conversation and it does not have any special consideration."

The news today is that Microsoft intends to join the DataPortability Project. So where’s the beef? Why are long-time influentials from all these large vendors joining the cause? What are we offering? What are we trying to do? What’s in it for them? What do they bring to the table?

First, I’d like to clarify that DataPortability is not mine. It is an initiative that was co-founded by many people who all believed that something was missing from the existing Identity/Data/Standards landscape. Something very small, but very important.

The business risks for Web 3.0 are fundamentally changing with increased public scrutiny of data privacy, portability, expanded Web Services, data sharing, cloud computing, etc. New privacy laws, new technological capabilities, and new user demands have created a situation where the question most frequently cited by students of Web 3.0 implementations have asked: we understand how beneficial it is to link data and derive new improved services, knowledge about our users/customers but what about privacy, regulation from the consumer perspective?

Key questions are discussed: who owns user data? How should users be able to reuse it? Why should companies consider allowing their users' personal data to be easily transportable? The answer here is: because in the end it will bring our users/customers closer, a finding many major enterprises have realized: Nokia, etc.

The World Wide Web Foundation seeks to advance One Web that is free and open, to expand the Web's capability and robustness, and to extend the Web's benefits to all people on the planet. The Web Foundation brings together business leaders, technology innovators, academia, government, NGOs, and experts in many fields to tackle challenges that, like the Web, are global in scale.

When Facebook joined the DataPortability.org Workgroup a few weeks ago, the press described the move both as a “bombshell” as well as “brilliant PR”. In order to understand what Facebook’s decision to join actually means a little bit better, I spoke with Chris Saad, Co-Founder and Chairperson of DataPortability.org.

IF: What does it mean for companies like Facebook to “join” DataPortability.org? CS: It means they agree to engage in the conversation and work towards a blueprint for maximum interoperability between applications.

IF: Has Facebook promised to implement any particular functionality by any particular time? CS: Not yet - but once the blueprint is done we can then start asking vendors to implement things. Many other vendors have already moved quickly - in the last few weeks and months lots of vendors have been implementing OpenID, etc - these things are not unrelated.

Data Portability and Cloud Ownership Posted July 21st, 2008 by Ross Fadner turn_ad_publisher = 2919766;turn_ad_publisher_ad_code = 2919800;turn_ad_layout = "300x250";turn_ad_publisher_channel = 2919778;turn_ad_manual_id = 24759350;<img height="1" width="1" border="0" src="http://ad.turn.com/r/error?errMsg=noiframe&adUrl=http%3A%2F%2Fad.turn.com%2Fserver%2Fads.htm%3F%26pub%3D2919766%26code%3D2919800%26cch%3D2919778%26l%3D300x250%26tmz%3D4%26area%3D1%26rnd%3D0.19900853499693383%26lmd%3D1216835834%26aid%3D24759350%26url%3Dhttp%253A%252F%252Fwww.mediapost.com%252Fblogs%252Fraw%252F%253Fp%253D671%26ref%3Dhttp%253A%252F%252Fwww.mediapost.com%252Fblogs%252Fraw%252F%253Fcat%253D16"/> In describing the state of the data portability movement, Alex Blum, CEO of KickApps, said, “we now have a situation where major Web players are vying to be the cloud—to provide the underlying technology for social graph data.” Blum duly noted that the idea scares both publishers and audiences, but Parity CEO Paul Trevithick, for one, doesn’t seem to think the Big Brother pretensions of the likes of Google are a foregone conclusion. “The point is architectural,” he said. “Facebook would say it should be us (that should be the gatekeeper of users’ data), but data goes in and doesn’t come out.” Instead, he said that, “people, themselves, as sovereign entities, should have the control.” This is the idea behind data portability: that users control their own data, and that that data is portable; i.e. it exists in many places without belonging to any of those places. As such, Trevithick said data portability would help bring about an Internet of the future where you don’t have to repeat yourself, because your data would exist in cloud that’s accessible whenever and wherever you go online.

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.

Chris Saad, cofounder and chair of the nonprofit ­DataPortability Project, notes that many current methods of transferring data expose users to huge security risks. For example, it's a common practice for social sites to ask users to submit the usernames and passwords for their Web-based e-mail accounts when they first sign up; an automated service can then search the network for people listed in their address books. "The door is open right now for any application that scrapes your Gmail address book to go ahead and scrape your shopping cart as well, or scrape your searches, or keep your username and password and pretend to be you," says Saad. "It's a nightmare of security, and it's something we need to solve sooner rather than later."

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.

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.

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.

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.

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.