Granted, music file formats are mature and standardized enough for cloud service as it is usually defined.
I was commenting on Google Reader's service that this article talks about. It is a reasonable question to ask: can we even call Reader service a cloud service?
The Reader service model was trying to emulate or even predict how we want to access and organize Web news. Perhaps the Facebook model, or part of its model, works better in channelling personal news. Perhaps Summly or part of Google Plus will work better. But can we even call such new agregator a "cloud" service?
You can't fully liberate data in the sense you imply for a few reasons.
Web services are what they are because they only try to REPRESENT our world with their particular data model as best they could. Like a map is not the territory itself. There are myriads of ways to do it. Those who do a good job in representation that best fit our human needs will succeed, like Google in general. But rightly or wrongly, Google judged that Reader is not doing a good representation job and wants to close it.
In their competition to service us, different Web services design DIFFERENT representational models through their database structure, and thus data structure CANNOT be fully homogenous or predetermined -- as new services emerge, evolve, merge, and die. To be homogenous would have meant an all-knowing, prescient, centralized, entity/committee who can design upfront how the world ought to be represented -- which is unrealistic, static, and non-innovative.
Finally, if one of the service providers found the best representation, they would want to keep it a trade secret (which is more moral than applying for a patent, ie, demanding government-granted monopoly), and would not want to share their understanding of customer psychology, much like any other business. That is their competitive advantage that helps them build a "homestead" on the database their customer generate. That is what they get in exchange for providing mostly "free" services. Why should they give it up?
Google is already quite enlightened to realize that their customers own their data, and is generous in revealing part of their database structure in the XML data output from their data liberation. But they are apparently confident enough about their control of the fine details, business philosophy, first-comer advantage, and continuous innovation, to still provide data liberation.
Steve Jobs is the inverse of the dutch boy who stuck his finger in the dyke. He loved the music industry copyright dyke, and dug a little hole in the dyke using iPod, to let profit flows through his hands.
Techdirt has not posted any stories submitted by ks.
Re: Re: Homogenous data structure not realistic
Granted, music file formats are mature and standardized enough for cloud service as it is usually defined.
I was commenting on Google Reader's service that this article talks about. It is a reasonable question to ask: can we even call Reader service a cloud service?
The Reader service model was trying to emulate or even predict how we want to access and organize Web news. Perhaps the Facebook model, or part of its model, works better in channelling personal news. Perhaps Summly or part of Google Plus will work better. But can we even call such new agregator a "cloud" service?
Homogenous data structure not realistic
You can't fully liberate data in the sense you imply for a few reasons.
Web services are what they are because they only try to REPRESENT our world with their particular data model as best they could. Like a map is not the territory itself. There are myriads of ways to do it. Those who do a good job in representation that best fit our human needs will succeed, like Google in general. But rightly or wrongly, Google judged that Reader is not doing a good representation job and wants to close it.
In their competition to service us, different Web services design DIFFERENT representational models through their database structure, and thus data structure CANNOT be fully homogenous or predetermined -- as new services emerge, evolve, merge, and die. To be homogenous would have meant an all-knowing, prescient, centralized, entity/committee who can design upfront how the world ought to be represented -- which is unrealistic, static, and non-innovative.
Finally, if one of the service providers found the best representation, they would want to keep it a trade secret (which is more moral than applying for a patent, ie, demanding government-granted monopoly), and would not want to share their understanding of customer psychology, much like any other business. That is their competitive advantage that helps them build a "homestead" on the database their customer generate. That is what they get in exchange for providing mostly "free" services. Why should they give it up?
Google is already quite enlightened to realize that their customers own their data, and is generous in revealing part of their database structure in the XML data output from their data liberation. But they are apparently confident enough about their control of the fine details, business philosophy, first-comer advantage, and continuous innovation, to still provide data liberation.
Steve Jobs inverse of dutch boy
Steve Jobs is the inverse of the dutch boy who stuck his finger in the dyke. He loved the music industry copyright dyke, and dug a little hole in the dyke using iPod, to let profit flows through his hands.