The leading voices in technology have exploded in discussion about data portability, data rights, and the future of web applications. As an active member in the DataPortability Policy group, here is my suggestion on how the debate needs to proceed: break it down. Michael Arrington seems pretty convinced you own all your data, but I don’t think that’s a fair thing to say – and at core is the reason he is clashing with Robert Scoble’s view. For things to proceed, I really think a deeper analysis of the issues need to be made.
1) Define the difference between data, information and knowledge. There’s a big difference.
2) Determine what things are. (is an e-mail address data or information?)
3) Recognise the difference between ownership, rights and their implications.
4) Determine what rights (if that’s what it is) the various entities have over data (users, web apps, etc).
This is a big area and has a lot of abstract concepts – break it down and debate it there.
Some of my own thoughts to give some context
1) Data is an object and information is generated when you create linkages between different types of data – the ‚Äòrelationships‚Äô. Knowledge is the application of information.
- 2000 is data – a symbol with no meaning. Connect it with other data, like the noun "year", and you have information because 2008 now has meaning. Connect that information with other information, like "computer bug" and "HSBC and you now have an application of that information. That being, there was an issue with the Y2K bug that has something to the bank HSBC.
2) Define what things are
What’s an e-mail address, a phone number, a social graph, an image, a podcast…I’m not entirely sure. I wouldn’t be blogging this if I had all the answers. Once we agree on definitions, we can then start categorising them and applying a criteria.
Here is something Steve Greenberg explained to me
– Ownership is relevant when there is scarcity.
– Ownership is the ability to deny someone else‚Äôs use of the asset.
– So, if data is shared and publicly available, it is a practical impossibility for me to deny use
– and if data is available in a form where I can‚Äôt control others‚Äô use of it, I can not really claim to own it
Nitin Borwankar has a very different argument: you should have ownership based on property rights. He explained that to me here .
4) Rights over data
I personally think no one owns data (which is inspired by the definition of data being inherently meaningless); instead you own things further down the value chain when that data becomes something with value. You own your overall blog posts – but not the words.
But again, this goes back to what is data?