Divergence between Sensor (Device, agent (including humans), or software (simulation)) and Actuator (device)

[KathiSchleidt]

The definition of Sensor is quite wide, Device, agent (including humans), or software (simulation) involved in or implementing a procedure

When we compare this with Actuator, it is much narrower, just a device that is used by, or implements, an (Actuation) Procedure

Looking at the underlying RDF, there's nothing to back up this difference. Thus, shouldn't we expand the textual definition of Actuator to be parallel with Sensor? Support human actuators?

[alexrobin]

@KathiSchleidt I fully agree with this.

[dr-shorthair]

Yes - there are many inconsistencies and asymmetries in the text.
It'll require a close reading to tease all these out as we go public.

I've added documentation and editorial tags so we can gather them all together.

[dr-shorthair]

@maximelefrancois86 created a related issue #284 with the following comment:

a sosa:System is "a piece of infrastructure that implements a Procedure."
System generalizes the Actuator, Sensor, and Sampler classes.
In its definition, sosa:Sensor covers devices, agents (including humans), or softwares (simulations).
Therefore, agents (including humans), or softwares (simulations) are pieces of infrastructures.
Maybe we should relax the definition of sosa:System to "an entity (such as a piece of infrastructure) that implements a Procedure."

I'll close that and we'll manage it all together here.