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

Re: ACTION-206: Check whether we can include ontology alignments and fragments without proper implementation evidence in rec trac document but marked as non-normative (Spatial Data on the Web Working Group)

From: Phil Archer <phila@w3.org>
Date: Mon, 10 Oct 2016 10:24:41 +0100
To: SDW WG Public List <public-sdw-wg@w3.org>, Scott Simmons <ssimmons@opengeospatial.org>
Message-ID: <095c1cc9-cdda-e95c-cd61-86c40b54213a@w3.org>
 From a W3C perspective, yes you can.

The rules are:
- if it's normative, you need to show evidence of implementation;
- implementation evidence is not required for non-normative sections of 
the doc, including extensions and alignments.

A reasonable expectation might be that across multiple implementations, 
all terms defined normatively were used multiple times. Individual 
implementations may then be the only example of use of non-normative 
terms and alignments. That then shows that the core is stable and well 
implemented, as well as being the useful basis for specific usage 
scenarios. In this case, saying "here's how you can align SSN with X" 
would be fine.

I leave it to Scott to comment on any delta between this and the OGC 
position.

HTH

Phil.

On 10/10/2016 03:54, Spatial Data on the Web Working Group Issue Tracker 
wrote:
> ACTION-206: Check whether we can include ontology alignments and fragments without proper implementation evidence  in rec trac document but marked as non-normative (Spatial Data on the Web Working Group)
>
> http://www.w3.org/2015/spatial/track/actions/206
>
> On: Phil Archer
> Due: 2016-10-12
> Product: Semantic Sensor Network Ontology
>
> If you do not want to be notified on new action items for this group, please update your settings at:
> http://www.w3.org/2015/spatial/track/users/36841#settings
>

-- 


Phil Archer
W3C Data Activity Lead
http://www.w3.org/2013/data/

http://philarcher.org
+44 (0)7887 767755
@philarcher1
Received on Monday, 10 October 2016 09:24:41 UTC

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