Re: sdw: ssn task for next ssn meeting

Hi Kerry,

I have drawn and uploaded a more detailed representation of the workflow of the SAO Ontology and its connections with the SSN, PROV, and Timeline Ontologies. I have also added an RDF document that depicts the utilisation of the ontology. Please let me know if the example I have put on the web page is confusing, I can easily add different examples.
https://www.w3.org/2015/spatial/wiki/Proposals_for_rewriting_SSN#Proposal_3_made_by_Sefki

I am now going to update the web page of the SAO ontology to upload the up to date version of it.

Kind Regards,

Sefki Kolozali
Research Fellow
Institute for Communication Systems (ICS), home of the 5G Innovation Centre
University of Surrey
Guildford, Surrey, GU2 7XH, United Kingdom
Tel: +44 (0)1483 689490

E-mail: s.kolozali@s<mailto:s.kolozali@qmul.ac.uk>urrey.ac.uk<http://urrey.ac.uk>
http://www.surrey.ac.uk/ics/<http://www.surrey.ac.uk/ccsr/>






On 3 Aug 2016, at 11:57, Kerry Taylor <kerry.taylor@anu.edu.au<mailto:kerry.taylor@anu.edu.au>> wrote:

Thanks Sefki,
No, I don’t think that is the right  place.. Here, that is linked straight from the main page, would be better : https://www.w3.org/2015/spatial/wiki/Proposals_for_rewriting_SSN. Or a new page you create that is anchored from that one.

>. It is not difficult to integrate it into the ssn ontology as another small module since it is not a large ontology.

It might help if you do that, too! If you use the old (ie ssn-xg) version of ssn for that you can’t go too wrong.


Kerry


From: s.kolozali@surrey.ac.uk<mailto:s.kolozali@surrey.ac.uk> [mailto:s.kolozali@surrey.ac.uk]
Sent: Wednesday, 3 August 2016 8:16 PM
To: Kerry Taylor <kerry.taylor@anu.edu.au<mailto:kerry.taylor@anu.edu.au>>; p.barnaghi@surrey.ac.uk<mailto:p.barnaghi@surrey.ac.uk>
Cc: public-sdw-wg@w3.org<mailto:public-sdw-wg@w3.org>
Subject: Re: sdw: ssn task for next ssn meeting



Hi Kerry,

In terms of the integration of the sao ontology, I have discussed it payam and we are happy for the sao ontology to be a module in the ssn ontology or an extension of the ssn ontology. It is not difficult to integrate it into the ssn ontology as another small module since it is not a large ontology. I am flexible with renaming some of the concept names to make it suitable with the rest of the modules. I will add some of the use cases that I have been working on using the sao ontology on the ssn web page. Is this the right page for me to add a few examples?
https://www.w3.org/2015/spatial/wiki/SSN_conceptual_modules


King Regards,

Sefki Kolozali
Research Fellow
Institute for Communication Systems (ICS), home of the 5G Innovation Centre
University of Surrey
Guildford, Surrey, GU2 7XH, United Kingdom
Tel: +44 (0)1483 689490

E-mail: s.kolozali@s<mailto:s.kolozali@qmul.ac.uk>urrey.ac.uk<http://urrey.ac.uk/>
http://www.surrey.ac.uk/ics/<http://www.surrey.ac.uk/ccsr/>





On 26 Jul 2016, at 23:19, Kerry Taylor <kerry.taylor@anu.edu.au<mailto:kerry.taylor@anu.edu.au>> wrote:

To those interested in ssn,

For the next meeting *please: review the current proposal for SOSA
<kerry> topic: SOSA core - procedures vs devices email thread
https://www.w3.org/2015/spatial/wiki/SOSA_Ontology

https://github.com/w3c/sdw/tree/gh-pages/ssn/rdf

The current code is here: https://github.com/w3c/sdw/blob/gh-pages/ssn/rdf/sosa.ttl


• SOSA core - procedures vs devices email thread<https://lists.w3.org/Archives/Public/public-sdw-wg/2016Jul/0156.html> https://lists.w3.org/Archives/Public/public-sdw-wg/2016Jul/0156.html


Sefki – could you please also consider issue-71 Should sao"point and sao:segment be inside the core for time series analysis.? In particular I think we need a case to be made about why in particular these are useful and necessary for on-board implementation in IoT devices. The use cases you have been working with could be what we need.

Furthermore, that same bar of “necessary” should be addressed to every other term in SAO core.

Finally – I’d like to ask (I recall Joel raised this earlier) what *is* the purpose of the core – ie what defines what belongs in the core and what does not? I think this needs to be well articulated to support our decision making and also our case for the user community.
--Kerry