W3C home > Mailing lists > Public > public-sdw-wg@w3.org > November 2016

ssn: issue-72 inverse properties in sosa-core

From: Kerry Taylor <kerry.taylor@anu.edu.au>
Date: Tue, 8 Nov 2016 23:41:16 +0000
To: SDW WG Public List <public-sdw-wg@w3.org>, Armin Haller <armin.haller@anu.edu.au>
Message-ID: <PS1PR06MB17402BB1A2E0E81712C0DD75A4A60@PS1PR06MB1740.apcprd06.prod.outlook.com>
https://www.w3.org/2015/spatial/track/issues/72

The issue of inverse property declarations in sosa-core was again vehemently discussed in the meeting today. We got to a point where 2 alternative approaches  were universally considered acceptable if necessary, but not to a point of reaching  a  consensus on which  was preferred.

At the next ssn meeting this will be put to the vote.  The decision to be made is between  either A or B below.

The SOSA-core should often declare properties that are named, and intended to be used as inverses of other declared properties.
In every case where both a property and its intended  inverse is declared in sosa-core:

(A)    The pair is to be related by an owl:InverseOf declaration; or

(B)   The pair are not to be axiomatically  related but documentation is to be used to make the  inverse intention clear

Due to requests at the meeting the question of whether Classes on sosa-core  were to be declared as owl:Class or rdfs:Class was left open as it was suggested that that question was too overloaded with misunderstanding of the consequences, and focusing on  a particular question like inverseOf might set the scene. I guess the idea behind this is that if we think owl:InverseOf is ok to use in sosa-core --- a particular place where OWL reasoning can be used with a useful effect but without insisting that it *must* be used--  then we should also be comfortable with  using owl:Class in sosa-core.


--Kerry
Received on Tuesday, 8 November 2016 23:41:54 UTC

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