model time dependent roles of series contributors

[StroemPhi]

With events it is rather straight forward that we can assume a contributor to have a role for the timespan in which the event is being planned and realized. But for series the e.g. creator is not fixed. An organization could be the agent setting up the series and be responsible for it for five years before another organization or a specific person takes over the responsibility of hosting (managing) the series. We need to define if such a switch of organizers must be described in AEON. Also we should think harder about how we define the organizer of a series in real life. Sometimes it is hard to get this info.

[Julian-tib]

The creator of a series in the DataCite Schema is probably what Aliaksandr would call "maintainer": "Just an explanation re „maintainer” – we introduced this term in the Crossref/DataCite Conference PID group to show that this entity/person is responsible for running the conference series and maintaining its metadata. Conference organizer can be a company or local chair who does it once and never involved in the conf again. The maintainer would be the steering committee or the general chair, i.e. this evolves over time." - Email by Aliaksandr 23.07.2021

[StroemPhi]

We need to define another organizer class in AEON that represents the "Maintainer" of an event series, who is defined as having a maintainer role that is defined by the duty to make sure the series will either have another event or that it will be ended. So unlike is the case in the realization of roles associated with an event it is not the process itself (the event series) in which the maintainer role gets realized. It must be another kind of process, one which can either span the whole existence of a series, or, more likely will be a period spanning a couple of events of a series.

@mconlon17 tackled this problem with the following pattern in the WIP ORG Ontology (see Membership): There is a bfo:occurent class representing the 'relationship' which realizes the maintainer role. (Already reported error in this pattern is the superclass bfo:occurent of this 'relationship' class. It must be bfo:process to be within the range/domain of bfo:realized in & bfo:realizes)

For the case where there is only one individual person being the maintainer of an event series (so not an organisation), we need to reuse this pattern in AEON (something like 'single maintainership period') . For the case where there are more people involved in a maintanance period of a series, we could ask Mike for a subclass of 'person membership' (something like 'series maintainer personal membership').