I think it could have worked pretty well to keep it as vague as that. (The auth aspects would need more detail, obviously.)
I don't think data format fragmentation is a big issue (just implement adapters for the top five competitors in your market...), but rather the impossibility of doing it in a quick and seamless manner on behalf of someone wanting to migrate their data to your service from some other service.
Yeah, this would have been nice. I am not sure if legally you could enforce that as automation itself is vague and depends on the source and target both.
> I don't think data format fragmentation is a big issue (just implement adapters for the top five competitors in your market...), but rather the impossibility of doing it in a quick and seamless manner on behalf of someone wanting to migrate their data to your service from some other service.
I think if companies were being honest in their efforts for data portability, as a first step they would not try to reap the benefit of the 30 day window by as much as they can.
For most, it should take mins or hours to get the export yet the best turnaround I have seen from any service has been from Tinder, it was I think 3 days.
Is there anything to prevent the export file format from shifting regularly? You know, for ongoing product improvement reasons, naturally.
Even when we implemented it for my last company, we did JSON exports on signed S3 paths. I thought structured data was the easiest way for any competitor or user to use their data.