-
Notifications
You must be signed in to change notification settings - Fork 16
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
Upgrade the output types for Publications, Products and Patents to align with the COAR Resource Types v.3.0 #99
Comments
In the last months, COAR has refined and published the new vocabulary at https://vocabularies.coar-repositories.org/resource_types/ , v3.0 |
Version 3.0 has dropped 7 terms from the earlier versions:
How do we handle these? I can see two options:
|
COAR has updated the resource types vocabulary v2.0 - 2021-02-03 , https://vocabularies.coar-repositories.org/resource_types/2.0/ From the COAR resource types v1.1, which is used by the current guidelines, to COAR v2.0 is no ChangeLog available. It seems to be, that only terms have been added. From v2.0 to v3.0 is the ChangeLog:
I would suggest, that the next release of the Guidelines marked the removed terms as deprecated and the future release will be remove the terms. The benefit would be that the guidelines remain compatible with v1.1 and v1.1.1 . |
Yes, I very much agree we should keep the terms removed in the 2.0 -> 3.0 step: we'd lose backwards compatibility otherwise. In the case of "periodical" and "contribution to journal" this will even involve keeping parts of the old hierarchy. |
Oops! Version 3.0 uses |
Dear @jdvorak001 , could you link to page. I see: and the namespace URI schema doesn't change it's still "http://purl.org/coar/resource_type/" |
Yes, it's been declared this way. But the skos:ConceptScheme in v3.0 is |
This was quite a project, but I believe we're done here. With @ACz-UniBi we have checked that the Guidelines now contain all the terms from the offical vocabulary website plus the ones that were present in the 1.1 version of the vocabulary and deprecated since then. |
We agreed to keep the deprecated terms in the vocabulary even if we are producing version 1.2.0 (instead of the originally planned 1.1.2). We will drop the date a term is deprecated since, because these were misleading: no new version of the OpenAIRE CRIS Guidelines was produced on that day. We will also add a notice about the possibility to drop these terms in a next release. |
http://vocabularies.coar-repositories.org/documentation/resource_types/
Recording today's discussion with @joschirr : It would be very difficult to coordinate with the releases of the other OpenAIRE Guidelines, so we should proceed on our own here. It is always recommended to use the latest available version.
The text was updated successfully, but these errors were encountered: