Representing a Temporal Context (or recording / trial)

[Mome]

In order to relate the files in NeemHub to results from OpenEASE queries, I would like to express that an instance belongs to one recording (internally we call this a trial).

Previously I saw that other users created a generic physical_task that served as a root task, related to some root-action, and all other actions where sub-actions of this. This works in our case, because we (mostly) always have a root-action per recording (i.e. table-setting). However this must not be case in general.

This is also important to (or maybe the same issue as) finding the right temporal context for an instance, since we are using relative timestamps in our data at the moment (relative to the beginning of the recording).

I found an Episode- or Situation- in SOMA, maybe this is a way to express what we need?

[mpomarlan]

Episode seems the right way to go here.

I would suggest then something like this: in the NEEM, there will exist an Episode individual that is to represent the complete recording.

This individual will connect via dul:includesTime (http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#includesTime) to a TimeInterval individual. The TimeInterval individual will connect via soma:hasIntervalBegin and soma:hasIntervalEnd (http://www.ease-crc.org/ont/SOMA.owl#hasIntervalBegin, http://www.ease-crc.org/ont/SOMA.owl#hasIntervalEnd) to two floats representing the beginning and ending timestamps.

If there are toplevel actions in the recording (in your example, the root action), then the Episode individual connects to these via dul:includesAction (http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#includesAction).

[daniel86]

+1 for using includesAction for all the toplevel actions in an Episode