defining the contributor roles involved in academic events and series #144
Comments
|
related to #97 |
committee involvement should also be modeled via roles entirely
|
related to data2health/contributor-role-ontology#132 |
StroemPhi
changed the title
StroemPhi
changed the title
* deprecate unneeded contributor defined classes & roles already present in CRO, OMRSE, OBIB and OOSTT * adding relevant event organizer roles * improve labels & text definitions of AEON roles * import committee from OOSTT * deprecate unneeded "has participant" & "participates in" subproperties * #146 was reversed by mistake in the ODK switch thus fixing this * fix typos and add series plan spec * fix wrong prefix of AEON classes * improve EC axiom of event format spec * add EC axiom on series format spec * update import terms * deprecate committee subclasess #144 (due to wrong IRI) * removed some disjointedness of roles for the moment and some EC axioms * delete unneeded interim aeon.ttl * update example individuals
|
There are still some outstanding improvements, such as deciding whether to subsume 'event organizer role' under CRO:'project management role' (CRO:0000065) once data2health/contributor-role-ontology#133 is merged. Yet in order to get forward I've closed this issue and will make new ones for these changes. |
* Update README-editors.md * relabel deprecated classes to be OBO QC conform * fix CI badge link * refresh import modules * #144 forgot to subsume 'event organizer role' under CRO:'contributor role' * delete subclassOf axiom for the clustering of deprecated classes to avoid warings in ROBOT report * delete wrong file * fix wrong IRIs (due to wrong Protégé settings) * check in Protege's alphabetical ordering * update IRI pf example individuls * add Munin2022 and change range of event number to xsd:integer * refactor term IRIs to proper AEON identifiers * add example instances * add 'http://' to example instance IRIs * new Protege order and fix of typo in Munin2022 IRI * add call for submissions and its missing subclasses * add example data * fix wrong subclassOf axiom on organizer and sponsor role * add members of Munin2022 general committee * use ro:member of instead of obi:member of organization in example data * add example data * closes #28, add Twitter handle as data property with example * add annotations * improve readability of definitions & add annotations * relabel AEON_0000134 (general organizing event committee) * delete the 'academic' in front of event in definitions * add 'event series maintainer role' (AEON:0000184), related to #144 * closes #135 * link to #138 * update annotations wrt term status * link to #133 wrt iao:'denoted by' subproperties * adding ISO 3166-1 alpha-2 code as interim identifier class #153
|
This issue needed to be reopened, as the idea to subsume AEON specific roles under CRO:'contributor role' and that under OMRSE:'role in human social processes' was a bad idea. First, using the automated workflows of the ODK causes this subsumption to break whenever a new release is built, as this will also rebuild the CRO module and thus delete the injected subclass of axioms. Second, it is not clear if this axiom injection is event allowed (see also: data2health/contributor-role-ontology#135). Third, there needs to be clarity about how to model such very general social roles the OBO way. As of now COB only reuses SEPIO's 'agent role', but with a new editor note that implies this bearer of this role to be causing the process in which it is involved, whereas the original SEPIO:'agent role' does not go so far. Also it is unclear whether the modeling descisions of roles in OMRSE, which do not link/reuse/or mention CRO at all, can be seen as canonical in OBO. All of this needs to be resolved somehow. So until there is a grand plan on how to best model such social roles in OBO, we will just define them in AEON. |
context:
We need to model the various roles and agents involved in the organization and realization of an academic event. That means we need to be able to say who are/were the organizers, sponsors, speakers, moderators and attendees. As the kind of roles needed in the organization of an academic event are also important in the scope of AEON, e.g. who was responsible for the program or the sponsor acquisition, we need to also model the various roles involved. For this we try to reuse as much of the roles already defined by ontologies such as CRO, OOSTT, OBIB or OMRSE. For now new roles are defined in AEON, but it needs to be discussed in separate issues, in how far these role can rather be defined in other ontologies, such as CRO.
design pattern:
A human or organization is the bearer of a certain role associated with and being realized in an academic event. At first we had defined classes for the agents that have these role, such as "organizer" (defined as
NCBITaxon:'Homo sapiens' or OBI:organization and (RO:'has role' some AEON:'event organizer role'). However, to minimize the complexity and maintenance load, we decided to only use such shadow classes only where it is absolutely necessary, as in the case of event committees.The text was updated successfully, but these errors were encountered: