ISSUE-139: the sdw charter asks us to standardise ssn and to make it modular

strategy to connect sosa to ssn

the sdw charter asks us to standardise ssn and to make it modular

State:
CLOSED
Product:
Semantic Sensor Network Ontology
Raised by:
Kerry Taylor
Opened on:
2017-01-11
Description:
Quote from charter
"The WG will work with the members of the former Semantic Sensor Network Incubator Group to develop its ontology into a formal Recommendation, noting the work to split the ontology into smaller sections to offer simplified access."


SOSA as it curently stands is completely disconnected from SSN. It includes
(a) terms that are also used in ssn but that have different meanings (both descriptively, formally and in application). e.g. sosa:Platform (issue-88),
sosa:Sensor (issue-93)
(b) terms for which there are very similar or identical SSN equivalents but different names e.g. sosa:resultTime ssn:observationResultTime
(c) terms that have no correspondence in SSN e.g. sosa:Sample

SOSA is not a simplified module of the most well-used (or most useful) parts of ssn which it should be. It is an independent (albeit simple) ontology. It has no formal nor semi-formal relationship to ssn -- being generous one could say perhaps that it is "inspired" by ssn. It has also lost connections to sensorML that are embodied in ssn.

There is no interoperability strategy nor tools, other than a weak human-readable(only) mapping table (currently WIP) that identifies some of the similar terms from each.

This fails to deliver on our charter. It only serves to confuse all our potential users.

There have been promises of an alignment ontology -- that could be helpful. But it would be very messy as sosa and ssn are currently defined. There was once an intention to import sosa into ssn -- that would be huge damage to ssn in the current state of sosa, importing a load of irrelevant and contradictory stuff for the sake of 3-5 useful terms? OTOH If sosa was instead a "core" of ssn this could be made to work well.

Please note that this is not an issue about those specific examples named here, as there are plenty more examples for each of these. It is an issue about a
strategy to connect sosa to ssn and to deliver on our charter.

Maybe this is just a re-statement of old and still outstanding issue-48, issue-49 and issue-37 in the light of further development since then.

Related Actions Items:
Related emails:
  1. Re: Remaining Options for SOSA-SSN Integration, Was: SOSA/SSN integration architecture (from rob@metalinkage.com.au on 2017-03-21)
  2. RE: Remaining Options for SOSA-SSN Integration, Was: SOSA/SSN integration architecture (from kerry.taylor@anu.edu.au on 2017-03-21)
  3. RE: Remaining Options for SOSA-SSN Integration, Was: SOSA/SSN integration architecture (from Simon.Cox@csiro.au on 2017-03-21)
  4. Re: Remaining Options for SOSA-SSN Integration, Was: SOSA/SSN integration architecture (from rob@metalinkage.com.au on 2017-03-21)
  5. Re: Remaining Options for SOSA-SSN Integration, Was: SOSA/SSN integration architecture (from rob@metalinkage.com.au on 2017-03-21)
  6. Re: Remaining Options for SOSA-SSN Integration, Was: SOSA/SSN integration architecture (from rob@metalinkage.com.au on 2017-03-21)
  7. Re: Remaining Options for SOSA-SSN Integration, Was: SOSA/SSN integration architecture (from armin.haller@anu.edu.au on 2017-03-21)
  8. Re: Remaining Options for SOSA-SSN Integration, Was: SOSA/SSN integration architecture (from rob@metalinkage.com.au on 2017-03-20)
  9. Remaining Options for SOSA-SSN Integration, Was: SOSA/SSN integration architecture (from maxime.lefrancois@emse.fr on 2017-03-20)
  10. Re: ISSUE-139, ISSUE-146, Methodology ? Was: alignment sosa to ssn (from maxime.lefrancois@emse.fr on 2017-02-13)
  11. Re: ISSUE-139, ISSUE-146, Methodology ? Was: alignment sosa to ssn (from armin.haller@anu.edu.au on 2017-02-12)
  12. Re: alignment sosa to ssn (from janowicz@ucsb.edu on 2017-02-12)
  13. Re: alignment sosa to ssn (from armin.haller@anu.edu.au on 2017-02-12)
  14. RE: ISSUE-139, ISSUE-146, Methodology ? Was: alignment sosa to ssn (from Simon.Cox@csiro.au on 2017-02-12)
  15. FW: alignment sosa to ssn (from Simon.Cox@csiro.au on 2017-02-12)
  16. ISSUE-139, ISSUE-146, Methodology ? Was: alignment sosa to ssn (from maxime.lefrancois@emse.fr on 2017-02-11)
  17. alignment sosa to ssn (from kerry.taylor@anu.edu.au on 2017-02-11)
  18. RE: Different or same Namespace for SOSA/SSN (from Simon.Cox@csiro.au on 2017-02-09)
  19. RE: Different or same Namespace for SOSA/SSN (from kerry.taylor@anu.edu.au on 2017-02-09)
  20. Re: Different or same Namespace for SOSA/SSN (from armin.haller@anu.edu.au on 2017-02-09)
  21. RE: Different or same Namespace for SOSA/SSN (from kerry.taylor@anu.edu.au on 2017-02-09)
  22. Re: Different or same Namespace for SOSA/SSN (from rob@metalinkage.com.au on 2017-02-09)
  23. RE: Different or same Namespace for SOSA/SSN (from Simon.Cox@csiro.au on 2017-02-09)
  24. Re: Different or same Namespace for SOSA/SSN (from janowicz@ucsb.edu on 2017-02-08)
  25. Re: Different or same Namespace for SOSA/SSN (from janowicz@ucsb.edu on 2017-02-08)
  26. Re: Different or same Namespace for SOSA/SSN (from armin.haller@anu.edu.au on 2017-02-08)
  27. RE: Proposals (was Re: Architecture of SOSA/SSN integration) : (from kerry.taylor@anu.edu.au on 2017-02-06)
  28. RE: Point of objection RE: State of SSN: arguments in favour of a single name and namespace, proposal, the SEAS example, proposal of action (from kerry.taylor@anu.edu.au on 2017-02-06)
  29. RE: Point of objection RE: State of SSN: arguments in favour of a single name and namespace, proposal, the SEAS example, proposal of action (from kerry.taylor@anu.edu.au on 2017-02-06)
  30. Re: Point of objection 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)
  31. Re: Point of objection RE: State of SSN: arguments in favour of a single name and namespace, proposal, the SEAS example, proposal of action (from janowicz@ucsb.edu on 2017-02-05)
  32. Re: Point of objection RE: State of SSN: arguments in favour of a single name and namespace, proposal, the SEAS example, proposal of action (from janowicz@ucsb.edu on 2017-02-05)
  33. RE: Point of objection RE: State of SSN: arguments in favour of a single name and namespace, proposal, the SEAS example, proposal of action (from kerry.taylor@anu.edu.au on 2017-02-05)
  34. RE: Point of objection RE: State of SSN: arguments in favour of a single name and namespace, proposal, the SEAS example, proposal of action (from kerry.taylor@anu.edu.au on 2017-02-05)
  35. Re: Point of objection RE: State of SSN: arguments in favour of a single name and namespace, proposal, the SEAS example, proposal of action (from janowicz@ucsb.edu on 2017-02-04)
  36. RE: State of SSN and josh's thoughts re modules and namespaces (from kerry.taylor@anu.edu.au on 2017-02-01)
  37. Re: State of SSN and josh's thoughts re modules and namespaces (from jlieberman@tumblingwalls.com on 2017-02-01)
  38. RE: State of SSN: comment on namespaces and urls (from kerry.taylor@anu.edu.au on 2017-02-01)
  39. RE: State of SSN and josh's thoughts re modules and namespaces (from kerry.taylor@anu.edu.au on 2017-02-01)
  40. Re: State of SSN: comment on namespaces and urls (from armin.haller@anu.edu.au on 2017-02-01)
  41. RE: State of SSN: comment on namespaces and urls (from kerry.taylor@anu.edu.au on 2017-02-01)
  42. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-31)
  43. RE: State of SSN (from kerry.taylor@anu.edu.au on 2017-01-31)
  44. How much sub-classing is actually required for SSN to import SOSA? (from Simon.Cox@csiro.au on 2017-01-31)
  45. Re: State of SSN (from rob@metalinkage.com.au on 2017-01-31)
  46. Re: State of SSN (from armin.haller@anu.edu.au on 2017-01-31)
  47. RE: State of SSN (from kerry.taylor@anu.edu.au on 2017-01-31)
  48. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-30)
  49. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-30)
  50. ISSUE-139 RE: Alignment of SSN and SOSA (from Simon.Cox@csiro.au on 2017-01-30)
  51. Re: State of SSN (from rob@metalinkage.com.au on 2017-01-30)
  52. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-30)
  53. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-30)
  54. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-30)
  55. Re: State of SSN (from jlieberman@tumblingwalls.com on 2017-01-30)
  56. RE: State of SSN (from kerry.taylor@anu.edu.au on 2017-01-30)
  57. RE: State of SSN (from kerry.taylor@anu.edu.au on 2017-01-30)
  58. Re: State of SSN (from armin.haller@anu.edu.au on 2017-01-30)
  59. Re: State of SSN (from rob@metalinkage.com.au on 2017-01-30)
  60. RE: State of SSN and agenda this week. (from kerry.taylor@anu.edu.au on 2017-01-30)
  61. RE: State of SSN (from kerry.taylor@anu.edu.au on 2017-01-30)
  62. Re: State of SSN (from armin.haller@anu.edu.au on 2017-01-30)
  63. Re: State of SSN (from armin.haller@anu.edu.au on 2017-01-30)
  64. RE: State of SSN (from Simon.Cox@csiro.au on 2017-01-30)
  65. Re: State of SSN (from rob@metalinkage.com.au on 2017-01-30)
  66. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-29)
  67. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-29)
  68. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-29)
  69. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-29)
  70. RE: State of SSN (from kerry.taylor@anu.edu.au on 2017-01-29)
  71. Re: State of SSN (from armin.haller@anu.edu.au on 2017-01-27)
  72. Re: State of SSN (from armin.haller@anu.edu.au on 2017-01-26)
  73. Re: State of SSN (from rob@metalinkage.com.au on 2017-01-26)
  74. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-25)
  75. Re: State of SSN (from armin.haller@anu.edu.au on 2017-01-25)
  76. RE: Alignment of SSN and SOSA (completion of ACTION-246 Prepare a graphical representation of the alignment) (from laurent.lefort@abs.gov.au on 2017-01-25)
  77. RE: Alignment of SSN and SOSA (completion of ACTION-246 Prepare a graphical representation of the alignment) (from kerry.taylor@anu.edu.au on 2017-01-25)
  78. ssn and sosa interaction design (from kerry.taylor@anu.edu.au on 2017-01-24)
  79. Re: Alignment of SSN and SOSA (completion of ACTION-246 Prepare a graphical representation of the alignment) (from laurent.lefort@abs.gov.au on 2017-01-24)
  80. Alignment of SSN and SOSA (from Simon.Cox@csiro.au on 2017-01-24)
  81. Re: ssn call this week (point 2: commit workkflow) (from laurent.lefort@abs.gov.au on 2017-01-24)
  82. Re: ssn call this week: what to call sosa issue-84 (from armin.haller@anu.edu.au on 2017-01-23)
  83. Re: ssn call this week: what to call sosa issue-84 (from janowicz@ucsb.edu on 2017-01-22)
  84. RE: ssn call this week: what to call sosa issue-84 (from kerry.taylor@anu.edu.au on 2017-01-17)
  85. Re: ssn call this week: what to call sosa issue-84 (from janowicz@ucsb.edu on 2017-01-16)
  86. Re: ssn call this week (from janowicz@ucsb.edu on 2017-01-16)
  87. ssn call this week (from kerry.taylor@anu.edu.au on 2017-01-16)
  88. ssn: issue-139 strategy to connect sosa to ssn (from kerry.taylor@anu.edu.au on 2017-01-11)

Related notes:

No additional notes.

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 139.html,v 1.1 2018/10/09 10:07:51 carine Exp $