W3C home > Mailing lists > Public > public-sdw-wg@w3.org > March 2017

Re: Naming the properties between FeatureOfInterest, xxxProperty, {Actuator/Sensor}, {Actuation/Observation}

From: <Simon.Cox@csiro.au>
Date: Wed, 8 Mar 2017 03:48:17 +0000
To: <armin.haller@anu.edu.au>, <maxime.lefrancois@emse.fr>, <public-sdw-wg@w3.org>
Message-ID: <1488944897304.73958@csiro.au>
> There are some naming inconsistencies if you want to follow a specific pattern

Indeed. We might not be able to reconcile everything to be consistent.

In particular,
- in the case of Sensing there is always a feature of interest which carries the observed property, and the result is an estimate of the value of the latter (an information object)
- in the case of Actuation there is likely feature of interest, whose property (or state) is changed, so the result is a different value for the property (might be Boolean)
- in the case of Sampling there is a feature of interest which is sampled, so the result is a sample (a thing, not an information object)

​I strongly suggest that you can't look at only the relationships to properties when considering how to line up the language.
When sensing or actuating or sampling happens there is a 'feature' (i.e. 'thing') involved, which then plays a role.

And remember Emerson's comment about consistency - sometimes foolish.

Simon J D Cox
Research Scientist
Land and Water<http://www.csiro.au/Organisation-Structure/Flagships/Land-and-Water>
CSIRO
E simon.cox@csiro.au T +61 3 9545 2365 M +61 403 302 672
   Physical: Reception Central, Bayview Avenue, Clayton, Vic 3168
   Deliveries: Gate 3, Normanby Road, Clayton, Vic 3168
   Postal: Private Bag 10, Clayton South, Vic 3169
people.csiro.au/C/S/Simon-Cox<http://people.csiro.au/C/S/Simon-Cox>
orcid.org/0000-0002-3884-3420<http://orcid.org/0000-0002-3884-3420>
researchgate.net/profile/Simon_Cox3<https://www.researchgate.net/profile/Simon_Cox3>
________________________________
From: Armin Haller <armin.haller@anu.edu.au>
Sent: Wednesday, 8 March 2017 2:22 PM
To: Maxime Lefrançois; SDW WG Public List
Subject: Re: Naming the properties between FeatureOfInterest, xxxProperty, {Actuator/Sensor}, {Actuation/Observation}

Hi Maxime,

Thanks for providing these illustrations!

I did fall in a trap today in the phone call in voting again on names at the end of the telco that we have already decided upon, i.e. see https://www.w3.org/2015/spatial/track/issues/108 and the illustration below by Kerry (with the implemented solution added in red). I.e. we do have the following relations:

madeObservation(Sensor, Observation)
madeBySensor(Observation, Sensor)
observes(Sensor, ObservableProperty)
isObservedBy(ObservableProperty, Sensor)

There are some naming inconsistencies if you want to follow a specific pattern, but considering the constraints we are living with, i.e. existing SSN relation names and names in the OGC (O&M and SensorML), the below graph shows the minimal changes that are required in SSN and that are already implemented: https://github.com/w3c/sdw/pull/591


Unless there are strong reasons for revisiting these decisions, I would propose to move to the next issue. In particular, as you point out in your proposed solution that has consistent naming, that observes/isObservedBy would have a different “domain” and “range” than in SSN, which is, in my opinion a too high price to pay for a consistent property naming convention.

[cid:image001.png@01D29817.612BDCE0]


From: Maxime Lefrançois <maxime.lefrancois@emse.fr>
Date: Wednesday, 8 March 2017 at 11:18 am
To: SDW WG Public List <public-sdw-wg@w3.org>
Subject: Naming the properties between FeatureOfInterest, xxxProperty, {Actuator/Sensor}, {Actuation/Observation}
Resent-From: <public-sdw-wg@w3.org>
Resent-Date: Wednesday, 8 March 2017 at 11:19 am

Dear all,

As a follow up to today's call, I created a simple figure that shows the old and current links between classes: FeatureOfInterest, xxxProperty, {Actuator/Sensor}, {Actuation/Observation}, as of 2017-03-08,

https://www.w3.org/2015/spatial/wiki/File:20170308-foi-property-object-event.png


I also produced another figure that illustrates an option where:
 1. naming is consistent between the ACT part and the SENSE part
 2. one can guess the name of the link between {Actuator, Actuation, Sensor, Observation} to xxxProperty by simply adding the string "Property" somewhere in the name of the link between  {Actuator, Actuation, Sensor, Observation} to FeatureOfInterest
 3. we rely on present or past to differentiate what is "potential" (i.e., links Actuator or Sensor), versus what is "done" (i.e., links {Actuation, Actuator}).

https://www.w3.org/2015/spatial/wiki/File:20170308-foi-property-object-event-maxime-would-be-happy-with.png


As you will understand, I am not 100% happy with this option neither:
  - it uses "observes" as the name of the link between Sensor and FeatureOfInterest, while in the old SSN the link "observes" was between a Sensor and a Property
  - it would imply that we reconsider the vote at https://www.w3.org/2015/spatial/wiki/Link_between_Actuation_and_Actuator



If anyone has a different proposal for the names, you can create a new option with the same "great style" using the pptx at the following URL:
 https://www.w3.org/2015/spatial/wiki/images/4/40/Foi-property-object-event.pptx



Also, now that we have a figure to evaluate all the links between classes FeatureOfInterest, xxxProperty, {Actuator/Sensor}, {Actuation/Observation}, it's clear to track the current progress of sosa/ssn, and identify the possible naming inconsistencies.

On the other hand, I absolutely don't have a clue on the best way to proceed to choose as a group each one of the names for the links as quickly as possible. If anyone has an idea about this, I'd be pleased to hear it.

Kind regards,
Maxime


image001.png
(image/png attachment: image001.png)

Received on Wednesday, 8 March 2017 03:49:18 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 03:49:18 UTC