> Just as an example, if I wanted to get a list of every song I liked on Spotify and import it into Apple Music, how would that even work? The songId of Spotify is undoubtedly different than the one Apple uses. Are Apple and Spotify supposed to agree on a common file format?
If I was Spotify I would export that as an SQLite DB. Maybe the metadata catalog as a standalone DB too.
Apple Music has an API[0] so it's already mostly possible to import a list of songs in it.
> I agree with the intent of the law but I'm not surprised most services do not offer an automated way to take out data. It's a rare case, often a heavy workload, and there's really no way to guarantee the data you receive is actually portable.
"Data Portability" is so vaguely defined that I can't help but see it as yet another law that EU bureaucrats will use to fleece (American) "Evil Tech Giants".
"Data portability" is vague so that the law is stable and flexible. As a comparison, "drivers need to adapt driving speed to weather conditions" is equally vague. It would simply be infeasible to publish an hourly speed limit chart based on rain, fog, snow, etc. It is the responsibility of driving instructors to raise awareness on reasons to adapt the speed. Drivers need to then interpret that clause to their situation.
Similarly, it is up to industry -- either via standardization bodies or courts -- to clarify what exactly is "data portability".
the phrase maybe, but the gdpr article itself provides more
"Article 20
Right to data portability
1. The data subject shall have the right to receive the personal data concerning him or her, which he or she has provided to a controller, in a structured, commonly used and machine-readable format and have the right to transmit those data to another controller without hindrance from the controller to which the personal data have been provided, where:"
https://eur-lex.europa.eu/eli/reg/2016/679/oj#d1e2753-1-1
so the law would state that you need to constantly check your phone for the app that tells the current speed limit based on weather, road type, road size, car size, tire type, and traffic
If I was Spotify I would export that as an SQLite DB. Maybe the metadata catalog as a standalone DB too.
Apple Music has an API[0] so it's already mostly possible to import a list of songs in it.
> I agree with the intent of the law but I'm not surprised most services do not offer an automated way to take out data. It's a rare case, often a heavy workload, and there's really no way to guarantee the data you receive is actually portable.
"Data Portability" is so vaguely defined that I can't help but see it as yet another law that EU bureaucrats will use to fleece (American) "Evil Tech Giants".
[0] https://developer.apple.com/documentation/applemusicapi