Mode in SAREF4EHAW vs States ?
It is unclear the relation between s4ehaw:Mode and saref:State. It could be deleted and saref:State could be used instead.
Activity
added redundancy issue in saref-portal label
For me it is not sure whether Mode and Status are equivalent, or the proposal for the updated implementation, since Mode is related to several properties that I don't know if they apply to Status (hasMode, inCurrentMode, modeName); and Status has some properties that I don't know if they apply to Mode.
If the developers created a new class, they should have a reason.
In any case, it is clear that this is something to analyse in detail for the extension.
definition of modes in SAREF4EHAW states: Each device has modes of operations that model its dynamic characteristic varying during its lifetime, e.g. active, hold, beacon...
To me, it's exactly equivalent to the states of a device.
hasMode and inCurrentMode seem to fill exactly the same purpose. Except inCurrentMode applies to the health device, and hasMode applies to the Device characteristics (of the device)
s4ehaw:modeName could be replaced by rdfs:label,
moved from saref-portal#77 (moved)
changed milestone to %V2.1.1
mentioned in issue #23 (closed)
added to-verify-before-closing label
added 5 - Propose closing label
removed to-verify-before-closing label
subsumed by #15 (closed)
