You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a whole repository dedicated to converting ROR to an OWL ontology in https://github.com/cthoyt/rorio. It automatically updates via a chronological github action, so it doesn't make sense to add in here.
As other ontologies (namely, OBO Foundry ontologies) adopt more granular attribution practices that not only include the ORCID of a person who makes a contribution, but also their affiliation via ROR, having ROR as an ontology itself makes it possible to import the relevant metadata about these ROR identifiers. This makes viewing in ontology tools like Protege much nicer.
I have a whole repository dedicated to converting ROR to an OWL ontology in https://github.com/cthoyt/rorio. It automatically updates via a chronological github action, so it doesn't make sense to add in here.
As other ontologies (namely, OBO Foundry ontologies) adopt more granular attribution practices that not only include the ORCID of a person who makes a contribution, but also their affiliation via ROR, having ROR as an ontology itself makes it possible to import the relevant metadata about these ROR identifiers. This makes viewing in ontology tools like Protege much nicer.
There are also some interesting bits in the code itself, including a function to get the latest version of the bulk dump (https://github.com/cthoyt/rorio/blob/114ad6e4a16f9361bbed21c1f915a01fa79e39db/build.py#L68-L83)
The text was updated successfully, but these errors were encountered: