-
Notifications
You must be signed in to change notification settings - Fork 4
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
NISO identifiers for CRediT roles #130
Comments
Hi @vincentml, Yes! I should be able to work on this. I haven't worked on CRO in quite some time but I'll work on this asap and let you know if I have any questions. |
Thanks @nicolevasilevsky! @vincentml, Nicole and I had a chat and we want to talk with the CD2H Architecting Attribution PIs before we make any changes, especially since we'll have to do some work to decommission our CRediT URIs and CRO is currently unfunded. I just want to make sure everyone who was involved with CRO is apprised of what's going on so nobody is surprised when we make the change. But I think it's great news that NISO has taken over CRediT and that it's an official standard, and I'm excited about opening communication with CRO! We should probably set up a meeting to talk at some point... |
@vincentml, I have a question. Does NISO have any plans for an OWL implementation of CRediT? The context for this question is the fact that the CRO was developed with the Ontology Development Kit,, and we treated CRediT as an imported ontology. In order to do that, we created our own OWL implementation of CRediT at https://github.com/data2health/credit-ontology, complete with persistent identifiers at both purl.org and w3id.org, and then we use the ODK to generate import files from it. What this means is that the "technically correct" way for us to update CRO is to update https://github.com/data2health/credit-ontology with the NISO URLs, create new imports for CRO, and then generate new CRO OWL and OBO files. This process is a bit over-engineered and I'm considering abandoning it, since it was tricky to get right the first time and the ODK and its supporting tools have changed considerably in the meantime. This would be a very easy decision if there were any plans for an official NISO OWL implementation of CRediT. Or perhaps it would be appropriate to discuss handing off our implementation to NISO? I'm not sure, and I'd be interested in your thoughts on the matter. |
The Contributor Roles Taxonomy (CRediT) is now being maintained by NISO to carry on the work that was started at CASRAI. The CRediT taxonomy can now be found at https://www.niso.org/standards-committees/credit as well as at https://credit.niso.org/. CRediT has been approved as an official ANSI/NISO standard, and NISO has formed a standing committee to support the future development and maintenance of CRediT. As a member of that committee I am hopeful that we can establish an open line of communication with CRO. In addition, NISO has assigned persistent identifiers to each of the 14 CRediT roles. Would it be possible for CRO to be updated to include the new persistent identifiers for CRediT roles? The CRediT roles and their new identifiers are listed below.
If there is any way that I can help please let me know.
The text was updated successfully, but these errors were encountered: