-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a DOI for SWEET #8
Comments
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 <notifications@github.com<mailto:notifications@github.com>> 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 GitHub<#8>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABNU0H9MYi3J91jOFm3JH4e2K67Ui1iQks5ru9EdgaJpZM4M6hzd>.
|
acknowledged @graybeal good point |
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.
|
Thanks @pbuttigieg for detailing. |
A paper which is relevant here |
Similar discussion at cf-convention/cf-conventions#127 |
Lets see how that conversation goes LOL |
Do we have formal release notes? |
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/
The text was updated successfully, but these errors were encountered: