Task Schema

[smakeig]

HED Task events

HED events must include 'Task Events' allowing the definition of the cognitive significance of e.g. sensory events in terms of participant intent - typically as defined by the task(s) they are performing. Thus, a task event demarcates, first of all, a time period in which a participant is performing a defined task. HED task events can allow some sort of task definition, involving task categorization, etc. - a difficult task in abstract, but likely possible to make work for the large majority of existing dataset tasks.

HED Cognitive events

Complementing task events, HED needs some form of Cognitive Events.

 For example, in "One-back" tasks, participants are typically asked to respond in some manner to the second of two consecutive stimuli, delivered within some stimulus stream, that share some property (ex: "Respond to the second of any two identical letter stimuli."). In such a task, the appearance of each stimulus belonging to the targeted stimulus stream initiates a 'cognitive event', the _active anticipation_ and _response preparation_ of the succeeding stream stimulus sharing the same class characteristic, thereby cueing the task-defined response (action such as button press, mental count increment, etc.).

[neuromechanist]

@arnodelorme, This is highly relevant to EEGDASH effort to annotate the task type, and could actually ground those based on the a reproducible schema.