The DOI System
doi.org
The DOI System
1–10 of 67 posts
Re: The DOI System
#2Re: The DOI System
#3Do DOIs still make sense if we have web3? Would the future of DOIs be similar to a filecoin kind of system, instead of using resolvers and organizations like CrossRef?
Re: The DOI System
#4IPFS (and other technologies like it) are essentially just distributed DOIs, which are extremely functional and have been used for years, yet get very little appreciation in tech field.
Re: The DOI System
#5IPFS (and other technologies like it) are essentially just distributed DOIs, which are extremely functional and have been used for years, yet get very little appreciation in tech field.
The "just distributed" is the interesting bit though. DOIs are really the same as URLs, except the lookup doesn't use DNS.
Re: The DOI System
#6Another issue is that it doesn't guarantee the URN (i.e. DOI number) uniquely identifies a resource. So a single resource can have several aliases, potentially confusing discussions or bypassing blacklists, etc.
Re: The DOI System
#7Huh I forgot that DOIs are meant for more than just academic journals. Do DOIs still make sense if we have web3? Would the future of DOIs be similar to a filecoin kind of system, instead of using resolvers and organizations like CrossRef?
Re: The DOI System
#8Earlier quoted context omitted.
The "just distributed" is the interesting bit though. DOIs are really the same as URLs, except the lookup doesn't use DNS.
I think DOI is essentially a URI schema. I don't think there is a technical reason preventing them from being distributed like IPFS, in fact the underlying resources are distributed it's just the URL lookup that is centralized.
> 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?
Re: The DOI System
#9Re: The DOI System
#10Can someone tell me where to get a definitive list of DOI prefixes? I tried to find this some time ago and came away very frustrated. The system seems in reality very opaque.