Can we do more with DOIs?

[oxinabox]

There is a lot of pressure to get a DOIs assigned to your data.
Since a DOI is a persistent identifier, even if URLs change.
the DOI can be updated.

However, problem is DOIs rarely point at the data directly,
the normally point at a site that talks about the data and has a link somewhere on it.
Consuming such as site is the job of DataDepsGenerators.jl.

In theory DOIs can put up a whole range of metadata (not just a redirect),
getting at it involves negotiating formats via HTTP headers.

See https://citation.crosscite.org/docs.html#sec-3

Doable e.g;
curl -LH "Accept: application/rdf+xml;q=0.5" https://doi.org/10.1126/science.169.3946.635
gives back a lot of metadata (add -I to see the Header redirect location).
None of which related to a download URL for any data.

Now maybe that is because it isn't a dataset:
but curl -LH "Accept: application/rdf+xml;q=0.5" https://doi.org/10.7910/DVN/GQCPXM is,
and it also has no useful information as far as an URL that I can actually fetch the dataset from.

Maybe the best we can do is tell people to include the DOI in their message,
so if their URLs break the DOI can be used to track down the new ones.

[oxinabox]

See also
ropensci-archive/doidata#1

and

https://blog.datacite.org/content-negotiation-update/

Possibly this should move to DataDepsGenerators.jl
Or possibly not,
since unlike something made with DataDepsGenerators,
if we can do it right with a DOI that should be able to do it perfect forver.
(Where-as many cases from DataDepsGenerators will be flaws and need human correction/ongoing maintanance))
So we could maybe have special RegesterDataDOI(name, doi)

[oxinabox]

Closed in DataDepGenerators