ISSUE-115: Are SSN classes and properties required where they are equivalent to imported SOSA resources?

Are SSN classes and properties required where they are equivalent to imported SOSA resources?

State:

CLOSED

Product:

Semantic Sensor Network Ontology

Raised by:

Simon Cox

Opened on:

2016-12-18

Description:

The proposed modularization shows SSN importing SOSA.
In which case, is it necessary to have classes and properties in the SSN namespace which are strictly equivalent to resources already defined in SOSA?
For example, do we need ssn:Sensor as well as sosa:Sensor?

The SSN ontology will certainly introduce additional axioms relating to SOSA resources, to provide the complete semantics for SSN, but does this require equivalent resources to be defined in the SSN namespace?

Since a new namespace is already being introduced, strict backward compatibility is broken anyway, so could the SOSA classes can be adopted instead, and thus reduce the proliferation of resource declarations.

Related Actions Items:

No related actions

Related emails:

1. RE: Different or same Namespace for SOSA/SSN (from Simon.Cox@csiro.au on 2017-02-09)
2. RE: Different or same Namespace for SOSA/SSN (from kerry.taylor@anu.edu.au on 2017-02-09)
3. Re: Different or same Namespace for SOSA/SSN (from armin.haller@anu.edu.au on 2017-02-09)
4. RE: Different or same Namespace for SOSA/SSN (from kerry.taylor@anu.edu.au on 2017-02-09)
5. Re: Different or same Namespace for SOSA/SSN (from rob@metalinkage.com.au on 2017-02-09)
6. RE: Different or same Namespace for SOSA/SSN (from Simon.Cox@csiro.au on 2017-02-09)
7. Re: Different or same Namespace for SOSA/SSN (from janowicz@ucsb.edu on 2017-02-08)
8. Re: Different or same Namespace for SOSA/SSN (from janowicz@ucsb.edu on 2017-02-08)
9. Re: Different or same Namespace for SOSA/SSN (from armin.haller@anu.edu.au on 2017-02-08)
10. RE: State of SSN and josh's thoughts re modules and namespaces (from kerry.taylor@anu.edu.au on 2017-02-01)
11. Re: State of SSN and josh's thoughts re modules and namespaces (from jlieberman@tumblingwalls.com on 2017-02-01)
12. RE: State of SSN: comment on namespaces and urls (from kerry.taylor@anu.edu.au on 2017-02-01)
13. RE: State of SSN and josh's thoughts re modules and namespaces (from kerry.taylor@anu.edu.au on 2017-02-01)
14. Re: State of SSN: comment on namespaces and urls (from armin.haller@anu.edu.au on 2017-02-01)
15. RE: State of SSN: comment on namespaces and urls (from kerry.taylor@anu.edu.au on 2017-02-01)
16. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-31)
17. RE: State of SSN (from kerry.taylor@anu.edu.au on 2017-01-31)
18. How much sub-classing is actually required for SSN to import SOSA? (from Simon.Cox@csiro.au on 2017-01-31)
19. Re: State of SSN (from rob@metalinkage.com.au on 2017-01-31)
20. Re: State of SSN (from armin.haller@anu.edu.au on 2017-01-31)
21. RE: State of SSN (from kerry.taylor@anu.edu.au on 2017-01-31)
22. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-30)
23. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-30)
24. ISSUE-139 RE: Alignment of SSN and SOSA (from Simon.Cox@csiro.au on 2017-01-30)
25. Re: State of SSN (from rob@metalinkage.com.au on 2017-01-30)
26. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-30)
27. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-30)
28. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-30)
29. Re: State of SSN (from jlieberman@tumblingwalls.com on 2017-01-30)
30. RE: State of SSN (from kerry.taylor@anu.edu.au on 2017-01-30)
31. RE: State of SSN (from kerry.taylor@anu.edu.au on 2017-01-30)
32. Re: State of SSN (from armin.haller@anu.edu.au on 2017-01-30)
33. Re: State of SSN (from rob@metalinkage.com.au on 2017-01-30)
34. RE: State of SSN and agenda this week. (from kerry.taylor@anu.edu.au on 2017-01-30)
35. RE: State of SSN (from kerry.taylor@anu.edu.au on 2017-01-30)
36. Re: State of SSN (from armin.haller@anu.edu.au on 2017-01-30)
37. RE: State of SSN (from Simon.Cox@csiro.au on 2017-01-30)
38. Re: State of SSN (from rob@metalinkage.com.au on 2017-01-30)
39. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-29)
40. Re: State of SSN (from janowicz@ucsb.edu on 2017-01-29)
41. RE: State of SSN (from kerry.taylor@anu.edu.au on 2017-01-29)
42. 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)
43. 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)
44. ssn and sosa interaction design (from kerry.taylor@anu.edu.au on 2017-01-24)
45. 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)
46. Alignment of SSN and SOSA (from Simon.Cox@csiro.au on 2017-01-24)
47. Re: issue-117: Comments on the SOSA and SSN implementations (from rgarcia@fi.upm.es on 2016-12-22)
48. RE: issue-117: Comments on the SOSA and SSN implementations (from Simon.Cox@csiro.au on 2016-12-22)
49. RE: issue-117: Comments on the SOSA and SSN implementations (from kerry.taylor@anu.edu.au on 2016-12-22)
50. Re: issue-117: Comments on the SOSA and SSN implementations (from rgarcia@fi.upm.es on 2016-12-20)
51. SSN - Does new SSN <import> SOSA? (from Simon.Cox@csiro.au on 2016-12-18)

Related notes:

Display change log