This is an excellent resource for software developers working with DOIs. It dispels all of the most stupid myths I have heard said about DOIs, and some others I didn’t know (e.g. the finer aspects of comparing DOI strings)
https://fosstodon.org/@joewass/113437281415235360
=> More informations about this toot | More toots from paulwalk@mastodon.social
@paulwalk In case you have any thoughts, there’s a proposal in the works to register a permanent URI scheme for DOIs that talks about a few of these issues…
https://github.com/sandflow/doi-uri-scheme
https://datatracker.ietf.org/doc/draft-lemieux-doi-uri-scheme/
=> More informations about this toot | More toots from gklyne@indieweb.social
@gklyne Interesting…. seems like an odd thing to do (but i haven't read the proposal yet). Thanks for sharing!
=> More informations about this toot | More toots from paulwalk@mastodon.social
@paulwalk Yes, it’s arguably late in the day to be pushing this, but even if use of the DOI scheme doesn’t catch on (e.g. by implementation in browsers), I think it does serve to codify some existing practices around them. (Disclosure: this isn’t my proposal, but I have been involved in reviewing it and am supportive of the scheme being registered with IANA.)
=> More informations about this toot | More toots from gklyne@indieweb.social
@paulwalk BTW, this is a DOI Foundation initiative.
=> More informations about this toot | More toots from gklyne@indieweb.social
@gklyne @paulwalk Quite amazingly, this is the first time I hear about it.
=> More informations about this toot | More toots from hvdsomp@w3c.social
@hvdsomp @gklyne likewise
=> More informations about this toot | More toots from paulwalk@mastodon.social
@hvdsomp @paulwalk I did flag it on the IETF URI-review list, and tried to get attention of a couple of Crossref folks, but didn’t know an obvious venue to circulate more widely (and, now I’m officially retired I don’t have the same informal channels).
=> More informations about this toot | More toots from gklyne@indieweb.social
@gklyne @hvdsomp @paulwalk There's been talk of DOI URIs for 20 years, and I'm sure I've seen plenty in the wild.
https://datatracker.ietf.org/doc/html/draft-paskin-doi-uri-04
(I'm former Crossref staff)
=> More informations about this toot | More toots from joewass@fosstodon.org
@joewass @gklyne @paulwalk I know about those days! I’m surprised to learn you’re no longer at CrossRef!
=> More informations about this toot | More toots from hvdsomp@w3c.social
@hvdsomp I was there for over a decade. Time for something new!
=> More informations about this toot | More toots from joewass@fosstodon.org
@paulwalk
"It’s possible to register multiple DOIs to the same resource URL. This could happen within a registration agency, or for two registration agencies to register a DOI for the same URL. There aren’t any checks for uniqueness at the DOI level."
Should such a check be put in place?
=> More informations about this toot | More toots from OpenSciTwente@akademienl.social
@OpenSciTwente I guess this be computationally expensive for the Registration Agencies to do - they would have check each new DOI as it was minted or edited. With the possibility of intermediate HTTP redirects this would become very challenging
=> More informations about this toot | More toots from paulwalk@mastodon.social This content has been proxied by September (3851b).Proxy Information
text/gemini