12:53:38 RRSAgent has joined #wot-pf 12:53:38 logging to https://www.w3.org/2021/09/30-wot-pf-irc 12:53:56 meeting: WoT Plugfest/Testfest - Day 4 12:57:20 chair: McCool 12:57:25 present+ Kaz_Ashimura 12:57:54 matsuda has joined #wot-pf 12:58:06 present+ Tetsushi_Matsuda 12:59:29 present+ Van_Cu_Pham 13:01:08 ktoumura has joined #wot-pf 13:02:09 present+ Michael_Koster, Kunihiko_Toumura, Michael_McCool, Tomoaki_Mizushima 13:02:14 pham has joined #wot-pf 13:02:19 rrsagent, make log public 13:02:21 rrsagent, draft minutes 13:02:21 I have made the request to generate https://www.w3.org/2021/09/30-wot-pf-minutes.html kaz 13:02:24 McCool has joined #wot-pf 13:02:28 rrsagent, who is on the call? 13:02:28 I'm logging. Sorry, nothing found for 'who is on the call' 13:02:41 Mizushima has joined #wot-pf 13:02:41 zakim, who is on the call? 13:02:41 Present: Kaz_Ashimura, Tetsushi_Matsuda, Van_Cu_Pham, Michael_Koster, Kunihiko_Toumura, Michael_McCool, Tomoaki_Mizushima 13:03:18 present+ Ege_Korkan 13:04:06 mjk has joined #wot-pf 13:04:49 present+ Phiipp_Blum 13:05:05 Agenda: https://www.w3.org/WoT/IG/wiki/PlugFest_WebConf#Agenda_30.09.2021 13:06:12 dape has joined #wot-pf 13:06:27 present+ Daniel_Peintner 13:06:33 scribenick: kaz 13:06:54 topic: Preliminary 13:06:58 mm: no new guests 13:07:04 ... or no logistics updates 13:07:06 topic: PRs 13:07:15 present+ Jan_Romann 13:07:20 subtopic: PR 176 13:07:54 -> https://github.com/w3c/wot-testing/pull/176 fix contentType & type #176 13:09:01 mm: wondering if it's OK to include extra space within the contentType string 13:09:11 kaz: don't think it's correct 13:09:19 mk: don't think so either 13:09:38 mm: merge the PR itself 13:09:40 (merged) 13:09:57 subtopic: any additional PRs? 13:10:11 mm: anybody still planning to provide new PRs? 13:10:27 ... TDs will be stored at the Directory automatically 13:10:39 ... would like to merge any valid PRs 13:11:05 ... tomorrow, we need to use the time to check the status and wrap it up 13:11:48 kaz: what about our remaining PR 165? 13:11:53 mm: would visit issues first 13:11:56 topic: Issues 13:12:15 mm: add label of "plugfest202109" 13:12:23 topic: PRs - revisited 13:12:28 subtopic: PR 165 13:12:48 -> https://github.com/w3c/wot-testing/pull/165 Updates to Intel TDs #165 13:13:14 mm: possible virtual device for geolocation 13:13:23 ... manual geolocation data this time 13:13:58 Ege has joined #wot-pf 13:14:14 ... don't have actual ontology yet 13:14:30 ... need to do that at some point 13:15:07 -> https://github.com/w3c/wot-testing/pull/165#issue-1009704324 goes through the check points on the Issue 165 13:16:08 mm: interesting validation issues 13:16:25 ... for multi language support 13:16:49 ... duplicated English title within the titles entry 13:17:21 ... also about explicit readproperty op in geolocator 13:17:35 ek: one of your form has writeproperty? 13:17:40 mm: yeah 13:17:56 ... the default setting may be confusing 13:18:05 ... getting warning is useful 13:18:08 q? 13:18:41 mm: (briefly shows some of the files changed) 13:18:50 ... would merge the PR 13:18:59 ... any objections? 13:19:09 (merged) 13:20:13 mm: (shows TDs under TD/TDs/Intel/) 13:20:38 -> https://github.com/w3c/wot-testing/blob/main/events/2021.09.Online/TD/TDs/Intel/intel-speak.td.jsonld 13:21:22 mm: what about a dynamic device? 13:21:35 ... (shows TD for a camera) 13:21:40 -> https://github.com/w3c/wot-testing/blob/main/events/2021.09.Online/TD/TDs/Intel/intel-camera.td.jsonld 13:21:53 mm: (and then geolocator) 13:22:11 q+ Ege 13:22:13 ack e 13:22:21 -> https://github.com/w3c/wot-testing/blob/main/events/2021.09.Online/TD/TDs/Intel/intel-geolocator.td.jsonld 13:22:37 mm: not actually reading the property data itself 13:22:43 ... kind of awkward too 13:23:04 ... don't want to give actual URI 13:23:31 (discussion on how to deal with the URI) 13:24:15 currently, the camera TD has [[ "href": "https://portal.mmccool.net:8100/api/location", ]] 13:24:38 mm: guess we need a different pointing mechanism 13:24:49 q+ 13:25:37 mk: also something to tell the format 13:25:55 mm: idea here is having an ontology for geolocation information 13:26:03 ... that's not a problem 13:26:31 kaz: some kind of alias mechanism? 13:26:38 mm: pointer mechanism 13:26:52 ... to deal with how many hops to go 13:27:03 ack k 13:27:05 q+ 13:27:39 mm: let's think about a vehicle moving 13:27:53 q+ 13:28:13 ... devices are self-describing 13:29:07 kaz: can understand the need for use cases but adding that capability to TD itself would be overkill 13:29:22 ... that's rather a capability for handling mobile network mesh 13:29:28 ... and IoT discovery itself 13:29:30 ack k 13:29:41 ... we can create an Issue for that, though 13:29:43 ack 13:29:48 s/ack// 13:29:49 ack e 13:30:19 ek: similar issue with robot use case as well 13:30:28 ... so this is a bigger issue 13:30:54 q+ 13:31:25 kaz: you can create an Issue with a label of "finding", etc. 13:31:31 I need to leave early today. bye :) 13:31:31 mm: yeah 13:31:39 (Ege leaves) 13:31:51 s/I need to leave early today. bye :)// 13:32:32 mm: (creates a new Issue) 13:32:34 q? 13:33:04 ack k 13:33:20 s/creates a new Issue/add comments to Issue 167/ 13:33:37 rrsagent, make log public 13:33:41 rrsagent, draft minutes 13:33:41 I have made the request to generate https://www.w3.org/2021/09/30-wot-pf-minutes.html kaz 13:34:23 mk: OneDM uses fragment identifier 13:35:05 mm: ok 13:35:15 ... would like to create some more fake devices 13:35:26 ... to handle geolocation queries 13:35:45 -> https://github.com/w3c/wot-testing/issues/167 Project (2021-09 Plugfest): Geolocation #167 13:36:03 -> https://github.com/w3c/wot-testing/issues/167#issuecomment-931328731 new comments 13:37:30 mm: (shows intel-speak.td.jsonld) 13:37:31 -> https://github.com/w3c/wot-testing/blob/main/events/2021.09.Online/TD/TDs/Intel/intel-speak.td.jsonld 13:37:49 mm: what does the "accuracy" mean? 13:38:09 q+ 13:38:25 ... basically the radius of 5m here 13:39:02 kaz: you're thinking about 2D positioning here given just using langitude and latitude 13:39:13 ... but possibly we could care about 3D positioning 13:39:16 mm: yeah 13:39:42 ... looked at the API within mobiles 13:40:23 ack k 13:40:33 ... should talk about the geospatial guys 13:40:40 q+ 13:41:09 kaz: also the DAS WG guys, e.g., Anssi 13:41:12 ack k 13:41:21 mm: yeah 13:41:46 ... maybe we might want to create a dedicated repo for this direction, e.g., wot-geo, like we did for wot-ejs 13:41:57 q? 13:42:08 mk: can assume GPS system? 13:42:21 ... or various possible mechanisms too? 13:42:23 mm: yeah 13:43:13 q+ 13:44:37 kaz: if we assume the geolocation api, we can't tell the method beforehand 13:44:49 ... the device will decide which method to get the best result 13:45:01 ... and we can tell that based on the response from the device 13:45:53 ... so we should think about the response from the device as well because it could include some important information about the method 13:45:56 mm: riht 13:46:02 s/riht/right/ 13:46:49 ... note here (after "position") is "altitude" which specify the 3D position 13:47:05 ... anyway would like to continue discussion with geo guys 13:47:39 @@@ wot-discovery/roposals/geolocation.md 13:47:44 s/rop/prop/ 13:48:26 https://github.com/w3c/wot-discovery/blob/main/proposals/geolocation.md 13:48:45 mm: my idea is making that MD a separate Note 13:49:43 q? 13:49:44 ack k 13:50:15 s|@@@ wot-discovery/proposals/geolocation.md|| 13:50:26 mm: heading would be a simple version of orientation 13:50:31 q+ 13:50:56 kaz: btw, we just have 10 more minutes 13:51:05 ... so let's talk about projects to be checked tomorrow 13:51:09 mm: right 13:51:15 topic: Projects to be checked 13:51:48 -> https://github.com/w3c/wot-testing/issues/174 Interop Testing (2021-09) #174 13:52:04 kt: checked the connectivity with the NHK devices 13:52:27 mm: (adds that to the Issue as a comment) 13:52:48 ... any other things expected by tomorrow? 13:53:12 ... wondering about Philipp's RIoT OS device 13:53:30 jr: some issue with network connection 13:54:00 q? 13:54:04 q- 13:54:18 ... Philipp has created some tutorial, though 13:54:40 q+ 13:55:06 ack k 13:55:24 kaz: thought Philipp was interested in using mobile network instead 13:55:36 ... so we can ask him about that direction as well 13:55:42 jr: can ask him about taht 13:55:45 s/taht/that/ 13:56:13 mm: maybe somebody could help them set up the configuration 13:56:47 ... e.g., TUM or Unibo? 13:57:07 ... would be good test of tutorial instructions too 13:57:52 ... issue noted with node-wot 13:58:09 ... old CoAP library can't handle TD... 13:58:31 ... if use "td+jsonld" as the MIME type 13:58:41 ... works only with "json" 13:59:21 jr: that issue has been fixed in the dev version of node-wot on my side 14:00:06 ... only remaining issue with node-wot fetch 14:01:02 -> https://github.com/w3c/wot-testing/issues/174#issuecomment-931350331 comments 14:01:07 topic: Tomorrow 14:01:20 mm: we'll wrap up the Plugfest tomorrow 14:01:33 ... there is a diagram of devices/apps by Toumura-san 14:02:10 -> https://github.com/w3c/wot-testing/tree/main/events/2021.09.Online network diagram by Toumura-san (at the bottom) 14:02:12 [adjourned] 14:02:21 rrsagent, draft minutes 14:02:21 I have made the request to generate https://www.w3.org/2021/09/30-wot-pf-minutes.html kaz 16:00:39 Zakim has left #wot-pf