saref-core issueshttps://labs.etsi.org/rep/saref/saref-core/-/issues2019-11-12T07:54:22Zhttps://labs.etsi.org/rep/saref/saref-core/-/issues/40Features of Interest2019-11-12T07:54:22ZMaxime LefrançoisFeatures of InterestHow should we add features of interest in SAREF v3?
relates to issue #29 , #5 , MR !24How should we add features of interest in SAREF v3?
relates to issue #29 , #5 , MR !24v3.1.1Maria PovedaMaria Povedahttps://labs.etsi.org/rep/saref/saref-core/-/issues/50Typo in rdfs:label2024-03-05T10:00:52ZHelen RawsthorneTypo in rdfs:labelIncorrect `rdfs:label` on line 767 in file https://labs.etsi.org/rep/saref/saref-core/-/blob/develop-v3.2.1/ontology/saref.ttl
```turtle
saref:hasPropertyKind a owl:ObjectProperty ;
rdfs:label "has feature kind"@en ;
rdfs:commen...Incorrect `rdfs:label` on line 767 in file https://labs.etsi.org/rep/saref/saref-core/-/blob/develop-v3.2.1/ontology/saref.ttl
```turtle
saref:hasPropertyKind a owl:ObjectProperty ;
rdfs:label "has feature kind"@en ;
rdfs:comment "links a property of interest to its kind, a property."@en ;
rdfs:domain saref:PropertyOfInterest ;
rdfs:range saref:Property .
```https://labs.etsi.org/rep/saref/saref-core/-/issues/45Wrong figure in documentation2020-07-17T08:21:31ZRaul Garcia-CastroWrong figure in documentationBUG spotted by Anna Lin (UGent-imec) Anna.Lin@UGent.be
Whilst reading your documentation (https://saref.etsi.org/core/v3.1.1/) I noticed that the Figure 3 mentioned there shows the exactly same content as Figure 2 (and from the descript...BUG spotted by Anna Lin (UGent-imec) Anna.Lin@UGent.be
Whilst reading your documentation (https://saref.etsi.org/core/v3.1.1/) I noticed that the Figure 3 mentioned there shows the exactly same content as Figure 2 (and from the description of the text I think it should show the device types (actuators, sensors, meters and appliances).https://labs.etsi.org/rep/saref/saref-core/-/issues/3Delete terms not used in the SAREF extensions2019-12-10T11:19:41ZMaxime LefrançoisDelete terms not used in the SAREF extensions**Situation:** Some terms are not used in the SAREF extensions, but may be used by users of SAREF:
- `saref:hasDescription`
- `saref:hasName` (hasName is now actually encoded inside the URI of the class)
- `EnergyRelated`, `FunctionRela...**Situation:** Some terms are not used in the SAREF extensions, but may be used by users of SAREF:
- `saref:hasDescription`
- `saref:hasName` (hasName is now actually encoded inside the URI of the class)
- `EnergyRelated`, `FunctionRelated`, `BuildingRelated`
**Proposal:** To delete these terms, and anywhere in the spec where `saref:hasDescription` is used, recommend the use of `dcterms:description` instead.
**Status:**
- `hasDescription` and `hasName`: agreed during SmartM2M-RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-04-08
- other classes: agreed during SmartM2M-2nd RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-05-06Raul Garcia-CastroRaul Garcia-Castrohttps://labs.etsi.org/rep/saref/saref-core/-/issues/22units of measure are just examples2019-11-11T18:47:02ZMaxime Lefrançoisunits of measure are just examples**Affects:** SAREF
**Situation:** SAREF contains the axiom
```
saref:UnitOfMeasure rdfs:isDefinedBy <http://www.wurvoc.org/vocabularies/om-1.6/Unit_of_measure> .
```
and all the instances of units of measures that serve as examples...**Affects:** SAREF
**Situation:** SAREF contains the axiom
```
saref:UnitOfMeasure rdfs:isDefinedBy <http://www.wurvoc.org/vocabularies/om-1.6/Unit_of_measure> .
```
and all the instances of units of measures that serve as examples are from OM v 1.8. However, these instances and this annotation are not present in the SAREF TS. The SAREF core ontology should not take one ontology of units of measure specifically. Examples may be provided in a separate document. OM had a v 1.8, now v 2.0 is under development. Alternatives include QUDT or the cdt:ucum datatype.
**Proposal:** The specification is agnostic of the way of representing units. The ontology file should also be agnostic. Examples of the use of OM will be moved to specific instance files using the ontology under consideration and that people can download to understand how SAREF can be used
**Status:** agreed during SmartM2M-2nd RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-05-06 . updated during SmartM2M-3rd RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-05-09Raul Garcia-CastroRaul Garcia-Castrohttps://labs.etsi.org/rep/saref/saref-core/-/issues/15Add domain or range of properties when unambiguous2019-12-05T14:17:55ZMaxime LefrançoisAdd domain or range of properties when unambiguous**Affects:** SAREF
**Situation:** It is clear from some definitions of properties what the subject and/or the object is. If some SAREF user uses them differently, it may lead to interoperability issues.
- saref:accomplishes: A relations...**Affects:** SAREF
**Situation:** It is clear from some definitions of properties what the subject and/or the object is. If some SAREF user uses them differently, it may lead to interoperability issues.
- saref:accomplishes: A relationship between a certain entity (e.g., a device) and the task it accomplishes
From this definition, it is unambiguous that the object of a saref:accomplishes relationship is always a task.
- saref:accomplishes - A relationship between a certain entity (e.g., a device) and the task it accomplishes
- domain is saref:Command and range is saref:State
- saref:actsUpon - A relationship between a command and a state
- domain saref:Command, range saref:State
- saref:controlsProperty - A relationship specifying the Property that can be controlled by a certain Device
- domain saref:Device, range saref:Property
- saref:hasCommand - A relationship between an entity (such as a function) and a command
- domain saref:Function and range saref:Command
- saref:hasFunction - A relationship identifying the type of function of a device
- domain saref:Device and range saref:Function
- saref:hasMeterReading - A relationship between a metering function and the measurement of the reading
- domain saref:MeteringFunction and range saref:Measurement.
- saref:hasMeterReadingType - A relationship identifying the reading type of a measurement (e.g., Water, Gas, Pressure , Energy , Power, etc.)
- domain saref:Measurement and range saref:Property
- saref:hasPrice - A relationships indentifying the price associated to an entity
- range saref:Price
- saref:hasProfile - A relationship associating a profile to a certain entity (e.g., a device)
- domain saref:Device and range saref:Profile
- saref:hasSensingRange - A relationship between a sensing function and a measurement identifying the range of a sensor detection
- domain saref:SensingFunction and range saref:Measurement
- saref:hasSensorType - A relationship identifying the sensing type of a sensor detection (i.e., Temperature, Occupancy, Humidity, Motion , Smoke, Pressure, etc.)
- domain saref:SensingFunction and range Property
- saref:hasState - A relationship identifying the type of state of a device
- domain saref:Device and range saref:State
- saref:hasThresholdMeasurement - A relationship associated with an event function to notify that a certain threshold measurement has been exceeded
- domain saref:EventFunction and range saref:Measurement
- saref:hasTime - A relationship to associate time information to an entity
- range saref:Time
- saref:isAccomplishedBy - A relationship identifying the task accomplished by a certain entity (e.g., a device)
- domain saref:Task
- saref:isCommandOf - A relationship between a command and a function.
- domain saref:Command and range saref:Function
- saref:isControlledByDevice - A relationship specifying the devices that can control a certain property
- domain saref:Property and range saref:Device
- saref:isMeasuredByDevice - A relationship specifying the devices that can measure a certain property
- domain saref:Property and range saref:Device
- saref:isMeasuredIn - A relationship identifying the unit of measure used for a certain entity.
- domain saref:Measurement and range saref:UnitOfMeasure
- saref:isOfferedBy - A relationship between a service and a device that offers the service
- domain saref:Service and range saref:Device
- saref:makesMeasurement - A relation between a device and the measurements it makes. Such measurement will link together the value of the measurement, its unit of measure and the property to which it relates.
- domain saref:Device and range saref:Measurement
- saref:measuresProperty - A relationship specifying the Property that can be measured by a certain Device
- domain saref:Device and range saref:Property
- saref:offers - A relationship between a device and a service
- domain saref Device and range saref:Service
- saref:relatesToMeasurement - A relationship between a property and the measurements it relates to
- domain saref:Property and range saref:Measurement
- saref:relatesToProperty - A relationship between a measurement and the property it relates to
- domain saref:Measurement and range saref:Property
- saref:represents - A relationship between a service and a function.
- domain saref:Service and range saref:Function
**Proposal:** To add ObjectPropertyDomain and ObjectPropertyRange axioms wherever the definition of a property unambiguously identifies the domain or the range of a property.
**Status:** agreed during SmartM2M-RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-04-08Raul Garcia-CastroRaul Garcia-Castrohttps://labs.etsi.org/rep/saref/saref-core/-/issues/5Clarify descriptions of some terms2019-11-07T10:50:50ZMaxime LefrançoisClarify descriptions of some termsSome term definitions can be clarified to avoid misunderstandings:
- (The definition of EventFunction is too strict compared to what the name suggests)
- EventFunction - A function that allows to notify another device that a certain t...Some term definitions can be clarified to avoid misunderstandings:
- (The definition of EventFunction is too strict compared to what the name suggests)
- EventFunction - A function that allows to notify another device that a certain threshold value has been exceeded
- **Proposal:** change definition to: A function that allows to notify another device that some event occurred, for example that a certain threshold value has been exceeded
- (saref:isUsedFor is used to link devices to commodities. Not to control function or command)
- saref:isUsedFor - A relationship specifying the purpose for which a device is used for (e.g., controlling a Commodity)
- **Proposal:** change definition to: A relationship specifying the commodity for which a device is used for
- (Only properties can be measured in Profiles. Also, no record of usage of Profiles for Commodity in SAREF4ENER the only use of Profile is for the property Power)
- Profile - about a certain Property (e.g., Energy) or Commodity (e.g. Water)
- **Proposal:** change definition to: about a certain Property (e.g., Energy)
- (Enforces the consistency of the definitions of the functions)
- LevelControlFunction - An actuating function that allows to do level adjustments of an actuator in a certain range (e.g., 0%-100%), such as dimming a light or set the speed of an electric motor.
- **Proposal:** change definition to: An actuating function that allows to do level adjustments of the property of a device or a feature of interest in a certain range (e.g., 0%-100%), such as dimming the light in a room or setting the speed of an electric motor.
- (hasCommand and isCommandOf are inverse one of another. the subject of a saref:hasCommand relationship will most often be automatically classified as a saref:Function. This may lead to bugs in systems.)
- saref:hasCommand - A relationship between an entity (such as a function) and a command
- saref:isCommandOf - A relationship between a command and a function.
- **Proposal:** change definition of saref:hasCommand to: A relationship between a function and a command
- Device instances will be linked to function instances. Not function types. If some SAREF user uses them differently, it may lead to interoperability issues.
- saref:hasFunction - A relationship identifying the type of function of a device
- **Proposal:** change definition to: A relationship identifying the function of a device
- (only saref:Device can be associated with profiles)
- saref:hasProfile - A relationship associating a profile to a certain entity (e.g., a device)
- **Proposal:** change definition to: A relationship associating a profile to a certain device or feature of interest
- (This is misleading as this is a class, not an instance. There is usually more than one unit of measure for a quantity kind)
- saref:Currency - The unit of measure for price
- **Proposal:** change definition to: The class of units of measures for price
Proposal: To update the term definitions.
**Status:** agreed during SmartM2M-RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-04-08Raul Garcia-CastroRaul Garcia-Castrohttps://labs.etsi.org/rep/saref/saref-core/-/issues/21relatesToMeasurement and relatesToProperty should be inverse one of another2019-09-17T13:31:00ZMaxime LefrançoisrelatesToMeasurement and relatesToProperty should be inverse one of another**Affects:** SAREF
**Situation:** from the definitions of relatesToMeasurement and relatesToProperty, it should be clear that these two properties are inverse one of another.
- saref:relatesToMeasurement - A relationship between a prop...**Affects:** SAREF
**Situation:** from the definitions of relatesToMeasurement and relatesToProperty, it should be clear that these two properties are inverse one of another.
- saref:relatesToMeasurement - A relationship between a property and the measurements it relates to
- saref:relatesToProperty - A relationship between a measurement and the property it relates to
**Proposal:** Add the axiom: `inverseOf( saref:relatesToMeasurement saref:relatesToProperty )`.
**Status:** agreed during SmartM2M-RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-04-08Raul Garcia-CastroRaul Garcia-Castrohttps://labs.etsi.org/rep/saref/saref-core/-/issues/18definition of EventFunction is too restrictive2019-09-17T13:26:58ZMaxime Lefrançoisdefinition of EventFunction is too restrictive**Affects:** SAREF
**Situation:** the definition of EventFunction is "A function that allows to notify another device that a certain threshold value has been exceeded.". However, there may be other kind of event functions such as to det...**Affects:** SAREF
**Situation:** the definition of EventFunction is "A function that allows to notify another device that a certain threshold value has been exceeded.". However, there may be other kind of event functions such as to detect when a person passes through a door.
Proposal: to rewrite the definition
**Status:** agreed during SmartM2M-RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-04-08Raul Garcia-CastroRaul Garcia-Castrohttps://labs.etsi.org/rep/saref/saref-core/-/issues/23Examples should be moved away from SAREF-core2019-12-05T14:17:56ZMaxime LefrançoisExamples should be moved away from SAREF-core**Affects:** SAREF
**Situation:** The SAREF ontology contains many examples of devices like WashingMachine
However, these instances and their annotation are not present in the SAREF TS. There is no evidence of usage of these concepts i...**Affects:** SAREF
**Situation:** The SAREF ontology contains many examples of devices like WashingMachine
However, these instances and their annotation are not present in the SAREF TS. There is no evidence of usage of these concepts in other SAREF extensions
**Proposal:** Move the examples to additional resources/documentation and not in the ontology. Only keep Actuator Appliance Sensor Meter, keep HVAC (maybe remove it in the future, add in the comment that there is a link with saref4bldg). Remove LightingDevice, remove MicroRenewable, remove Multimedia but create an example about Multimedia. remove Network.
**Status:** agreed during SmartM2M-2nd RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-05-06Raul Garcia-CastroRaul Garcia-Castrohttps://labs.etsi.org/rep/saref/saref-core/-/issues/24range of hasValue should not be xsd:float.2019-10-02T10:05:30ZMaxime Lefrançoisrange of hasValue should not be xsd:float.**Affects:** SAREF
**Situation:** SAREF contains axiom Range( hasValue xsd:float ). However, there are other datatypes for measurements. Some domains require the precision of doubles. One may use the cdt:ucum datatype to associate a val...**Affects:** SAREF
**Situation:** SAREF contains axiom Range( hasValue xsd:float ). However, there are other datatypes for measurements. Some domains require the precision of doubles. One may use the cdt:ucum datatype to associate a value. The number of persons in a building would be an integer. Other types of property may be thought about, like vectors (x, y, z acceleration), matrices (strain in deformable solids)
**Proposal:** remove the axiom. Update the definition of hasValue to specify that numeric values are expected to enable reasoning
**Status:** agreed during SmartM2M-2nd RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-05-06Raul Garcia-CastroRaul Garcia-Castrohttps://labs.etsi.org/rep/saref/saref-core/-/issues/38I would like a concept for washing machine2019-11-12T07:54:37ZMaxime LefrançoisI would like a concept for washing machineThis is important because I don't like to wash dishes by hand.This is important because I don't like to wash dishes by hand.Laurent VelezLaurent Velezhttps://labs.etsi.org/rep/saref/saref-core/-/issues/14Are tasks accomplished by at least one device ?2019-07-22T14:04:40ZMaxime LefrançoisAre tasks accomplished by at least one device ?**Affects:** SAREF
**Situation:** The axiom below states that each and every task is accomplished by at least one device. This restriction is too strong and not necessary. One should be able to describe a task even if no device accompli...**Affects:** SAREF
**Situation:** The axiom below states that each and every task is accomplished by at least one device. This restriction is too strong and not necessary. One should be able to describe a task even if no device accomplishes it.
```
Axiom subClassOf( saref:Task ObjectMinCardinality ( 1 saref:isAccomplishedBy saref:Device ) )
```
**Proposal:** To remove these axioms.
**Status:** agreed during SmartM2M-2nd RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-05-06Raul Garcia-CastroRaul Garcia-Castrohttps://labs.etsi.org/rep/saref/saref-core/-/issues/11DoorSwitch both is a Switch and consistsOf Switch2019-07-22T14:04:22ZMaxime LefrançoisDoorSwitch both is a Switch and consistsOf Switch**Affects:* SAREF
**Situation:** From the combination of the two axioms below, a SAREF user may induce that there are two distinct switches. This would lead to wrong classification, and potentially make a knowledge graph inconsistent.
...**Affects:* SAREF
**Situation:** From the combination of the two axioms below, a SAREF user may induce that there are two distinct switches. This would lead to wrong classification, and potentially make a knowledge graph inconsistent.
```
Axiom subClassOf( DoorSwitch Switch )
Axiom subClassOf( DoorSwitch someValuesFrom( consistsOf Switch ) )
```
Other concepts have the same situation: EnergyMeter is asserted to be both a Meter and some device that consists of a Meter
**Proposal:** Remove the second axiom, for each of the impacted concepts
**Status:** agreed during SmartM2M-2nd RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-05-06Raul Garcia-CastroRaul Garcia-Castrohttps://labs.etsi.org/rep/saref/saref-core/-/issues/41Move examples of devices and functions out of SAREF core2024-03-05T10:00:12ZRaul Garcia-CastroMove examples of devices and functions out of SAREF coreMany terms under `saref:Device` still look more like examples and should be deleted from the core and moved to examples.
Namely:
* Door switch, light switch, smoke sensor, temperature sensor
* HVAC
* Appliance
This also applies to s...Many terms under `saref:Device` still look more like examples and should be deleted from the core and moved to examples.
Namely:
* Door switch, light switch, smoke sensor, temperature sensor
* HVAC
* Appliance
This also applies to specific functions below actuating function.https://labs.etsi.org/rep/saref/saref-core/-/issues/9Clarify link between service and command2024-03-05T09:56:48ZMaxime LefrançoisClarify link between service and command**Situation:** there is no clear relationship between concepts switchOnService and OnCommand, although their name suggests there is. There is nothing specific about “On” in the description.
**Proposal:** Clarify/document the relationshi...**Situation:** there is no clear relationship between concepts switchOnService and OnCommand, although their name suggests there is. There is nothing specific about “On” in the description.
**Proposal:** Clarify/document the relationships between services, functions and commands in the documentation.Explain the link is in oneM2M.
**Status:** agreed during SmartM2M-2nd RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-05-06. Open question: keep service in SAREF, or just import oneM2M , or just reuse a subset of oneM2M terms, without importing it ?Raul Garcia-CastroRaul Garcia-Castrohttps://labs.etsi.org/rep/saref/saref-core/-/issues/31commands can act upon other states2019-07-22T13:48:44ZMaxime Lefrançoiscommands can act upon other states**Affects:** SAREF
**Situation:** SAREF contains axioms `subClassOf( ?someCommand AllValuesFrom( actsUpon ?someState ) )`. However, for example, an actuating function may act on other states by transitivity (e.g., a heater actsUpon temp...**Affects:** SAREF
**Situation:** SAREF contains axioms `subClassOf( ?someCommand AllValuesFrom( actsUpon ?someState ) )`. However, for example, an actuating function may act on other states by transitivity (e.g., a heater actsUpon temperature and humidity, as temperature and humidity are coupled). If a user asserts that an actuating function acts on two distinct properties, then the knowledge base will be inconsistent. Other example: an actuating function should also be capable of changing the property of a feature of interest (ex. the temperature of the heater, which may be linked to a state of the heater cold or hot).
**Proposal:** change the axioms to `subClassOf( ?someCommand SomeValuesFrom( actsUpon ?someState ) )`
**Status:** agreed during SmartM2M-3rd RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-05-09Raul Garcia-CastroRaul Garcia-Castrohttps://labs.etsi.org/rep/saref/saref-core/-/issues/12Bug in LightSwitch2019-07-22T14:05:51ZMaxime LefrançoisBug in LightSwitch**Affects:** SAREF
**Situation:** A LightSwitch is classified as an actuator. It does not measure light. But SAREF contains the following axiom:
```
Axiom subClassOf( LightSwitch SomeValuesFrom( measuresProperty Light) )
```
**Propos...**Affects:** SAREF
**Situation:** A LightSwitch is classified as an actuator. It does not measure light. But SAREF contains the following axiom:
```
Axiom subClassOf( LightSwitch SomeValuesFrom( measuresProperty Light) )
```
**Proposal:* Replace with controlsProperty.
**Status:** agreed during SmartM2M-2nd RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-05-06Raul Garcia-CastroRaul Garcia-Castrohttps://labs.etsi.org/rep/saref/saref-core/-/issues/28a metering function may have other commands than the three currently specified2019-07-22T14:05:01ZMaxime Lefrançoisa metering function may have other commands than the three currently specified**Affects:** SAREF
**Situation:** Some axioms are to restrictive in SAREF:
- axiom `SubClassOf( MeteringFunction AllValuesFrom( hasCommand UnionOf ( saref:GetCurrentMeterValueCommand saref:GetMeterDataCommand saref:GetMeterHistoryComm...**Affects:** SAREF
**Situation:** Some axioms are to restrictive in SAREF:
- axiom `SubClassOf( MeteringFunction AllValuesFrom( hasCommand UnionOf ( saref:GetCurrentMeterValueCommand saref:GetMeterDataCommand saref:GetMeterHistoryCommand ) ) )`, which means that if a metering function has a command, then this command is a GetCurrentMeterValueCommand , a GetMeterDataCommand , or a GetMeterHistoryCommand. However, a metering function may have other commands than these three (ex. saref-ext:GetLast10MeterValueCommand ) . If a SAREF user adds such a command, then it would be wrongly classified as one of the three. This may lead to knowledge base inconsistencies.
- **Proposal:** change the axiom to
- `subClassOf( GetCurrentMeterValueCommand AllValuesFrom( isCommandOf MeteringFunction ) )`, which means: the command GetCurrentMeterValueCommand is a command of the function MeteringFunction
- axiom `subClassOf( EventFunction AllValuesFrom( hasCommand NotifyCommand)`. However, a event function may have other commands than the notify command (ex. saref-ext:SetMaxRateCommand saref-ext:SetBurstValueCommand ) . If a SAREF user adds such a command, thaen it would be wrongly classified. This may lead to knowledge base inconsistencies. At least, the NotifyCommand is always a command of the EventFunction function
- **Proposal:** change the axiom to
- `subClassOf( NotifyCommand AllValuesFrom( isCommandOf EventFunction)`.
- `axiom subClassOf( SensingFunction AllValuesFrom( hasCommand GetSensingDataCommand)`. However, a sensing function may have other commands than the get sensing data command. If a SAREF user adds such a command, then it would be wrongly classified. This may lead to knowledge base inconsistencies
- **Proposal:** change the axiom to
- `subClassOf( GetSensingDataCommand SomeValuesFrom( isCommandOf SensingFunction)`
- axiom `subClassOf( OnOffFunction AllValuesFrom( hasCommand UnionOf( saref:OffCommand saref:OnCommand saref:ToggleCommand))`. Same problem as above.
- **Proposal:** change the axioms, except for Toggle, which may be a command for other functions, like saref-ext:HotColdFunction.
- Axiom `subClassOf( OffCommand AllValuesFrom( isCommandOf OnOffFunction)`
- Axiom `subClassOf( OnCommand AllValuesFrom( isCommandOf OnOffFunction)`
- Axiom `subClassOf( ToggleCommand AllValuesFrom( isCommandOf OnOffFunction)`
- This also applies to:
- OpenCloseFunction and the commands OpenCommand and CloseCommand.
- StartStopFunctionand and the commands StartCommandand StopCommand.
- LevelControlFunction and the commands SetAbsoluteLevel SetRelativeLevelCommand StepDownCommand StepUpCommand.
**Proposal:** rewrite the axioms
**Status:** agreed during SmartM2M-3rd RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-05-09Raul Garcia-CastroRaul Garcia-Castrohttps://labs.etsi.org/rep/saref/saref-core/-/issues/13Use of saref:accomplishes2019-07-22T13:48:05ZMaxime LefrançoisUse of saref:accomplishes**Affects:** SAREF
**Situation:** there exists temperature sensors who are not meant to accomplish comfort. But SAREF contains the following axiom:
```
Axiom subClassOf( TemperatureSensor HasValue( accomplishes Comfort) )
```
This ha...**Affects:** SAREF
**Situation:** there exists temperature sensors who are not meant to accomplish comfort. But SAREF contains the following axiom:
```
Axiom subClassOf( TemperatureSensor HasValue( accomplishes Comfort) )
```
This happens in other places too, where the axiom was meant to provide examples, but has unwanted logical implications.
**Proposal:** Delete these axioms, and add a sentence at the end of the definitions to give an example of the task they can accomplish
**Status:** agreed during SmartM2M-2nd RG Meeting about 2 NWIs SAREFv3 and SAREF Com Framework V2 2019-05-06Raul Garcia-CastroRaul Garcia-Castro