Warning:
This wiki has been archived and is now read-only.

Actuation

From Spatial Data on the Web Working Group

Jump to: navigation, search

1 Actuation and Actuators in SOSA
2 Question 1:
- 2.1 Discussions
- 2.2 Currently proposed options
3 Question 2: naming of xxxProperty --> Resolved
4 Question 3: naming of the link between Actuation and ActuatableProperty --> Resolved
5 Question 3': naming of the link between Observation and ObservableProperty
6 Question 4: naming of the link between Actuation and Actuator --> Resolved
7 Question 4': naming of the link between Observation and Sensor
8 Question 5: Result and Command ?
9 Question 6: phenomenonTime and resultTime
10 Question 7: axioms in SSN
11 Question 8: measurement properties in SSN
12 Question 9: operating properties in SSN
13 Question 10: naming of the link between Actuator and ActuatableProperty
14 Question 10': naming of the link between Sensor and ObservableProperty
15 Pointers to Related Work

Actuation and Actuators in SOSA

This page documents proposed changes to the current (Feb 12, 2017) version of SOSA. The changes address a few shortcomings of the current version, e.g., as raised by Maxime. There are two main changes by which SOSA:actuatedProperty and SOSA:ActuableProperty are introduced. Finally, and as a small update, the definition of FeatureOfInterest is broadened. This task is in preparation for (potentially) introducing a deeper axiomatization for Actuators and Actuation in the new SSN. This document, however, only describes modifications to be made to SOSA. See also Issue-91. Use cases for actuators and actuation can be found at Data on the Web Use Cases & Requirements. Some notes are listed below:

Error creating thumbnail: Unable to save thumbnail to destination

For sake of simplicity, this concept map does not show inverse properties although they are defined in SOSA.
Please keep in mind that everything that is not shown in a dashed style is already part of SOSA.
With respect to SOSA:Result, this assumes we pick option 3 (or 5, or 6): https://www.w3.org/2015/spatial/wiki/Storing_Observation_Value ; see also https://lists.w3.org/Archives/Public/public-sdw-wg/2017Feb/0319.html.
With respect to ActuableProperty See also http://ontologydesignpatterns.org/wiki/Submissions:Actuation-Actuator-Effect (SAN) and https://w3id.org/seas/DeviceOntology. SAN (https://www.irit.fr/recherches/MELODI/ontologies/SAN.html) is explicitly inspired by the SSO pattern of the old SSN and aligns very well with the proposal above (and the current state of SOSA).
FeatureOfInterest needs a tiny change in the definition, see https://github.com/w3c/sdw/pull/549. This also addresses Maxime's request (https://lists.w3.org/Archives/Public/public-sdw-wg/2017Feb/0090.html)
The proposal above will be encoded and made available as a new push request to sosa.ttl (please do not accept the request before our telco as it will likely be modified in some way or another).
Please keep in mind that these are change requests for SOSA, i.e., the minimal and lightweight model. We do not aim at being feature-complete here in any sense. More proposed updates (for SSN) will follow.

UPDATE (02/20/17) SOSA:ActuableProperty changed to SOSA:ActuatableProperty (see, e.g., https://lists.w3.org/Archives/Public/public-sdw-wg/2017Feb/0361.html); actuatedProperty SOSA:actuatedProperty changed to SOSA:actsOnProperty (see, e.g., question 3 below). Please note that these changes are introduced in order to find common ground and to act as a basis for discussions, they do not reflect any official decision by the group (as of 02/20/17). The old figure remains available at: concept map.

sosa.ttl


sosa:ActuatableProperty
 rdf:type rdfs:Class ;
 rdf:type owl:Class ;
 rdfs:comment "An actuatable property, i.e., characteristic, of a FeatureOfInterest."@en ;
 rdfs:label "Actuatable Property"@en ;
 skos:definition "An actuatable property, i.e., characteristic, of a FeatureOfInterest."@en ;
 skos:example "A window actuator acts by changing the state between a frame and a window. The ability of the window to be opened or closed is its ActuatableProperty."@en .

sosa:actsOnProperty
 rdf:type owl:ObjectProperty ;
 schema:domainIncludes sosa:Actuation ;
 schema:rangeIncludes sosa:ActuatableProperty ;
 rdfs:comment "Relation between an Actuation and the property of a Feature Of Interest it is acting upon."@en ;
 rdfs:label "acts on property"@en ;
 owl:inverseOf sosa:isActedOnBy ;
 skos:definition "Relation between an Actuation and the property of a Feature Of Interest it is acting upon."@en ;
 skos:example "In the activity (Actuation) of automatically closing a window if the temperature in a room drops below 20 degree Celsius, the 
 property on which the Actuator acts upon is the state of the window as it changes from being open to being closed. "@en .

The skos:examples provided here are based on the 4.48 Smart Cities use case, more specifically on the item 3. Stimulating green behavior.

UPDATE (02/21/17) The changes we voted on have been reflected in the following pull request: PR571

Question 1:

ok for a complete actuator/actuation/xxxProperty model in sosa ?

ok to reflect this in snn ?

Discussions

Kerry: What is the impact on SSN?

- Maxime: should we duplicate any axiom that exists for Observation and adapt it for Actuation?

Kerry: suggest you just do so -- I don't think anyone is objecting to Actuation modelling in SSN and this schematic seems approved of. There has been some requests for "command" and also thinking of this would be helpful, I think: https://w3c.github.io/wot/current-practices/wot-practices.html#interaction-patterns