Naming of xxxProperty
PLEASE NOTE THAT WE HAVE RESOLVED THIS DURING CALL 21-02-16
Kerry: ActuableProperty is also not English. What is meant here? Perhaps an explanation of the concept would help to choose the term. SEAS uses "Property" which suits me, but I guess we are stuck in a pattern since we have "ObservableProperty elsewhere. SAN uses ImpactedProperty which is certainly better, and that would also suggest actuatedProperty could be 'impacts'. Or, better still (because impacts is too forceful, in general) how about "affects" and "AffectedProperty"
- Maxime: related emails in the list: https://lists.w3.org/Archives/Public/public-sdw-wg/2017Feb/0335.html https://lists.w3.org/Archives/Public/public-sdw-wg/2017Feb/0338.html https://lists.w3.org/Archives/Public/public-sdw-wg/2017Feb/0339.html .
- Maxime: propose: "sosa:ActionableProperty" Kerry: definitely an improvement - Can live with that if follwing the "pattern" is important
- sosa:ActuableProperty and sosa:ObservableProperty
- sosa:ActionableProperty and sosa:ObservableProperty
- sosa:ActuatableProperty and sosa:ObservableProperty --> See UPDATE (02/20/17) --> UPDATE (02/21/17): voted on and accepted.
- just sosa:Property
- Actuator, Action, Actionable Property (from WoT)
- AffectedProperty (or, for "able" form, AffectableProperty)
- (Kerry) This really bothers me -- heading down the direction that some properties are Observable and some others are Affectable which is surely entirely
application dependent? In the the sosa context surely we only care about whether some Property *is* "Observed" or *is* "Affected" which should be defined only by the use in relation to the an "Observation" or "Actuation", but not an intrinsic property of the Property.? There *is* a case for distinction in WoT where device capability is being modelled (as SSN does too), but there seems to be no obvious case in sosa, which seems to be just marking up data that has been observed (or actuated? but what does that mean?). I dunno --- still looking hard for the sosa use case. Is it the WoT use case? Isn't this a fundamental question in this area?
KJ: Kerry, being observable and being actuatable is not disjoint, so I do not see any problem here.