Skip to main content

event

Version: v26.0608 Namespace: https://behaverse.org/schemas/event

Raw experimental events for cognitive tests, questionnaires, and games. An xAPI-style envelope (actor / verb / object) carrying a single canonical bdm: vocabulary, so one set of analytics tooling can process every domain. Continuous signals (mouse, keyboard, EEG) are referenced via attachments, not inlined.

A Behaverse event is an xAPI Statement — an actor / verb / object envelope — carrying the Behaverse bdm: controlled vocabulary. The envelope is the standard container (defined by xAPI); the vocabulary below is what Behaverse defines. See About for the xAPI background.

Controlled vocabulary — defined by Behaverse

All terms live in the bdm: namespace; the canonical id of initialized is bdm:initialized.

Event envelope (xAPI — external)

These are the standard xAPI Statement fields; Behaverse uses them as-is. They are the container, not what this schema defines — see About.

FieldTypeRequirementDescription
actorobjectrequiredWho or what performed/experienced the event — {objectType, id, name?}, where objectType is one of the actor types below. (Renamed from agent; an Agent is one type of actor — BDM deviation D5.)
verbstringrequiredThe action that occurred, drawn from the canonical verb vocabulary below.
objectobjectrequiredWhat the action was performed on — {objectType, id, name?}, where objectType is one of the object types below.
timestampdatetime (RFC 9557)requiredWhen the event occurred, as an ISO 8601 / RFC 9557 datetime with timezone offset.
resultobjectoptionalThe outcome of the event (e.g. accuracy, response_time, score). Domain-specific payload lives under result.extensions keyed by bdm:* extension keys.
contextobjectoptionalContextual information (study, studyflow, and the session→activity→runtime→block→trial scoping hierarchy) under context.extensions, keyed by bdm:* extension keys.
versionstringoptionalThe associated BDM/schema version (e.g. v26.0608). Typically populated by the LRS.
storeddatetime (RFC 9557)optionalWhen the event was stored in the LRS. Populated by the LRS.
updateddatetime (RFC 9557)optionalWhen the event was last updated in the LRS. Populated by the LRS.
authorityobjectoptionalThe authority that generated the event (e.g. the client app/developer). Populated by the LRS.
attachmentsarrayoptionalReferences to additional files/data associated with the event (stimulus blobs, recording files, timeseries), each with its own metadata. Payloads are not inlined.