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

ISSUE-139 RE: Alignment of SSN and SOSA

From: <Simon.Cox@csiro.au>
Date: Mon, 30 Jan 2017 23:28:48 +0000
To: <public-sdw-wg@w3.org>
Message-ID: <2fb8a827cd894a1381bba7e95d5ed96a@exch1-mel.nexus.csiro.au>
I should have tagged this notification with ISSUE-139

From: Simon.Cox@csiro.au [mailto:Simon.Cox@csiro.au]
Sent: Tuesday, 24 January, 2017 16:29
To: public-sdw-wg@w3.org
Subject: [ExternalEmail] Alignment of SSN and SOSA

I just created a little file containing an initial proposed mapping from SSN to SOSA and loaded it to a branch – see


I just followed the alignment shown here: https://www.w3.org/2015/spatial/wiki/Mapping_Table but expressed it more formally so all the alignments are cast as

ssn:XXX rdfs:subClassOf sosa:YYY .
ssn:vvv rdfs:subPropertyOf sosa:uuu .

except for one, which is the other way round because the definition in SOSA seemed to be more restricted than SSN.

sosa:hasValue rdfs:subPropertyOf ssn:hasValue ;

I think this matches the discussion today. I issued a pull-request.

In some cases it may be appropriate to replace rdfs:subClassOf with the stronger owl:equivalentClass.

This relates to ISSUE-37, ISSUE-49, ISSUE-88, ISSUE-102, ISSUE-115, ISSUE-139 .


From: Armin Haller [mailto:armin.haller@anu.edu.au]
Sent: Tuesday, 24 January, 2017 11:46
To: Kerry Taylor <kerry.taylor@anu.edu.au<mailto:kerry.taylor@anu.edu.au>>; janowicz@ucsb.edu<mailto:janowicz@ucsb.edu>; Joshua Lieberman <jlieberman@tumblingwalls.com<mailto:jlieberman@tumblingwalls.com>>
Cc: Rob Atkinson <rob@metalinkage.com.au<mailto:rob@metalinkage.com.au>>; Raúl García Castro <rgarcia@fi.upm.es<mailto:rgarcia@fi.upm.es>>; public-sdw-wg@w3.org<mailto:public-sdw-wg@w3.org>; Cox, Simon (L&W, Clayton) <Simon.Cox@csiro.au<mailto:Simon.Cox@csiro.au>>
Subject: Re: ACTION-251: (ISSUE-88) write up how an ssn:platform and a sosa:platform are essentially the same, with an example (Spatial Data on the Web Working Group)

I can see rapid convergence here in this thread. …
Received on Monday, 30 January 2017 23:30:01 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:31:28 UTC