saref-core issueshttps://labs.etsi.org/rep/saref/saref-core/-/issues2024-03-06T10:21:11Zhttps://labs.etsi.org/rep/saref/saref-core/-/issues/51V4.1.1: Delete deprecated classes and properties2024-03-06T10:21:11ZMaxime LefrançoisV4.1.1: Delete deprecated classes and propertiesV4.1.1Maxime LefrançoisMaxime Lefrançoishttps://labs.etsi.org/rep/saref/saref-core/-/issues/49Need to represent measurements with more than one value and values without un...2023-06-27T14:13:48ZSocorro BernardosNeed to represent measurements with more than one value and values without unit of measurementIn the COGITO Project we have found a couple of requirements that are currently not being covered by the SAREF ontology.
In construction sites there are tracking devices for workers and equipment that track the location of these resourc...In the COGITO Project we have found a couple of requirements that are currently not being covered by the SAREF ontology.
In construction sites there are tracking devices for workers and equipment that track the location of these resources. The result provided by these devices is a point in space with the location of the resource.
Right now SAREF expects that every measurement has as a result exactly one value (since the range is not defined for saref:value, this is not a problem since the value could be a point) but **SAREF also requires that every measurement has exactly one unit of measurement**. In this case, since points do not have a unit of measurement, they cannot be directly represented in a consistent way.
Furthermore, the tracking devices can provide different values for the same measurement, such as the point directly measured by the device or the point after applying some filtering (e.g., Kalman) to improve the accuracy of the measurement. Since **SAREF requires having exactly one value as the result of a measurement**, this situation cannot be represented in SAREF.
In the COGITO IoT ontology (https://cogito.iot.linkeddata.es/def/iot#) we have partially solved the issue by creating a new class Result and a property hasResult that links the Measurement with a Result. But the restriction on the unit of measurement is still there.https://labs.etsi.org/rep/saref/saref-core/-/issues/48Sampling device as subclass of Device?2022-05-23T05:53:01ZAudun VenneslandSampling device as subclass of Device?In the project Digital-Water.city there is a need for specifying automated sampling devices and their measurements. A description of such devices is provided here: [Automatic Water Samplers](https://www.endress.com/en/field-instruments-o...In the project Digital-Water.city there is a need for specifying automated sampling devices and their measurements. A description of such devices is provided here: [Automatic Water Samplers](https://www.endress.com/en/field-instruments-overview/liquid-analysis-product-overview/automatic-water-samplers). As this might be relevant in other domains besides water management, the change request is added here.https://labs.etsi.org/rep/saref/saref-core/-/issues/35Alignment to SOSA/SSN2019-09-17T05:21:43ZMaxime LefrançoisAlignment to SOSA/SSN**Affects:** SAREF
**Situation:** The TS document contains an alignment to oneM2M base ontology, but not to SOSA/SSN.
**Proposal:** Discuss the alignment with with SOSA/SSN and add in a section after the oneM2M alignment
**Status:** ...**Affects:** SAREF
**Situation:** The TS document contains an alignment to oneM2M base ontology, but not to SOSA/SSN.
**Proposal:** Discuss the alignment with with SOSA/SSN and add in a section after the oneM2M alignment
**Status:** agreed during SmartM2M-RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-04-08 SAREF4Indus and SAREF4Agri already propose mappings, they may be used as starting pointsRaul Garcia-CastroRaul Garcia-Castro