Closed StroemPhi closed 1 year ago
Looking at RO, it seems best to reuse the starts
& ends
and starts with
& ends with
for determining the start and end of an academic event series, as an academic event series always starts with and ends with an event, which is also always a part of the series.
The planned start date and end date of an academic event are being modeled as data properties restricted to the domain of academic event and to the range of xsd:dateTimeStamp
.
Both data properties have a sub-property that can be used to provide a previously planned end or start date for the case that an academic event has been rescheduled.
I don't know if this way of modeling is sufficient wrt to BFO, as in not modeling them as process boundaries. But for our use case in ConfIDent it is sufficient at the moment to just have a data property with this range restriction to annotate academic events.
So far the start and end date of an event is being modeled as a data property of academic event with the range xsd:datetimestamp. This should rather be more general, having a start and end for a process as a process boundary.