Warning:
This wiki has been archived and is now read-only.
Link between Actuator and ActuatableProperty
Back to Semantic Sensor Network Ontology.
Contents
Old and current implementation
As of 2017-03-08, the old and current links between classes: FeatureOfInterest, xxxProperty, {Actuator/Sensor}, {Actuation/Observation} are represented in the following figure:
Discussions
- Maxime: I do not see a problem with reusing the same name that we already use for the link between Actuation and ActuatableProperty.
- Jano: I would absolutely try to avoid that (having the same name for two totally different issues)
- Maxime: Then why not differentiate them using present vs past: actOnProperty from actuator to ActuatableProperty, and actedOnProperty from actuation to ActuatableProperty
- Maxime: Or making it obvious that the link between Actuator and ActutableProperty is "potential"
Currently proposed options for actuator
- sosa:actsOn/sosa:isActedOnBy
- sosa:mayActOn/sosa:mayBeActedOnBy
- sosa:canActOn/sosa:canBeActedOnBy
- sosa:propertyIsActuatedBy/sosa:actuatesProperty
- ...
Focus on Option 4
- Maxime: I would be happy with consistent like in the figure below, although it may require that some of the old ssn terms are renamed: