Group items tagged

Gartner analysts at the Gartner Symposium/ITxpo in Las Vegas discussed what they believe will be the most disruptive technologies through 2012. Disruptive technologies are those that force changes in industry models, business processes, vendor types, products and services, as well as the all-important user model. Take a look at this list and tell us whether you think something has been omitted—or just plain doesn't belong. This list is ranked in order from least disruptive to most disruptive.

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?

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.

I’m sure some folks are wondering exactly what this means. Even though I was close to the decision making around this, I believe it is still too early to tell. Personally, I share Marc Canter’s skepticism about Dataportability.org given that so far there’s been a lot of hype but no real meat.

As far as I can tell, Dataportability.org seems like a good forum for various social software vendors to start talking about how we can get to a world where there is actual interoperability between social software applications. I’d like to see real meat fall out of this effort not fluff. One of the representatives Microsoft has chosen is the dev lead from the product team I am on (Inder Sethi) which implies we want technical discussion of protocols and technologies not just feel good jive. We’ll also be sending a product planning/marketing type as well (John Richards) to make sure the end user perspective is also being covered. You can assume that even though I am not on the working group in person, I will be there in spirit since I communicate with both John and Inder on a regular basis.

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.

MicroID is a lightweight identity layer for the web, invented by Jeremie Miller (creator of Jabber). MicroID enables anyone to claim verifiable ownership over content hosted anywhere on the web (social networking sites, discussion forums, blogs, etc.). MicroID is not an authentication or single-sign-on service, just a straightforward method for identifying content ownership that complements existing technologies such as OpenID and microformats. The technology is radically simple and enables developers to build new and unique meta services with minimal effort. It's already being used by the likes of ClaimID, Last.fm, Ma.gnolia, Wikitravel, and Yedda.

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.

This session will provide an overview of the basics behind Data Portability, discussing some of the principles associated with it, how the social networking vendors are addressing it, and what you should be aware of as you consider providing or utilizing some of the newest standards that enable Data Portability.

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.

My last column discussed the brand utility supported entertainment model in which content providers and marketers work upstream to create customized complimentary experiences. One option would be to align this model with the open standard objectives of DataPortability.org. Their mission: to gather "existing open standards into a blueprint for a social, open, remixable Web where your online identity, media, contacts and content can follow you wherever you go."

For brands and content creators, that means conversation would truly have to be initiated by the user. The user would own the data, and the brand content offering would have to be valuable enough to warrant an exchange. In essence, brand content would be bought with "data currency."

There are brand enthusiasts who participate in campaigns on an ongoing basis. Yet each time they return, these fans must register and sign-up for the full experience. If the brand were to embrace technologies such as OpenID, not only would it provide their fans access to cross-promotional properties around that campaign, it would also provide easy access to all future campaigns. And with future potential of data portability, people could take those experiences with them, introducing content to friends and hopefully igniting passionate new fans.

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.

On Sunday, we had a significant discussion on data portability and about the activities, responsibilities and opportunities of and for the eponymous group which has recently generated much hype and buzz but little, (as far as I’ve see) clarity and/or cogent strategy for advancing its expansive charter:

So anyway, I do believe that there is an opportunity here and Chris Saad is correct that getting a number of the prominent players in this arena to come to the table on this topic is a feat; however, simply bringing them together without engaging with the gnarly problems and policies that have kept data portability from becoming a reality could bring more confusion and angst than benefit.

The frustration over the minimal barrier to “becoming a member” of the group (you simply have to sign up for a mailing list) and the focus on large vendors without advancing an agenda with teeth and clearly defined metrics for success was palpable. But so was the desire to make some progress, and if not come to complete agreement, to at least identify concerns shared by the majority of us and perhaps develop a strategy to deflate the hype to date and get the group moving in a productive direction.