Re: Actuation and Actuators in SOSA (issue-91)

Dear Jano,

Great work, I would be happy that SOSA includes a bit more material about
Actuation and Actuators, your propoal goes in the right direction.

Requirement 5.27 [1] seems to assume that only actuators that are also
sensors are in the scope of SOSA/SSN. Is it OK to relax this restriction a
little ?

I would be more comfortable in voting for some actual turtle snippets,
could you please add those that reflect your proposal, and maybe add more
options ?

I expect questions/votes to be raised shortly about the following related
aspects:
 1.  add a property sosa:hasCommand and class sosa:Command ?
 2. how shall the relations that link Actuation/Actuator ,
Observation/Sensor, be named ? should there be a total of four properties,
or could two suffice ?
 3. shall we try to stick to a uniform naming convention for properties
whenever possible ?

Kind regards,
Maxime

[1] - https://www.w3.org/TR/sdw-ucr/#ModelActuation



Le lun. 13 févr. 2017 à 00:49, Krzysztof Janowicz <janowicz@ucsb.edu> a
écrit :

> Dear all,
>
> I added a wiki pages that shows a concept map for the changes to be made
> on the Actuator and Actuation side of SOSA. The proposed changes address
> some shortcomings of the current model and are also in preparation for a
> deeper axiomatization in SSN.
>
> There are two major (but in no sense dramatic changes) to SOSA, namely a
> proposal to add the SOSA:actuatedProperty role and a class called
> SOSA:ActuableProperty.  These are in line with previous work and
> requests made on this list.
>
> I hope you can look at the concept map and the notes on the wiki page as
> I hope we can get this resolved during our next teleconference. Please
> keep in mind that everything that is not shown in a dashed style is
> already part of SOSA.
>
> https://www.w3.org/2015/spatial/wiki/Actuation_in_SOSA
>
> Best,
> Jano
>
>
>