20:44:26 RRSAgent has joined #sdwssn 20:44:26 logging to http://www.w3.org/2017/02/14-sdwssn-irc 20:44:28 RRSAgent, make logs world 20:44:28 Zakim has joined #sdwssn 20:44:30 Zakim, this will be SDW 20:44:30 ok, trackbot 20:44:31 Meeting: Spatial Data on the Web Working Group Teleconference 20:44:31 Date: 14 February 2017 20:44:44 s/Wworking/SSN Sub/ 20:44:50 s/Working/SSN Sub/ 20:44:58 RRSAgent, make logs public 20:56:20 SimonCox has joined #sdwssn 20:56:41 phila has changed the topic to: https://www.w3.org/2015/spatial/wiki/Meetings:SSN-Telecon20170214 20:56:59 agenda: https://www.w3.org/2015/spatial/wiki/Meetings:SSN-Telecon20170214 20:57:07 chair: Armin 20:57:33 IS webex up yet? 20:57:46 I'll check SimonCox 20:58:14 You shouldn't need me to be here to use the WebEx 20:58:19 But I'm dialling in anyway 20:58:30 Says host has not yet joined the meeting 20:58:41 roba has joined #sdwssn 21:00:50 present+ ahaller2 21:01:47 present+ 21:02:11 present+ SimonCox 21:02:44 present+ 21:03:17 ClausStadler has joined #sdwssn 21:03:30 KJanowic has joined #sdwssn 21:03:39 yes 21:04:11 scribe: roba 21:04:16 i'm eating too but will be finfished soon :-) 21:04:30 DanhLePhuoc has joined #sdwssn 21:04:32 scribenick: roba 21:04:51 mlefranc has joined #sdwssn 21:04:58 kerry_ has joined #sdwssn 21:05:04 present+ kerry 21:05:20 RaulGarciaCastro has joined #sdwssn 21:05:21 present+ mlefranc 21:05:39 present+ DanhLePhuoc 21:05:55 present+ 21:06:05 topic: Patent call https://www.w3.org/2015/spatial/wiki/Patent_Call 21:06:10 present+ RaulGarciaCastro 21:06:49 approve last week's minutes? 21:07:00 -> https://www.w3.org/2017/02/07-sdwssn-minutes Last week's minutes 21:07:04 topic: approve last week's minutes 21:07:08 +1 21:07:16 +1 21:07:17 +1 21:07:20 +1 21:07:21 +1 21:07:22 +1 21:07:28 +1 21:07:41 topic: Alignment of SOSA/SSN with O&M shall denote classes and properties from the ISO 19156 O&M UML model using URIs which are defined in ISO 19150-2, and are currently visible in ontology files available from https://github.com/ISO-TC211/GOM/tree/master/isotc211_GOM_harmonizedOntology/19156/2011 21:07:50 +1 - noting i was in fact present .. 21:08:40 q+ 21:09:34 q+ 21:10:16 q+ to talk URIs 21:10:22 simoncox reiterated the proposal 21:10:23 ack mlefranc 21:10:37 RobA is the scribe! 21:10:43 q- 21:10:51 ack kerry_ 21:11:27 ack phila_car 21:11:27 phila_car, you wanted to talk URIs 21:11:47 kerry_: is this only as ref to the O&M model 21:12:09 q? 21:12:18 PROPOSAL: Alignment of SOSA/SSN with O&M shall denote classes and properties from the ISO 19156 O&M UML model using URIs which are defined in ISO 19150-2, and are currently visible in ontology files available from https://github.com/ISO-TC211/GOM/tree/master/isotc211_GOM_harmonizedOntology/19156/2011 21:12:21 phila: dsicussed with ISO, "good will" regarding intent here, dereferencing mechanics to be taken care of 21:12:31 +1 21:12:32 +1 21:12:34 +1 21:12:37 +1 21:12:37 +1 21:12:39 +1 21:12:41 +1 21:12:42 +1 21:12:57 s/dsicussed/discussed/ 21:13:08 ClausStadler has joined #sdwssn 21:13:30 ahaller2: commit ot git? 21:13:40 s/ot/to 21:13:41 s/ot/to/ 21:13:50 SimonCox: in wiki ready top drop in when appropriate 21:14:01 https://www.w3.org/2015/spatial/wiki/Alignment_to_O%26M 21:14:28 q+ 21:14:33 q+ 21:14:34 present+ ClausStadler 21:14:34 ack KJanowic 21:14:48 RaulGarciaCastro has joined #sdwssn 21:15:34 KJanowic: multiple edits to wiki is hard to track - can we discuss on email and one person edit? 21:15:35 q+ 21:16:43 ack kerry_ 21:16:43 ...specifically when options are being edited, emnail discussion can be made ambiguous 21:17:05 s/emnail/email 21:17:31 fine with me 21:17:49 kerry_: lots of stuff on email - comments fragment and get lost - wiki capture is better - proposes comments wiki page if in-line comments a problem 21:18:01 (I never suggested that) 21:18:13 agree with kerry - wiki style, email is too hard to folloow current state 21:18:28 q? 21:18:48 ack mlefranc 21:19:31 @ahaller 2 do you want to propose a way or do i need to capture those rtecommendations? 21:20:08 +1 21:21:08 roba: then you need to write "RESOLVED:" afterwards 21:21:17 q+ 21:21:17 PROPOSED: That options are not changed in substance on the wiki, and new options provided if needed 21:21:26 +1 21:21:27 +1 21:21:28 +1 21:21:33 +1 21:21:33 +1 21:21:40 +1 21:21:41 q? 21:21:47 ack kerry_ 21:21:54 +1 21:22:00 +1 21:22:13 Raul has joined #sdwssn 21:22:26 q? 21:22:33 kerry_: please link pages in so they can be found 21:22:33 https://www.w3.org/2015/spatial/wiki/Main_Page -> https://www.w3.org/2015/spatial/wiki/Semantic_Sensor_Network_Ontology 21:22:35 topic: SOSA pattern for Observation and Value: remove hasValue, keep class Result as of Option 3 on wiki: https://www.w3.org/2015/spatial/wiki/ 21:23:02 Its linked from here: https://www.w3.org/2015/spatial/wiki/Semantic_Sensor_Network_Ontology 21:23:08 q? 21:23:28 Can you post the link 21:23:38 SOSA pattern for Observation and Value: remove hasValue, keep class Result as of Option 3 on wiki: https://www.w3.org/2015/spatial/wiki/Storing_Observation_Value#Option_3:_SOSA_pattern_for_Observation_and_Value:_remove_hasValue.2C_keep_class_Result https://www.w3.org/2015/spatial/track/issues/90 21:24:00 q? 21:24:07 q+ 21:24:13 ack kerry_ 21:24:13 q+ 21:24:38 q+ 21:25:11 kerry_: the discussion is not complete enough yet - e.g. how oldSSN can be transitioned to model 21:25:24 q+ 21:26:18 q? 21:26:49 ...deprrecating classes without working out how the alignment would work is a "cop-out" 21:27:00 q? 21:27:09 s/deprrecating/deprecating/ 21:27:21 ahller2: so object to voting on this today? 21:27:29 q+ 21:27:45 kerry_: depends on the wording on the proposal 21:27:53 other people would like to speak too 21:28:14 ack KJanowic 21:28:17 ...have mentioned these issues on list 21:29:16 ack mlefranc 21:29:57 KJanowic: option 3 does not allow simple SOSA to refer to the value - would prefer a new(?) option 5 21:30:15 I am fine with option 3 but 5 would allow sosa users to directly publish observation values without having to learn how to do this with the help of other ontologies (which is important for sosa users) 21:30:18 laurent_oz has joined #sdwssn 21:30:30 @roba: it would be option 5 (as is) 21:30:31 q? 21:30:32 mlefranc: preferes to vote today - find some common ground 21:30:32 q+ 21:30:34 ack kerry_ 21:30:51 q+ 21:31:06 q+ 21:31:08 @KJanowic thanks for clarifying 21:31:09 +1 to voting today, we have been putting issues aside for months 21:32:26 I agree with ahaller2 (on results) 21:32:30 q? 21:32:34 ack KJanowic 21:32:44 Today we can vote on selecting one of the options, but we cannot decide on the concrete implementations because they are incomplete 21:32:59 potential PROPOSAL: Actuation + Actuator shall be included in SOSA 21:33:40 q? 21:33:57 ack phila_car 21:34:04 I am proposing that in option 3 we change 'result" back to "observedvalue" 21:34:28 q? 21:34:33 ack SimonCox 21:34:34 I wanted to say it sounds as if there is consensus on moving forward but that Kerry still has concerns 21:34:53 OK, so vote to move forward but invite kerry to come back with specific modifications after the vot 21:34:59 +1 to simon (on keeping result) 21:35:16 q+ 21:35:22 ack KJanowic 21:35:38 q+ 21:35:39 SimonCox: result of actuation or sample not an "ObservationValue" 21:35:57 q+ 21:36:00 q+ 21:36:05 ack kerry_ 21:36:42 kerry_: notes SensorML uses ObservationValue terminology 21:36:46 option 5 is option 3 + a direct way for sosa users to assign values to observations which is very important. We can also change the hasValue name if this is the only problem 21:38:03 q? 21:38:06 q+ 21:38:35 Yes - Kerry does have a point, superclass Result conflates several rather different concepts (including 'Sample' which is the outcome of a sampling activity) 21:39:31 roba: Option 5 has a number of TODOs and question marks. If I do an actuation, I get a result back, which includes the observed value, for example, it is "on now" 21:39:37 q+ 21:39:44 ack roba 21:40:28 ack kj 21:40:58 q? 21:41:09 ack mlefranc 21:41:17 Yes +1 on that 21:41:32 I like this idea! 21:41:33 Kjanowic: have not yet considerd actuation - may needs broadeing as Option 5 21:41:54 q+ 21:42:02 I would be pretty unhappy with option 4 21:42:08 RRSAgent, draft minutes 21:42:08 I have made the request to generate http://www.w3.org/2017/02/14-sdwssn-minutes.html phila_car 21:42:21 an actuation result seems to me more like the return value of a function invocation - if i say: rotate some component by 45 degree, the result may be a pointer (URI) to a sequence of observations being made as the action runs. 21:42:39 ack phila_car 21:42:39 q+ 21:43:27 +1 to having a vote and keep improving! 21:43:41 phila: good conversation about technical details - urges some sort of vote to demonstrate progres - can amend later if needed 21:43:41 +1 21:43:48 +1 21:43:59 ack KJanowic 21:44:00 present+ 21:44:47 IMHO, too general 21:45:06 option 4 is like voting on almost nothing, let's be brave ;-) 21:45:06 PROPOSED: SOSA pattern for Observation and Value: remove hasValue, keep class Result as of Option 3 on wiki: https://www.w3.org/2015/spatial/wiki/Storing_Observation_Value#Option_3:_SOSA_pattern_for_Observation_and_Value:_remove_hasValue.2C_keep_class_Result , pending a modelling decision on isProducedBy, and a decision on how to attach values in SOSA 21:45:07 can me further specialized 21:45:18 +1 21:45:27 +1 21:46:04 q+ (let us keep 'result') 21:46:14 q+ 21:46:27 than do :-) 21:46:43 ack KJanowic 21:46:49 q+ to not claus'es remark 21:46:58 s/not/note/ 21:47:07 +1 21:47:07 PROPOSED: SOSA patter for observation and value: do not vote about "hasValue" yet, keep some class, name it Result for now, nearly as of option 3 in wiki 21:47:11 +1 21:47:14 +0 21:47:29 q+ 21:48:01 ack kerry_ 21:48:01 kerry_, you wanted to not claus'es remark 21:48:04 I would not like this idea, this is like voting on nothing 21:48:46 q+ 21:48:50 it is, for example, a change of state 21:48:51 What is the result of an actuation? See RobA emails on list 21:48:52 kerry_: ref ClausStadler comment - what is an actuation result? Lack of discussion about this 21:49:11 q+ 21:49:14 we are going in circles again 21:49:23 ahaller2_ has joined #sdwssn 21:49:26 Thats why i voted +0 - wasnt 100% sure the model was completely described 21:49:30 q 21:49:32 q 21:49:35 q? 21:49:36 q? 21:49:38 q? 21:50:02 q? 21:50:09 q? 21:50:10 +1 to that 21:50:13 phila: is actuation result just a followon issue? OK to vote, 21:50:13 +1 21:50:32 ok 21:50:36 q- 21:50:37 q+ 21:50:39 +1 to that. We need treatment of consequences now, and then revisit if needed 21:50:50 PROPOSED: SOSA pattern for Observation and Value: remove hasValue, keep class Result as of Option 3 on wiki: https://www.w3.org/2015/spatial/wiki/Storing_Observation_Value#Option_3:_SOSA_pattern_for_Observation_and_Value:_remove_hasValue.2C_keep_class_Result 21:50:53 +1 21:50:53 +1 21:50:57 +1 21:50:58 +1 21:50:58 +1 21:51:00 +1 21:51:03 q- 21:51:04 +1 21:51:09 0 21:51:18 0 21:51:28 q- 21:51:28 action ? 21:51:34 great, can we brielfy talk about the actuation part? 21:51:39 q? 21:51:53 ahller2: agenda next meeting to include followup options and descriptions 21:52:01 topic: Include Actuation, ActuableProperty and Actuator class with associated relations (invokedBy, actuatedProperty) in SOSA as of proposal on wiki: https://www.w3.org/2015/spatial/wiki/Actuation_in_SOSA 21:52:03 q+ 21:52:13 ack KJanowic 21:53:34 KJanowic: describes proposal on wiki. 21:53:38 q+ 21:53:59 q? 21:54:40 ack roba 21:54:44 q+ 21:55:06 Window example: window has a property "open" with boolean value. 21:55:15 (apparently I accidentally deleted all my edits in the wiki. please refresh your browser now) 21:55:16 roba: actuableproperty is promoted to be a special case in this option 21:55:17 we do have observableproperty 21:55:24 Actuation changes the value of this property from "true" to "false" 21:55:40 q+ 21:55:45 q? 21:55:54 no it has these axioms 21:55:56 Note also distinction between ActuableProperty and actuatedProperty - nice! 21:56:33 q+ 21:56:41 We worked on this topic at the time of the XG, check this post on the mailing list: https://lists.w3.org/Archives/Public/public-xg-ssn/2010Feb/0002.html (please have a look) 21:56:59 I will add the axioms and options 21:57:08 we can discuss this next week 21:57:30 q? 21:57:31 ... and I will work up Sampling equivalent 21:57:44 @ahaller2_ I will add the code and options for next week's discussion 21:57:47 ack kerry 21:58:30 KJanowic: confirms q from roba that its just the diagram incomplete - not representing the full proposed model here, 21:59:07 kerry_: seems reasonable - can we apply Use Cases to this pattern now to make sure we understand it 21:59:36 will do so 21:59:56 ack mlefranc 22:00:03 q- 22:00:25 In the WoT group they are defining as interaction patterns Properties and Actions (also events but these are not fix yet (https://w3c.github.io/wot/current-practices/wot-practices.html#interaction-patterns) 22:00:53 [I cannot hear maxime] 22:01:20 I like the idea that actuation and actuator is in sosa 22:01:39 q+ 22:02:07 mlefranc: reservations about names, but would like to vote to accept concept of actuation in SOSA 22:02:19 q- 22:02:31 I will 22:02:52 q? 22:03:11 ahller2: asks for wiki to be updated with options to vote on next week 22:03:15 I like the idea that we just mimic the observation/sensor/sensing for actuation/acutator/actuating, and limit the number of new terms 22:03:18 Bye 22:03:19 thanks for the productive telco today 22:03:22 bye bye 22:03:23 thans 22:03:27 bye all 22:03:43 Bye! 22:04:16 rrsagent, make logs public 22:04:23 rrsagent, draft minutes 22:04:23 I have made the request to generate http://www.w3.org/2017/02/14-sdwssn-minutes.html kerry_ 22:04:27 RRSAgent, make logs public 22:04:31 bye! 22:04:34 RRSAgent, draft minutes 22:04:34 I have made the request to generate http://www.w3.org/2017/02/14-sdwssn-minutes.html ahaller2_