Of course this will only work in some jurisdictions, and even then it needs stronger enforcement to ensure that data controllers will comply (or even understand their obligations).
As others have pointed out, that doesn't quite work. But the way that I use rsync with my remarkable is to use sshfs to mount the remarkable's filesystem, and then run rsync between the local and mounted filesystems. Works for me without having to install rsync on the remarkable.
Unfortunately you will not get any speed boost in that case, in fact it will be slower having to fetch all the remote side data for small file changes.
Fair enough. It does work for my simple use case: rsync student coursework to the remarkable, mark coursework on the remarkable, rsync back. There aren't many small file changes and USB is fast enough. The real bottleneck is the marking but I'm not sure if I want a package manager to help me with that!
I had my Masters students do this as part of my wireless networking class this year. It was very instructive for me and the students seemed to enjoy it, so I'll definitely keep it in the syllabus.
Unfortunately not everyone reports this information. Here is a study that we did of over 500 papers using online social network data: http://tnhh.org/research/pubs/tetc2015.pdf While most authors would report high-level characteristics (e.g., which social network they measured), fewer authors reported how they sampled the network or collected data, and very few people reported on how they handled ethics, privacy and so forth.
The article's description of a DOI is a bit vague. It isn't just a link. When you register a DOI, you have to register the metadata, which are then stored with your DOI registration agency (like crossref or datacite). e.g., 10.15783/C7F59T is a DOI for one of our datasets. If you follow http://doi.org/10.15783/C7F59T in your browser then you get taken to our data archive, but if that goes away then you can still query the metadata at datacite (http://data.datacite.org/10.15783/C7F59T)
In the second instance, we're as open as possible about it and discuss the shortcomings of the system! It's not perfect, but nothing is. We think it's the best solution.
Thank you for the clarification. It clears a up lot; it seems I gave the designers of the DOI too little credit. Your last question brings some food for thought. The naive answer is to "just decentralize it", but smarter people than I have been trying to tackle a similar issue with certificate authorities. Sometimes software isn't really the easiest solution in contrast to open dialogue and cooperation.
Of course this will only work in some jurisdictions, and even then it needs stronger enforcement to ensure that data controllers will comply (or even understand their obligations).