sweet
sweet copied to clipboard
ESIPFed
Create a DOI for SWEET
We should create a DOI to make SWEET referenceable. We can do this via https://zenodo.org/ and also add a badge to the README similar to what ENVO have done at https://github.com/EnvironmentOntology/envo/
Hi Lewis,
Thanks for all the work on all things semantic for ESIP!
Umm, this risks starting a DOI/URL debate, but IMHO SWEET should be eminently referenceable without a DOI. I would call a DOI for SWEET rather anti-semantic, in fact.
There are obviously major assumptions that inform my opinion, most importantly that any organization that is going to run a semantic repository should own up to the responsibility to maintain those addresses "in perpetuity" (which is to say, as close to that as is reasonably possible).
It's certainly a topic where opinions differ, and my input is perhaps not of the greatest weight. But I did want to register the opinion for your consideration.
john
On Apr 11, 2017, at 8:14 PM, Lewis John McGibbney <[email protected]mailto:[email protected]> wrote:
We should create a DOI to make SWEET referenceable. We can do this via https://zenodo.org/ and also add a badge to the README similar to what ENVO have done at https://github.com/EnvironmentOntology/envo/
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/ESIPFed/sweet/issues/8, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABNU0H9MYi3J91jOFm3JH4e2K67Ui1iQks5ru9EdgaJpZM4M6hzd.
Greetings both,
ENVO uses PURLs to point to the ontology release files themselves. The DOI points to the latest set of release notes as a sort of nanopublication.
A paper which is relevant here Aquino, J. A., J. J. Allison, R. A. Rilling, D. Stott, K. Young, and M. D. Daniels, (2017). Motivation and strategies for implementing Digital Object Identifiers (DOIs) at NCAR’s Earth Observing Laboratory -- Past progress and future collaborations. Data Science Journal, 16, p. 7, doi:10.5334/dsj-2017-007.
Similar discussion at https://github.com/cf-convention/cf-conventions/issues/127
