Admin message

WARNING! Gitlab maintenance operation scheduled for Thursday, 18 June between 19:00 and 20:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.

Modelling Functions and Commands
SAREF4EHAW defines one sub-class of saref:Function and two sub-classes of saref:Command: - s4ehaw:MeasurementFunction rdfs:comment "The functionality necessary to accomplish the measurement task for which a measurement-related health Device (e.g. Sensor, Wearable, ECG Device...) is designed for, e.g. a heart rate measurement function."@en - s4ehaw:AlarmCommand rdfs:comment "A command corresponding to alarm sending."@en - s4ehaw:ReminderCommand rdfs:comment "Command used for sending reminder notifications to health actors, e.g. patients, users or Caregivers."@en Commands are low-level directives that a device implements, and are logically grouped in functions. ## MeasurementFunction Remarks: - this definition assumes the existence of a Task named "measurement" - class Measurement is deprecated (See #14 ) - the name is generic but the definition focuses on health Devices ## Commands The name of commands look more like functions, and some specific commands could be defined for each ``` :AlarmFunction a saref:Function . :TriggerAlarm a saref:Command ; saref:isCommandOf :AlarmFunction . :SnoozeAlarm a saref:Command ; saref:isCommandOf :AlarmFunction . ... :ReminderFunction a saref:Function . :SendReminder a saref:Command ; saref:isCommandOf :ReminderFunction . ... ```
issue