Two interesting posts on the question of data ownership, coming from two very different perspectives.
Harold Jarche comes at the question from a “physical” standpoint, as he contemplates the closure of Eduspaces, in his post Own Your Data:
Anyone who asks me about blogging or setting up a community on the Web using wikis or some other application is given pretty well the same advice. If the site is important and the data are of some significance for the long term, then:
- Use an open source platform from a stable and functioning community.
- Own your own domain, and have a Service Level Agreement for your hosting.
Using open source gives you freedom from vendors and ensures that you are not handcuffed to your technology provider. Having your own domain name and paying for a service provider (or hosting on your own server) ensure that you have control over your data.
This is one of the reasons I moved this blog off of Blogger and onto my own domain . I’m eventually planning to import that old version onto the new, but I’ve not been able to get the function to work properly. (An excellent example of what Harold is talking about.)
On the other hand, Ton Zijlstra is thinking more about how to control how the data is used. In To (Web2.0) Developers: I Want Control of My Data, I Want to Write My Own Rules, he gives developers his two key reasons:
First because if you tell me I have no friends simply because my data is not on your platform, you’re not getting it. I am the landscape, you are the map. And the map does not get to say what reality is, just what it thinks it looks like.
Second because I want my tools to become smarter, a lot smarter. And it is only me that can provide the context and data that allows tools to be smarter. I need to be in control of my data for you to let your tools be smarter. I need to be the owner of e.g. my favourites/wishlists and preferences for you to really give me good recommendations.
Something to think about.