See also: IRC log
<kerry> scribe: sefki
<kerry> scribeNick: SefkiKolozali_UniS
<KJanowic> @ahaller2: ok, the ontology is now in gh-pages (assuming this is our 'master')
<ahaller2> @KJanowic: thanks!
<ClausStadler> +0 (was on holidays)
<KJanowic> +1
<RaulGarciaCastro> +1
<kerry> +1
<ahaller2> I was present, but it does not show up
<ScottSimmons> +0 (not in call)
<roba> +1
RESOLUTION: approve minutes http://www.w3.org/2016/07/12-sdwssn-minutes
<kerry> topic : patent call https://www.w3.org/2015/spatial/wiki/Patent_Call
<kerry> https://www.w3.org/2015/spatial/wiki/Proposals_for_rewriting_SSN#Design_constraints
Krzysztof: we don't need to duplicate every single term in the process of namespace processing,
<roba> can we handle this by publishing an alignement module to http://purl.oclc.org/NET/ssnx/ssn: ? such a module can reference SOSA core and necessary extensions and be under governance of the orginal SSN team...
<ahaller2> +1 to KJanowic to first design the new ontology and then when finished look at alignment
<SimonCox> +1 KJanowic
<kerry> +1 to roba comment
<KJanowic> +1 ahaller2
Armin: once we have a stable core, we could start to align to the core ssn and to other modules.
<kerry> my point is that every change we make needs to be justified and approved
<SimonCox> +1 KJanowic
<KJanowic> kerry, I absolutely agree that the existing user base needs to be supported
<SimonCox> q_
<KJanowic> yes
Simon: he is not sure whether or not citations to the ssn paper indicate the use of the ontology.
kerry: she cannot provide a proof for that, but she received lots of e-mails from users.
<kerry> +1 agreed!
<KJanowic> +1 ahaller2
<KJanowic> Also, all, please keep in mind that this is about the axiom level and thus deprecation is a difficult task
armin: we have to use the same name, but the core is a completely different use case.
<SimonCox> Alignment with OGC is also a requirement
<SimonCox> +1 KJanowic
<ahaller2> +1 KJanowic, we cannot deprecate in the core, otherwise the purpose of the core is undermined!
<KJanowic> Agreed.
<KJanowic> IMHO, we see rapid convergence around SOSA and would propose to put our energy there and leave the discussion we are having now for a later time period.
<KJanowic> SimonCox, yes this is also an OGC group
<ahaller2> +1 KJanowic, I think we are largely in agreement and should move on
<KJanowic> Agreed
<ahaller2> +1 KJanowic, 30-40% of pages use schema.org at the moment, we need to be in this market
<KJanowic> Same feeling here as ahaller2
Armin: it is pretty much completely aligned to the ssn ontology.
<KJanowic> This is the current version: https://github.com/w3c/sdw/blob/gh-pages/ssn/rdf/sosa.ttl
<kerry> https://www.w3.org/2015/spatial/wiki/Proposals_for_rewriting_SSN
http://iot.ee.surrey.ac.uk/citypulse/ontologies/sao/sao
<KJanowic> I am not sure how this relates to our discussion about the axiomatization of the SSN, can you give us a bit context about this?
http://iot.ee.surrey.ac.uk/citypulse/ontologies/sao/saopy.html
<ahaller2> +1 to Stream Annotation Ontology presented by SefkiKolozali_UniS. Definitely to be looked at for one of the outer cores. I don't think we need to distinguish between streams and discrete sensing in the core, though
<KJanowic> So this is an use case example of the current SSN?
<roba> this is potentially a "horizontal" - scope extension of the "core modules" - do we mean a single module as core or the modularised set of concepts in scope?
<kerry> jano: should be an extension to ssn and not in eithe the core nor the ssn namespace or it will be impossibel to mangage
+q
<KJanowic> Sefki: looks interesting to me but mostly as one of the many, very important cases that use or import or rework SSN but we should not take use cases and make them part of the standard
<KJanowic> IMHO, a standard has to be a subset of user requirements, not a super set.
I believe that sao:point and sao:segment are fairly crucial to ingerate into the ssn or to use on iot devices as it allows one to represent data streams in temporal features when we conduct time series analysis
<kerry> issue: should sao"point and sao:segment be inside the core for time series analysis
<trackbot> Created ISSUE-71 - Should sao"point and sao:segment be inside the core for time series analysis. Please complete additional details at <http://www.w3.org/2015/spatial/track/issues/71/edit>.
<kerry> q/
<kerry> q/
<SimonCox> https://www.w3.org/2015/spatial/wiki/SOSA_Ontology
<SimonCox> https://github.com/w3c/sdw/tree/gh-pages/ssn/rdf
<KJanowic> The current code is here: https://github.com/w3c/sdw/blob/gh-pages/ssn/rdf/sosa.ttl
<KJanowic> Thanks kerry
<KJanowic> bye bye
<ahaller2> thanks
<RaulGarciaCastro> bye!
<RaulGarciaCastro> Thanks!
<kerry> rrsagent: draft minutes
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: sefki Found ScribeNick: SefkiKolozali_UniS Present: KJanowic kerry ScottSimmons SimonCox SefkiKolozali_UniS ClausStadler ahaller2 RaulGarciaCastro roba JRamsay Found Date: 26 Jul 2016 Guessing minutes URL: http://www.w3.org/2016/07/26-sdwssn-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]