Open StroemPhi opened 3 years ago
for batch term requests to CRO see: https://github.com/data2health/contributor-role-ontology/issues/120
We also need to look into the sepio:'agent role' as it seems to represent what we have in mind with aeon:'contributor role' and also because it seems to be used in COB.
https://github.com/data2health/contributor-role-ontology/issues/14 sheds some light on how to best model the contributor roles
For the remaining and very context dependent contributor roles, I think it's best to bring AEON to a stage where it can be submitted to OBO first, before actually requesting these to be rather defined in CRO. This way the OBO reviewers or CRO developers can properly inspect AEON's roles and decide/suggest, if it better fits the scope of CRO. Until then they will be marked with the status ''requires discussion''.
What also needs to be decided before AEONs first stable release is if it is even ok to subsume CRO's 'contributor role' under BFO:role (see https://github.com/data2health/contributor-role-ontology/issues/135).
The roles defined in AEON that are needed for representing the realization of academic events and event series should better be modeled in CRO .