ACTION-246: Prepare a graphical representation of the alignment
Prepare a graphical representation of the alignment
- State:
- pending review
- Person:
- Laurent Lefort
- Due on:
- December 27, 2016
- Created on:
- December 20, 2016
- Associated Issue:
- strategy to connect sosa to ssn
- Related emails:
- 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)
- 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)
- 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)
- Re: [Minutes SSN] 2016-12-20 (from ssimmons@opengeospatial.org on 2016-12-20)
- [Minutes SSN] 2016-12-20 (from phila@w3.org on 2016-12-20)
Related notes:
Supplied two examples of alignments, one with the coupling between SSN and SOSA proposed by Simon Cox and a 2nd one with a stronger coupling (owl:equivalentClass) to illustrate how the tool's more compact representation may be helpful in the context of us figuring out the relationships between SOSA and SSN.
Please, create a new ACTION as required e.g. once the group has agreed on whatever other representations are needed (we will also have to define how we can get this information on GitHub in a way which help us to know which version of the figures I generate corresponds to which version of the ontology or alignment is considered for review/publication ...).
I hope that having all the ontologies drawn together will help us to spot and correct designs flaws such as the ones described by in point 6 of Phil's email: https://lists.w3.org/Archives/Public/public-sdw-wg/2017Jan/0148.html
"please don't have the same property/class names in the two namespaces with different semantics (ssn:Platform and sosa:Platform, for example)"
Display change log.