ISSUE-90: The rationale is unclear here: the implication of the new term may be too much

sosa-core:Result

The rationale is unclear here: the implication of the new term may be too much

State:

CLOSED

Product:

Semantic Sensor Network Ontology

Raised by:

Kerry Taylor

Opened on:

2016-11-09

Description:

sosa-core:Result as currently described is a big departure from SSN and it is not obvious how an alignment would look. How is it proposed? Why is this a good idea? Is this a bi-product of having no sensing in sosa-core, as the Result annotation suggests (copied below)?

sosa-core:Result seems to combine ssn:SensorOutput and ssn:ObservationValue. Arguably, those two concepts could be collapsed in the main ssn too to match this proposal in sosa-core.

O&M uses two different names for the corresponding idea; both "observation result" in the glossary and simply "result" in the UML.
i.e "observation result:
estimate of the value of a property determined through a known observation procedure"


Also-- the annotation is wrong or misleading:
"The Result of an Observation, Actuation, or Sampling, e.g., the value for an ObservedProperty of some FeatureOfInterest such as 20m for the height of a tree."@en ;"

In sosa-core terms the Result cannot be a "value". Instead the "value" is connected by a sosa-core:hasValue datatype property (which is very similar to ssn's approach too). Or perhaps it is the sosa:hasvalue that is wrong wrt the comment here?

Related Actions Items:

No related actions

Related emails:

1. [Minutes SSN] 2017 02 14 (from phila@w3.org on 2017-02-15)
2. RE: hasResult / Sampling in SOSA & ISSUE-90 (from kerry.taylor@anu.edu.au on 2017-02-14)
3. Re: hasResult / Sampling in SOSA & ISSUE-90 (from maxime.lefrancois@emse.fr on 2017-02-13)
4. Re: hasResult / Sampling in SOSA & ISSUE-90 (from janowicz@ucsb.edu on 2017-02-13)
5. RE: hasResult / Sampling in SOSA & ISSUE-90 (from kerry.taylor@anu.edu.au on 2017-02-13)
6. Re: hasResult / Sampling in SOSA & ISSUE-90 (from armin.haller@anu.edu.au on 2017-02-12)
7. Re: hasResult / Sampling in SOSA & ISSUE-90 (from janowicz@ucsb.edu on 2017-02-12)
8. Re: hasResult / Sampling in SOSA & ISSUE-90 (from rob@metalinkage.com.au on 2017-02-10)
9. Re: hasResult / Sampling in SOSA & ISSUE-90 (from maxime.lefrancois@emse.fr on 2017-02-10)
10. RE: hasResult / Sampling in SOSA & ISSUE-90 (from Simon.Cox@csiro.au on 2017-02-10)
11. Re: hasResult / Sampling in SOSA & ISSUE-90 (from armin.haller@anu.edu.au on 2017-02-10)
12. Re: hasResult / Sampling in SOSA & ISSUE-90 (from janowicz@ucsb.edu on 2017-02-09)
13. Re: hasResult / Sampling in SOSA & ISSUE-90 (from maxime.lefrancois@emse.fr on 2017-02-09)
14. hasResult / Sampling in SOSA & ISSUE-90 (from danh.lephuoc@tu-berlin.de on 2017-02-09)
15. [Minutes SSN] 2017 02 08 (from phila@w3.org on 2017-02-08)
16. Agenda SSN meeting this week (from armin.haller@anu.edu.au on 2017-02-06)
17. Re: State of SSN: arguments in favour of a single name and namespace, proposal, the SEAS example, proposal of action (from armin.haller@anu.edu.au on 2017-02-06)
18. Re: Proposals (was Re: Architecture of SOSA/SSN integration) (from rob@metalinkage.com.au on 2017-02-02)
19. Re: Proposals (was Re: Architecture of SOSA/SSN integration) (from janowicz@ucsb.edu on 2017-02-01)
20. Re: Proposals (was Re: Architecture of SOSA/SSN integration) (from armin.haller@anu.edu.au on 2017-02-01)
21. RE: Agenda SSN meeting this week (from kerry.taylor@anu.edu.au on 2017-01-30)
22. Agenda SSN meeting this week (from armin.haller@anu.edu.au on 2017-01-30)
23. Re: new issues raised for ssn (from rgarcia@fi.upm.es on 2016-12-20)
24. [sdw] ssn meeting this week (from armin.haller@anu.edu.au on 2016-12-05)
25. new issues raised for ssn (from kerry.taylor@anu.edu.au on 2016-11-13)

Related notes:

Display change log