Group items tagged

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.

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.

The Google Contacts Data API allows client applications to view and update Contacts content in the form of Google Data API feeds. Your client application can request a list of a user's contacts, edit or delete content in an existing contact, and query the content in an existing contact. Here are some of the things you can do with the Contacts Data API: Synchronize Google contacts with contacts on a mobile device Maintain relationships between people in social applications Give users the ability to communicate directly with their friends from external applications using phone, email, and IM

Data portability has become a huge meme in the internet universe in the last six months. I am very supportive of the ideas behind data portability, but I am not sure that actual "portability" is really what I most want as a user.

Portability typically implies import/export. I can move my data from here to there. Certainly there is value to this, but it seems to me what I really want is a unified "data location agnostic" view of my data. For example, I'd love to be able to do a search in my data universe and find everything with the words "waterfront project" across all my data silos like Facebook, Google Apps, etc.

As part of the ongoing DataPortabilityAndMe conversation, I have posted my series of videos answering the questions posed... here they are!

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.