Comments on: Google liberates data http://futureoftheinternet.org/google-liberates-data Jonathan Zittrain is Professor of Law at Harvard Law School and co-founder of the Berkman Center for Internet and Society at Harvard Law School Fri, 30 Jul 2010 06:25:46 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Kindermode http://futureoftheinternet.org/google-liberates-data/comment-page-1#comment-13228 Kindermode Thu, 15 Oct 2009 18:30:47 +0000 http://futureoftheinternet.org/?p=890#comment-13228 I think that it`s dangerous to use this tools and putting own data to networks, everyone can use.... I think that it`s dangerous to use this tools and putting own data to networks, everyone can use….

]]> By: Nick @ Brick Marketing http://futureoftheinternet.org/google-liberates-data/comment-page-1#comment-13158 Nick @ Brick Marketing Tue, 13 Oct 2009 13:43:22 +0000 http://futureoftheinternet.org/?p=890#comment-13158 I think this is a battle that will be difficult to fight in the long run. As soon as you start using some of these products they gain control of what ever you put onto those networks. Facebook has rights to the photos in Facebook. It is the price you pay to use their services. Nobody is forcing anyone to use a Google blog or email. I think this is a battle that will be difficult to fight in the long run. As soon as you start using some of these products they gain control of what ever you put onto those networks. Facebook has rights to the photos in Facebook. It is the price you pay to use their services. Nobody is forcing anyone to use a Google blog or email.

]]> By: Andrew Martin http://futureoftheinternet.org/google-liberates-data/comment-page-1#comment-13108 Andrew Martin Mon, 12 Oct 2009 11:50:51 +0000 http://futureoftheinternet.org/?p=890#comment-13108 There's certainly a need for a voluntary code of practice, and perhaps regulation: Picture a future scenario where a significant cloud data provider gets into financial difficulty. As rumours about its viability spread, everyone tries to pull off copies of their own data. This overloads the servers, compounding the fears. The company goes bust, and the liquidators do their best to return data to its rightful owners, but they may not have the resources to do so. It's not unlike a run on the bank - and for those with data significantly 'invested' in the provider, approaching the same level of seriousness. There’s certainly a need for a voluntary code of practice, and perhaps regulation:

Picture a future scenario where a significant cloud data provider gets into financial difficulty. As rumours about its viability spread, everyone tries to pull off copies of their own data. This overloads the servers, compounding the fears. The company goes bust, and the liquidators do their best to return data to its rightful owners, but they may not have the resources to do so.

It’s not unlike a run on the bank – and for those with data significantly ‘invested’ in the provider, approaching the same level of seriousness.

]]> By: Saqib Ali http://futureoftheinternet.org/google-liberates-data/comment-page-1#comment-13088 Saqib Ali Mon, 12 Oct 2009 00:58:52 +0000 http://futureoftheinternet.org/?p=890#comment-13088 Vendor lock-in is an issue with any data storage system - in the cloud or hosted in-house. We need to look into and investigate the tools that the vendor provides to extract the data out of the system. From what I seen (and experimented with), Google provides excellent set of APIs to access the data stored in Google's Cloud. And Google is always working on to improve the APIs. Google usually first adds functions to the API, and then introduces them in the UI. Compare this to other software vendors, who usually introduce the new functions in the UI and then at a later time provide API access to those functions - if it all. I currently use both Google Docs and Windows Live Workspace to store my personal / school related stuff. I use both of these because they both have their benefits. Windows Live Workspace provides complete integration with Office 2007, whereas Google Docs provide editing capabilities in a Web browser. Recently I have been thinking of writing an application that will synchronize the content of both of these repositories. Google provides APIs that make this task easy from Google's side, but there are no Windows Live Workspace APIs, so I have to devise a workaround to get documents into the Windows Live Workspace. "With problems that we are not aware of yet, the ability to put right - not the sheer good luck of avoiding indefinitely - is our only hope, not just of solving problems, but of making progress. " - Physicist David Deutsch Vendor lock-in is an issue with any data storage system – in the cloud or hosted in-house. We need to look into and investigate the tools that the vendor provides to extract the data out of the system.

From what I seen (and experimented with), Google provides excellent set of APIs to access the data stored in Google’s Cloud. And Google is always working on to improve the APIs. Google usually first adds functions to the API, and then introduces them in the UI. Compare this to other software vendors, who usually introduce the new functions in the UI and then at a later time provide API access to those functions – if it all.

I currently use both Google Docs and Windows Live Workspace to store my personal / school related stuff. I use both of these because they both have their benefits. Windows Live Workspace provides complete integration with Office 2007, whereas Google Docs provide editing capabilities in a Web browser. Recently I have been thinking of writing an application that will synchronize the content of both of these repositories. Google provides APIs that make this task easy from Google’s side, but there are no Windows Live Workspace APIs, so I have to devise a workaround to get documents into the Windows Live Workspace.

“With problems that we are not aware of yet, the ability to put right – not the sheer good luck of avoiding indefinitely – is our only hope, not just of solving problems, but of making progress. ” – Physicist David Deutsch

]]>