Preferred Name |
activity |
|
Synonyms |
|
|
Definitions |
Activity represents the Subject's physical state while interacting with the Context during a Session. This concept describes an Activity performed by the Subject on a specific Session while interacting with a Context. BCI applications monitor the Subject's physical state during the Sessions. This concept identifies the type of Activity that the Subject is performing while recording the data in a Session. Hence, each Session associates a single Subject interactions with a single Context while performing a single Activity. An Activity can be break down as a set of Actions, performed by the Subject while interacting with the Context. |
|
ID |
https://w3id.org/BCI-ontology#Activity |
|
change note |
Status: *STABLE* |
|
definition |
Activity represents the Subject's physical state while interacting with the Context during a Session. This concept describes an Activity performed by the Subject on a specific Session while interacting with a Context. BCI applications monitor the Subject's physical state during the Sessions. This concept identifies the type of Activity that the Subject is performing while recording the data in a Session. Hence, each Session associates a single Subject interactions with a single Context while performing a single Activity. An Activity can be break down as a set of Actions, performed by the Subject while interacting with the Context. |
|
describedby | ||
editorial note |
(*) The concept of Activity is agnostic regarding the number of Subjects engaging in an individual Activity. The ontology clearly defines that the connection between Subjects and Activity(ies) is through Sessions: one Session associates one Subject performing one Activity while interacting with one Context. (*) BCI applications can use this concept as a way to annotate/mark (Marker) the Records (DataSegments). Relationship between Activity and Aspect: (*) Commonly, BCI applications are designed to analyze how an Activity influences an Aspect: it's part of the research scheme and purpose of a BCI application. However, the BCI-O model allows an Activity to be linked with, possibly, multiple Aspects through its Session (a session connects to one activity) and its Records (a session has multiple records, and each record has its own aspect). (*) From the perspective of a BCI application, an Activity has a "main" Aspect to analyze; i.e., multiple Records of the same Session connect to the same Aspect. (*) A SPARQL triple pattern matching that connects Activity(ies) to Aspects would be: ?Session hasActivity ?Activity ?Session hasRecord ?Record ?Record bci:aspectOfInterest ?Aspect |
|
example |
Some subclasses of this concept could be: (*) Glaucoma Tracking: This Activity type is a common example for "pre-screening" of Subjects. (*) Learning: BCI applications can apply different Stimuli (StimulusEvent) to the Subjects. This Activity type is a common example for "interactive" observations. (*) Sleeping: BCI applications don't apply any kind of Stimuli to the Subjects (there are no StimulusEvent). This Activity type is a common example for "running" observations: continuous observations. |
|
isDefinedBy | ||
modified |
2018-05-11T23:42:00 |
|
part |
Session,Subject |
|
preferred label |
activity |
|
prefixIRI |
bci:Activity |
|
scope note |
This class is intended to be the root of a class hierarchy. Domain-specific applications can extend this class hierarchy for their own purposes to describe any relevant Activity classification that Subjects can engage on in Sessions. |
|
StillImage |
Activity.png |
|
title |
Activity |
|
subClassOf |
http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#SpatioTemporalRegion |