20:58:50 RRSAgent has joined #sdwssn 20:58:50 logging to http://www.w3.org/2016/07/12-sdwssn-irc 20:58:52 RRSAgent, make logs world 20:58:52 Zakim has joined #sdwssn 20:58:54 Zakim, this will be SDW 20:58:54 ok, trackbot 20:58:55 Meeting: Spatial Data on the Web Working Group Teleconference 20:58:55 Date: 12 July 2016 20:58:56 present+ kerry 20:59:02 chair: kerry 20:59:27 present+ KJanowic 20:59:46 SimonCox has joined #sdwssn 21:00:05 rrsagent, make logs public 21:00:23 present+ SimonCox 21:00:36 roba has joined #sdwssn 21:01:00 present+ DanhLePhuoc 21:02:05 RaulGarciaCastro has joined #sdwssn 21:02:06 present+ roba 21:02:14 present+ RaulGarciaCastro 21:03:04 present+ scottsimmons 21:03:58 I can scribe 21:04:17 :-) 21:04:23 scribe: KJanowic 21:04:37 scribenick: KJanowic 21:04:59 topic: patent call https://www.w3.org/2015/spatial/wiki/Patent_Call 21:06:20 kerry: Discussion of how much change we can/should do compared to OWL:Time 21:06:42 q+ 21:06:58 kerry: Dont delete but deprecate 21:07:13 Simon: we are fine as long as we use a new namespace 21:07:37 kerry: Agreed, but this is also about respecting the current user base 21:07:41 s/dont/don't 21:08:20 Q+ 21:08:33 Try to avoid removing parts of the ontology (axioms) 21:08:35 q+ 21:08:40 q? 21:08:44 ack ahaller2 21:09:16 q- 21:09:28 ack ahaller 21:09:32 ahaller2: we use a new namespace so we should be fine. The core will be significantly different but one of the other layers would be very similar to the existing SSN. 21:10:03 q+ 21:10:12 Kerry: fair enough. We have more flexibility than OWL:Time 21:10:47 q? 21:10:53 ack KJanowic 21:11:03 q- 21:11:28 +1 for not adding deprecated classes in the core 21:11:40 +1 21:11:51 Sure, I know this 21:12:25 q+ 21:12:30 q? 21:12:51 kerry: Agreed but we need to take it back to the group and be respectful of existing users 21:12:56 q? 21:13:05 ack SimonCox 21:13:35 Simon: I am pretty sure that this only applies for a previously published namespace. 21:14:13 Simon: protecting users is done via not making changes to the existing namespace. 21:14:46 q? 21:14:46 kerry: lets wait for Phil and move on in the agenda 21:15:02 q? 21:15:08 topic: SSN Requirements from UCR 21:15:39 kerry: This is purely a reminder to have a look at UCR and that we are all happy with the current content. 21:15:57 topic: ISSUE-20 Reference external vocabularies 21:16:14 issue-20? 21:16:14 issue-20 -- Reference external vocabularies -- open 21:16:14 http://www.w3.org/2015/spatial/track/issues/20 21:16:53 ? 21:16:54 q+ 21:16:55 q? 21:17:03 q+ 21:17:06 ack KJanowic 21:17:49 kjanowic: isn't this about nomenclature? If so, we should deal with it 21:18:45 q? 21:19:01 ack roba 21:19:16 KJanowic: so this is also about typecasting between class and entity based classifications, right? 21:19:35 Rob: We also need to look into units of measure 21:20:03 [My daughter just woke up, can somebody please scribe for 2min?] 21:20:31 ack KJanowic 21:20:47 q? 21:21:30 roba: no the issue does not need to stay as it will be picked up by broader best practice environment although it is relevant 21:21:46 ....whther uom should be part of ssn for example? 21:21:55 q? 21:22:22 i'll scribe 21:22:24 q? 21:22:53 action: frans to close issue-20 please 21:22:53 Created ACTION-184 - Close issue-20 please [on Frans Knibbe - due 2016-07-19]. 21:23:05 ...pointed out that its a general BP - but a Use Case and consideration of UoM as a challenge is SSN space 21:23:09 topic: ISSUE-24 clarification of lightweight APIs requirement 21:23:20 s/whther/whether 21:23:23 ...kerry - consensus is then the close issue 21:23:26 issue-24? 21:23:26 issue-24 -- clarification of lightweight APIs requirement -- open 21:23:26 http://www.w3.org/2015/spatial/track/issues/24 21:23:51 q+ 21:23:59 ack raul 21:24:16 ack ahaller2 21:24:25 raul - infrastructure requirement not onotology req. 21:24:46 q? 21:24:51 q+ 21:25:01 armin - agree its infrastructure but points out that lightweight core will support lightweigt APIs 21:25:10 q? 21:25:23 kerry - UCR closing - need concrete proposal 21:25:23 [I am back, sorry] 21:25:26 ack ahaller2 21:25:35 ahaller- 21:25:42 ack ahaller 21:25:48 ack ahaller 21:26:04 ack DanhLePhuoc 21:26:24 Danh - more general problem? 21:26:27 q? 21:26:34 Kerry - change to an example 21:27:14 q? 21:27:28 q+ 21:27:44 ack roba 21:28:02 q? 21:28:35 q? 21:28:42 q+ 21:28:53 ack DanhLePhuoc 21:29:35 Danh: Rephrase this requirement to the lightweight profile of the ontology wrt IoT. 21:29:47 +1 21:30:01 roba: req reads like it is intended to ensure SSN is relevant to the IoT space - but we would need the IoT req stated 21:30:02 +1 21:30:39 +1 21:30:42 +1 21:30:43 +1 21:30:54 Proposal: Ask Franz to rephrase 21:30:55 +1 21:32:23 action: frans to rephrase issue-24 requirement to something like "develop lightweight profile of the ontology for IoT" 21:32:24 Created ACTION-185 - Rephrase issue-24 requirement to something like "develop lightweight profile of the ontology for iot" [on Frans Knibbe - due 2016-07-19]. 21:32:36 Sounds good to me 21:32:46 q? 21:32:59 ack roba 21:33:00 whether this is about profiles or not is another story that we can discuss at a later time 21:33:38 Simom: Develop an example how the ontology can be used. The SOSA Core is not a profile. 21:34:06 Kerry: Show how the ontology can be used for lightweight IOT needs. 21:34:07 maybe "require a lightweight way to exchange data according to the SSN ontology" 21:34:13 see above 21:34:33 "in the IoT context" 21:34:46 q? 21:35:10 final version: Show how the SSN ontology can be applied in the context of lightweight IoT needs 21:35:11 Okay> 21:35:16 Okay? 21:35:24 q? 21:35:25 APIs are always about exchange 21:35:37 +1 21:35:39 +1 21:35:40 +1 21:35:42 +1 21:36:27 action: frans to fix issue-24 by replacing requirment to "Show how the SSN ontology can be applied in the context of lightweight IoT needs" 21:36:28 Created ACTION-186 - Fix issue-24 by replacing requirment to "show how the ssn ontology can be applied in the context of lightweight iot needs" [on Frans Knibbe - due 2016-07-19]. 21:36:35 q? 21:37:03 q? 21:37:10 q+ 21:37:47 topic: Suggested changes to ontology editing process/tooling 21:38:03 ack ahaller 21:38:16 Ahaller2: We moved the ontology away from Webprotege for may reasons, one of them being issues with the namespace. This makes it pretty unusable for our work. Proposal was to use github. 21:38:28 q? 21:39:28 Ahaller2: Most people will edit the file directly. 21:39:38 q+ 21:39:43 q? 21:40:06 q- 21:40:10 q? 21:40:33 We can usue whatever we want as long as we are carful with our github pull requests and the way we handle the raw file 21:40:46 topic: SOSA/SANDA? 21:40:50 I find TopBraid generates a very consistent serialization. It just isn't the same as Protege ... 21:41:01 q+ 21:41:12 ack KJanowic 21:42:10 See: https://github.com/w3c/sdw/blob/kjanowicz-ssn/ssn/rdf/sosa.ttl 21:42:17 q+ 21:42:19 KJanowic: - didnt get that sorry.. 21:42:25 ack ahaller2 21:42:27 Kerry: asks for summary 21:42:37 ack ahaller 21:43:21 Ahaller2: What we did was taking kjanowic work, add the actuator class and then change the name and so forth. 21:43:42 q+ 21:44:36 ahaller starting the discussion on process and procedure 21:44:42 ack KJanowic 21:44:54 Armin + Simon worked on SANDA - http://webprotege.stanford.edu/#Edit:projectId=32a4ea9e-4d06-4f92-8188-07fcd96f81a7 21:45:11 Simon and Jano worked on https://www.w3.org/2015/spatial/wiki/SOSA_Ontology 21:46:43 Re Procedure - shoudl be " ... responsible for generating an observation result or another change in the world" 21:46:54 +1 on distinguishing the instruments and the procedure. This was definitely my intention in the first proposal of the core 21:46:57 q+ 21:47:01 q+ 21:47:02 +1 21:47:20 s/shoudl/should 21:47:31 q? 21:47:35 ack SimonCox 21:48:02 ahaller2, great. But if you look at samplingprocedure and procedure now, only sampling procedure is about a procedure. 21:48:17 simon: agreed, there is some confusion that we need to clean up 21:48:35 KJanowic: That was a problem of wrong documentation of the class. 21:48:36 q+ 21:48:46 KJanowic: Webprotege was playing up with us 21:49:11 KJanowic: reintroducing rdf:coments for whatever reason 21:49:13 aheller2: Sure, I just wanted to point this out 21:49:20 s/coments/comments 21:49:36 same for Results being only created by Sensors (I already changed this) 21:50:03 q+ 21:50:18 ack roba 21:51:17 Very important issue 21:51:31 ack KJanowic 21:53:00 q? 21:53:08 +1 to KJanowic, the procedure is measuring the temperature of soil or air, depending on how you use the SensingDevice 21:53:26 +1 to KJanowic 21:53:42 +1 21:53:47 ObservingProcedure is subclass of Procedure and superclass of Sensor? 21:54:26 SimonCox: we called it Sensing, didn't we 21:54:26 Procedure is also superclass of ActuatingProcedure and SamplingProcedure 21:54:28 ?? 21:54:59 Simon: IMHO, the procedure is like to cookbook recipe. It is not a superclass of sensor. 21:54:59 Yes - Sensing/Actuating/Sampling better names 21:55:18 Then yes 21:55:27 Agree - is recipe, not device 21:55:31 Uses a device 21:55:38 It is a bridge to workflows 21:55:51 Agree 21:56:24 Kerry: sorry, yes I will 21:56:53 yes, so if the procedure is a sequence of actions (like in a receipt) and not a device, than we should change the description 21:57:06 Rob: There needs to be a method to identify a procedure as well as to describe it 21:57:31 q+ 21:57:32 +1 to change the description. I think we all are on the same page 21:57:45 great. 21:58:00 We are also talking about the subtle differences between sensing and a procedure 21:58:30 Rob: Just needs to be clear to the usage 21:58:46 q+ 21:59:03 ack KJanowic 21:59:20 krz: there are instruments, that might be a specific sensor that 21:59:32 ...carries an observation, a sensing is always tking place.. 21:59:52 ...but an observation procedure is more of a'to take a measurement do these steps" 22:00:03 ...this is a procedure that makes sure [missed] 22:00:17 ...want to be as inclusive as we can e,g instruments and human sensors 22:00:18 SensingDevice is an Instrument 22:00:37 We need to be careful with the Sensor class, this is why we renamed it to Sensing, because Sensor sounds like a device 22:00:44 .... want to distinguish describing a procedure from [missed] 22:00:47 works for me - needs to be front anb centre of description 22:00:52 q? 22:00:58 If this is okay with everybody, I can do the change in SOSA (this is all just about the comment, there is no axiom anyway :-)) 22:01:25 armin: need to be careful with sensor class which sounds like an instrument 22:01:27 ahaller2: lets be careful with sensor class as it sounds like an instrument. sensing is the super class 22:01:29 q+ 22:01:31 q+ 22:01:41 ahaller2: we should use sensing 22:01:50 ... but sensing is a superclass..., sensor could be confused with sensing device 22:01:53 q? 22:02:25 Danh: Completely different question: What about the way we are coding, i.e., RDF versus OWL. 22:02:39 q+ 22:02:40 ack KJanowic 22:02:55 ack DanhLePhuoc 22:03:14 Sensing would not be the Instrument 22:03:20 agree 22:03:27 krz: sensing implies an action, we need to discuss how to call this on the email list -- the procedure and the thing that executes it is doffernt 22:03:32 SensingDevice is the Instrument 22:03:39 Human could be the Instrument 22:03:51 In short: there is the procedure and the XYZ that carries out this procedure to generate a valid observation 22:04:04 yes 22:04:04 rrsagent, draft miutes 22:04:04 I'm logging. I don't understand 'draft miutes', kerry. Try /msg RRSAgent help 22:04:12 The question is how we call XYZ so that it includes sensors, simulations, humans,... 22:04:24 kerry closing the meeting 22:04:27 XYZ could be Sensor, but not sure about the name 22:04:39 ObservingProcedure? 22:04:46 EstimatingProcedure? 22:04:47 rrsagent, draft minutes 22:04:47 I have made the request to generate http://www.w3.org/2016/07/12-sdwssn-minutes.html kerry 22:04:58 bye, let's continue on the list 22:05:01 bye bye 22:05:40 KJanowic has left #sdwssn 22:10:49 ahaller2 has joined #sdwssn 23:11:06 ahaller2 has joined #sdwssn