> DOI & URI: how does the DOI system work with web URI technologies?
> DOI names may be expressed as URLs (URIs) through a HTTP proxy server. In addition, DOI is a registered URI within the info-URI namespace (IETF RFC 4452, the "info" URI Scheme for Information Assets with Identifiers in Public Namespaces). See the DOI Handbook, 2 Numbering and 3 Resolution, for more information.
I know little about IPFS. I know a bit more about DOIs.
A DOI maps more to an abstract, mutable resource than a specific document or file. That doesn't seem so easy to express in IPFS.
Take doi:10.1093/nar/gkz173 which I picked arbitrarily. This resolves to https://academic.oup.com/nar/article/47/11/e63/5377471 .
That shows the content of the paper in HTML, with an option to download in PDF.
It also has references to the journal issue, methods to get the citation in various format, a navigation bar for the site, and branding for the journal.
Many of these may change over time. Indeed, the paper itself may change if there are any updates or corrections, without changing the DOI.
Or the paper might be retracted, like doi:10.1126/scisignal.abn0168 which resolves to https://www.science.org/doi/10.1126/scisignal.abn0168 . The original paper is no longer accessible. (An alternative is to add the equivalent of a big red stamp on it saying "RETRACTED" while leaving the content accessible.)
Finally, I suspect many journals would not accept a scheme which prevents them from charging for access.
Could you explain how IPFS might handle these issues of multiple formats, mutability, and payment?