diff --git a/documentation/diagrams/SAREF4WEAR figures.drawio b/diagrams/SAREF4WEAR figures.drawio similarity index 100% rename from documentation/diagrams/SAREF4WEAR figures.drawio rename to diagrams/SAREF4WEAR figures.drawio diff --git a/documentation/diagrams/health-status-monitor.drawio b/diagrams/health-status-monitor.drawio similarity index 100% rename from documentation/diagrams/health-status-monitor.drawio rename to diagrams/health-status-monitor.drawio diff --git a/documentation/diagrams/indoor-event.drawio b/diagrams/indoor-event.drawio similarity index 100% rename from documentation/diagrams/indoor-event.drawio rename to diagrams/indoor-event.drawio diff --git a/documentation/diagrams/openair-event.drawio b/diagrams/openair-event.drawio similarity index 100% rename from documentation/diagrams/openair-event.drawio rename to diagrams/openair-event.drawio diff --git a/documentation/description.html b/documentation/description.html new file mode 100644 index 0000000000000000000000000000000000000000..e2e88b8cf1c7eea466d37224f3e264c75cb0f52c --- /dev/null +++ b/documentation/description.html @@ -0,0 +1,123 @@ +

This document presents the implementation of the SAREF extension for the wearables domain (SAREF4WEAR) which based on a limited set of use cases and from available existing data models. This work has been developed in the context of the STF 566 which was established with the goal to create SAREF extensions for the domains of automotive, eHealth and ageing well, wearables, and water.

+ + +

General overview

+ +

Figure 1 presents an overview of the classes and the properties included in the SAREF4WEAR extension.

+ +
+ SAREF4WEAR overview +
Figure 1: SAREF4WEA overview
+
+ + +

Measurement

+ +

As it can be observed in Figure 2, the modelling of measurements in the SAREF4WEAR ontology mostly relies on the measurement model proposed in SAREF.

+ +

The SAREF4WEAR extension requires to be able to represent those devices that measure a certain feature of interest (and those features of interest that are measured by a device) independently of having measures from which this relationship could be inferred. Because of this, in this extension we have created four new properties to relate saref:Device and saref:FeatureOfInterest: s4wear:featureIsMeasuredByDevice, s4wear:featureIsControlledByDevice, s4wear:measuresFeature, and s4wear:controlsFeature.

+ +
+ Measurement model +
Figure 2: Measurement model
+
+ + +

Feature of interest

+ +

The Feature of Interest module describes the different actors that can be equipped with a Wearable device, as presented in Figure 3. We foresee different types of actors: living organisms (s4wear:LivingOrganism) and software (s4wear:Software). There is also a wearer class (s4wear:Wearer) to describe those living organisms that wear some wearable.

+ +

The s4wear:LivingOrganism concept represents any living being that can be equipped with a Wearable device. The s4wear:Software concept represents a program that can be linked with a s4wear:Wearable especially for acquiring information.

+ +

The s4wear:Wearer concept defines any saref:LivingOrganism for which the s4wear:featureIsMeasuredByDevice property subsists, i.e., the s4wear:Wearable device transmits information related to the connected saref:LivingOrganism.

+ +

The s4wear:User concept refers to a saref:FeatureOfInterest for which the s4wear:interactsWith relationship with a s4wear:Wearable individual exists.

+ +
+ Feature of interest model +
Figure 3: Feature of interest model
+
+ + +

Wearable

+ +

SAREF4WEAR defines the s4wear:Wearable abstract concept representing a saref:Device having the capability of being wore by a s4wear:Wearer.

+ +

As depicted in Figure 4, the s4wear:Wearable class subsumes three further concepts with information related to the position of the s4wear:Wearable with respect to its s4wear:Wearer: +

+

+ +

The latter is furtherly specified with the s4wear:TextileBasedWearable concept describing s4wear:Wearable devices integrated into textile products directly.

+ +

The extension also allows to define for a wearable which are the policies (s4wear:Policy) followed by it by means of the s4wear:followsPolicy property.

+ +

Besides, the capabilities of a wearable under specific conditions (ssn-system:SystemCapability), such as its precision or accuracy, can be represented using the ssn-system:hasSystemCapability property.

+ +
+ Wearable model +
Figure 4: Wearable model
+
+ + +

Function

+ +

This model specifies the functions that are considered relevant for the wearables domain. We defined three new concepts that are subsumed by the saref:Function concept and we reuse other functions defined in SAREF, as presented in Figure 5: +

+

+ +
+ Function model +
Figure 5: Function model
+
+ + +

Occurrence

+ +

In some cases, wearables will be able to detect occurrences (s4wear:Occurrence) taking place (s4wear:takesPlaceAt) in a location that is relevant to the wearer (geosp:Feature). These occurrences can be related to the device detecting them through the s4wear:isDetectedBy property, as shown in Figure 6.

+ +

In the context of a smart city, more specific classes can be used from SAREF4CITY, to represent events (s4city:Event, a subclass of s4wear:Occurrence) that take place at (s4city:takesPlaceAtFacility) facilities (s4city:Facility, a subclass of geosp:Feature).

+ +
+ Occurence model +
Figure 6: Occurrence model
+
+ + +

Property

+ +

SAREF4WEAR includes a classification of the different properties that are relevant to the wearables domain, as shown in Figure 7. These properties are classified into wearable (s4wear:WearableProperty), wearer (s4wear:WearerProperty), crowd (s4wear:CrowdProperty), and environment (s4wear:EnvironmentProperty) ones.

+ +

Furthermore, wearable properties are further classified into electrical one (s4wear:ElectricalProperty) that refer to the electric information of a wearable, electrical safety ones (s4wear:ElectricalSafetyProperty) that refer to safety information concerning electrical aspects of wearables, and emission one (s4wear:EmissionProperty) that refer to information about kind of emissions (e.g. noise, temperature, etc.) associated with a wearable.

+ +

The extension defines different individuals for each type of water property; however, this list of individuals does not aim to be exhaustive but to reflect the potential use of the ontology.

+ +
+ Property model +
Figure 7: Property model
+
+ + +

Wearable component

+ +

This model describes some of the components that could be integrated into a s4wear:Wearable device. We foresee different types of components, as depicted in Figure 8: +

+

+ +
+ Wearable component model +
Figure 8: Wearable component model
+
diff --git a/documentation/diagrams/SAREF4WEAR Closed environment event example.png b/documentation/diagrams/SAREF4WEAR Closed environment event example.png new file mode 100644 index 0000000000000000000000000000000000000000..78783d4e2a4571956c49d8fb78c99210e51f9ff4 Binary files /dev/null and b/documentation/diagrams/SAREF4WEAR Closed environment event example.png differ diff --git a/documentation/diagrams/SAREF4WEAR Feature of interest.png b/documentation/diagrams/SAREF4WEAR Feature of interest.png new file mode 100644 index 0000000000000000000000000000000000000000..c846a2ea1c7e46553dac80f6b24de5c841c82e08 Binary files /dev/null and b/documentation/diagrams/SAREF4WEAR Feature of interest.png differ diff --git a/documentation/diagrams/SAREF4WEAR Function.png b/documentation/diagrams/SAREF4WEAR Function.png new file mode 100644 index 0000000000000000000000000000000000000000..ae497ce265e76bea450b3f47542e46ea7ed0d495 Binary files /dev/null and b/documentation/diagrams/SAREF4WEAR Function.png differ diff --git a/documentation/diagrams/SAREF4WEAR Healthcare example.png b/documentation/diagrams/SAREF4WEAR Healthcare example.png new file mode 100644 index 0000000000000000000000000000000000000000..483192a32f9d2d6407c3330f726f1b20c22acb58 Binary files /dev/null and b/documentation/diagrams/SAREF4WEAR Healthcare example.png differ diff --git a/documentation/diagrams/SAREF4WEAR Measurement.png b/documentation/diagrams/SAREF4WEAR Measurement.png new file mode 100644 index 0000000000000000000000000000000000000000..6e8d7a95262568c9ce984a27eb09c91964aa393a Binary files /dev/null and b/documentation/diagrams/SAREF4WEAR Measurement.png differ diff --git a/documentation/diagrams/SAREF4WEAR Occurrence.png b/documentation/diagrams/SAREF4WEAR Occurrence.png new file mode 100644 index 0000000000000000000000000000000000000000..56343045f8cd0ed431fc387c0656e9ea9bb530a5 Binary files /dev/null and b/documentation/diagrams/SAREF4WEAR Occurrence.png differ diff --git a/documentation/diagrams/SAREF4WEAR Open air event example.png b/documentation/diagrams/SAREF4WEAR Open air event example.png new file mode 100644 index 0000000000000000000000000000000000000000..eec68e581cad9f392e285d5b7a9d5558bce69596 Binary files /dev/null and b/documentation/diagrams/SAREF4WEAR Open air event example.png differ diff --git a/documentation/diagrams/SAREF4WEAR Overview.png b/documentation/diagrams/SAREF4WEAR Overview.png new file mode 100644 index 0000000000000000000000000000000000000000..a392085863b4137da511220043eb56ad54f85d5e Binary files /dev/null and b/documentation/diagrams/SAREF4WEAR Overview.png differ diff --git a/documentation/diagrams/SAREF4WEAR Property.png b/documentation/diagrams/SAREF4WEAR Property.png new file mode 100644 index 0000000000000000000000000000000000000000..237c1e6c95691fc2567b93cd96e56e87e5087585 Binary files /dev/null and b/documentation/diagrams/SAREF4WEAR Property.png differ diff --git a/documentation/diagrams/SAREF4WEAR Wearable component.png b/documentation/diagrams/SAREF4WEAR Wearable component.png new file mode 100644 index 0000000000000000000000000000000000000000..fb60cdce7c61c182783f396d3ae92b0523cb342a Binary files /dev/null and b/documentation/diagrams/SAREF4WEAR Wearable component.png differ diff --git a/documentation/diagrams/SAREF4WEAR Wearable.png b/documentation/diagrams/SAREF4WEAR Wearable.png new file mode 100644 index 0000000000000000000000000000000000000000..19a162333eca4f9ef39e8a78eaf6b348c6347523 Binary files /dev/null and b/documentation/diagrams/SAREF4WEAR Wearable.png differ diff --git a/documentation/examples.html b/documentation/examples.html new file mode 100644 index 0000000000000000000000000000000000000000..2e38bcc75021f7925fc7ea2fbd28c2b7c60d0db9 --- /dev/null +++ b/documentation/examples.html @@ -0,0 +1,27 @@ +

In a healthcare scenario the wearer is represented by a user equipped with wearable devices in charge of monitoring healthy parameters (e.g., heart rate, body temperature, blood oxygenation, etc.) and to inform the user in real-time about his/her status. This scenario can be instantiated into different situations ranging from the self-management of chronic diseases to the simple lifestyle monitor.

+ +

The example presented in Figure 9 depicts a wearer (ex:Patient1) who is equipped with a wearable (ex:AccuMed500) that contains a photodetector (ex:Photodetector1); the sensor measures oxygen saturation (ex:OxygenSaturation) through a measurement (ex:OxygenLevel97). A similar example is depicted for a runner wearing a heart rate monitor that measures heart rate.

+ +
+ Healthcare example +
Figure 9: Healthcare example
+
+ +

Another scenario is that of open air public events, which refers to the description of open space public events, such as street festivals, by using the SAREF4WEAR extension. As an example, wearables and sensors are used for measuring the sound level limits, for equipping security staff with the necessary devices for receiving proper information, and for managing the crowd movements around the facility. The management of this challenge can be done by means of a network of wearable devices.

+ +

The example presented in Figure 10 illustrates an event (ex:MusicFestival2020) that takes place in a facility (ex:MusicFestival2020). The facility contains different sound sensors (ex:SoundSensor) and multiple customers (s4wear:User) who are located through individual GPS trackers (ex:GPSTracker). The example also presents a member of the staff (ex:Staff1) who interacts with a crowd control wearable (ex:Receiver1) that is able to measure queue sizes (s4wear:QueueSize); such wearable has detected the queue created by customers in the toilets (ex:ToiletsQueue).

+ +
+ Open air event example +
Figure 10: Open air event example
+
+ +

The closed environment events scenario differs from the previous one due to the environment in which events take place. Here, sensors are used for controlling access, checking the presence of undesired situations (e.g., blazes), and for alerting attendees about emergency situations. At the same time, stewards and security staff members are equipped with wearables for managing communications and for being informed about undesired events (e.g., brawls). Moreover, children could be equipped with wearables for avoiding their loss in the event facility.

+ +

The example presented in Figure 11 illustrates an event (ex:VolleyLeagueFinals) that takes place in a facility (ex:ForumAssago). The facility contains different smoke sensors (ex:SmokeSensor) and multiple customers (s4wear:User) who are located through individual GPS trackers (ex:GPSTracker). The example also presents the head of the staff (ex:StaffHead) who interacts with an audio control wearable (ex:Controller1) that controls the speakers of the facility (ex:FacilitySpeaker1).

+ +
+ Closed environment event example +
Figure 11: Closed environment event example
+
+