Parse data? You've already lost. What percentage of the population can do that? What I'm saying is that I believe the main effort should have been in data porta

Parse data? You've already lost. What percentage of the population can do that? What I'm saying is that I believe the main effort should have been in data portability, not in the side-show of source code copyright. But I can give you a concrete example - let's say you're a blogger - it's a large part of your professional output, and a great resource for the people in your field. Now you're not really techie, but you do keep the some original writing locally because you write in Word or whatever. But all the images have to be put in the CMS directly - you can't paste that in - and they are very important. Then there's a bunch of comments, which might greatly add to the post. Then the place that was hosting your blog goes broke/changes business model. Okay maybe you have a techie friend who thinks about this stuff, but they maybe forgot to wget your blog for a few months/year [ahem!]. Those posts are gone. The entire stack of the blogging platform could be, and probably is, open source. It doesn't help one bit. Those open source CMSs could have agreed and maintained a file format for local editing and tools around that. But they didn't because that wasn't seen as the main problem for some reason.