Comment by tuukkah
3 years ago
In one word, MyData: I should be able to authorize a new service Y to download all data about me from service X. I should be able to delete all data about me from service X and leave a redirect to my new profile URL at service Y.
Number portability is not a novelty requirement in competition law, but somehow we haven't expanded it to apply to online accounts.
Standardisation is needed but that's why RFCs, W3C etc. exist. The existing web standards go a long way if fully implemented.
Thank you! I totally agree that data should belong to the user (in fact, I find it shocking that some consider this opinion controversial). I’m still not quite clear however how the software can interoperability is supposed to be achieved. I understand that one can impose a standard, but a standard presupposes a certain data model. What if my application does not follow this data model? Would one ban social network apps that don’t want to implement a particular database schemas?
Interoperability is focused on what happens between services, not what happens inside. You don't have to use a specific database schema to be able to support standards in APIs.
Like Facebook messenger and Google chat both used to support xmpp, they don't run those services in that internally but they built gateways that let clients that talk xmpp talk to them.