15:03:45 RRSAgent has joined #wot-discovery 15:03:45 logging to https://www.w3.org/2021/01/18-wot-discovery-irc 15:03:50 Meeting: WoT Discovery 15:03:57 present+ Kaz_Ashimura, Farshid_Tavakolizadeh, Andrea_Cimmino, Kunihiko_Toumura, Christine_Perey 15:04:19 present+ Michael_McCool, Tomoaki_Mizushima 15:05:05 Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#18_January_2021 15:05:59 present+ Christian_Glomb 15:06:07 zakim, who is here? 15:06:07 Present: Kaz_Ashimura, Farshid_Tavakolizadeh, Andrea_Cimmino, Kunihiko_Toumura, Christine_Perey, Michael_McCool, Tomoaki_Mizushima, Christian_Glomb 15:06:09 On IRC I see RRSAgent, Zakim, McCool, cperey, ktoumura, Mizushima, cimmino, FarshidT, zkis, kaz 15:07:15 glomb has joined #wot-discovery 15:10:05 present+ Cristiano_Aguzzi 15:10:15 cris has joined #wot-discovery 15:10:17 scribenick: cris 15:11:40 mc: about implementation report do you need it before PR transition? 15:12:09 kaz: yes, we need for CR 15:12:29 mc: (noting down deadlines in the agenda) 15:13:00 s/for CR/the report for PR but we need to provide the implementation report plan including the assertions for CR./ 15:13:04 s/need/need implementation plan/ 15:13:18 rrsagent, make log public 15:13:22 rrsagent, draft minutes 15:13:22 I have made the request to generate https://www.w3.org/2021/01/18-wot-discovery-minutes.html kaz 15:14:05 https://w3c.github.io/wot-thing-description/testing/report.html 15:14:17 mc: (showing example of an implementation report) 15:14:18 s/https/-> https/ 15:14:46 s/html/html Thing Description implementation report/ 15:15:24 i/about imple/topic: Schedule and publication requirements/ 15:16:18 mc: I have to deal with the fact that need to generate test cases for our assertions 15:16:48 mc: failures are not a big problem as long as we have a least two passing implementations. 15:18:20 mc: some features cannot be test automatically. Manual assertion cover this use-case. Implementers just state that they comply with a particular feature of the specification 15:19:12 farshid: could we maybe script all of this tests? maybe with Github Actions? 15:20:17 mc: you can't always test all the assertion in the specification. However automated testes are useful. We can talk about it. First I'll try to adapt the work done in TD assertion testing. 15:21:02 ... the next plug fest is a good place to start talking about how to improve our testing workflow 15:22:06 mc: last year we prepared a list of failing tests as a implementation plan 15:22:42 farshid: for linksmart thing directory we have already a bunch of unit tests. Also the APIs are covered 15:22:51 topic: quick updates 15:23:15 mc: tomorrow we'll have a meeting with Spatial Data on the Web IG 15:23:41 mc: there's a meeting link in issue 955 of wot repository 15:24:04 Christine: which IRC channel should we use? 15:24:23 mc: I'll propose wot-usecases 15:24:36 Christine: agree 15:24:41 i|tomorrow|-> https://github.com/w3c/wot/issues/955 Issue 955 on the joint meeting about AR use cases| 15:25:36 mc: this meeting is more on AR 15:26:22 ... Christine brought up differences in how geospatial queries are done in AR 15:26:35 ... I hope to discuss about it tomorrow 15:27:30 ... by the way AR = Augmented Reality. Digital objects are overlaid on a real world video 15:28:30 ... about the Geolocation queries I was thinking about a point-radius method. 15:28:44 ... but in AR field of view is more relevant 15:29:48 Christine: It is important to instruct users where is the device. (i.e., device behind you; turn around to interact) 15:31:21 Christine: we use the terms of 6 degree of freedom when we are referring to if the user can look up or down. 15:32:01 ... body area networks have tons use-cases in industrial use-cases 15:32:54 mc: it is the problem of the "semantic" locations (i.e., arm, leg, living room...) 15:33:44 mc: ideally there are two orthogonal problems. Geospatial should work regardless "semantic" locations. 15:35:02 kaz: robotic and Autonomous vehicles are typical use-cases. 15:35:21 s/robotic/robotics/ 15:37:31 mc: I'll catch more input tomorrow and I report them in a PR or document. 15:37:47 mc: any other issues to discuss? 15:37:55 q? 15:38:06 farshid: there're some comments 15:38:34 rrsagent, draft minutes 15:38:34 I have made the request to generate https://www.w3.org/2021/01/18-wot-discovery-minutes.html kaz 15:38:43 mc: issue #54 15:38:43 Chair: McCool 15:38:45 rrsagent, draft minutes 15:38:45 I have made the request to generate https://www.w3.org/2021/01/18-wot-discovery-minutes.html kaz 15:39:23 mc: terms for TD should go to the Thing Description document 15:39:33 q+ 15:39:57 farshid: should we had to the TD context 15:40:07 ... or another context? 15:40:15 mc: it should be another context 15:40:20 cris: I agree 15:40:30 s/quick updates/Joint meeting on AR use cases/ 15:41:10 mc: (capturing the statement in a comment) 15:41:32 i|issue #54|topic: Issue 54| 15:41:42 i|issue #54|-> https://github.com/w3c/wot-discovery/issues/54 Issue 54| 15:42:13 mc: we can close combo scheme issue 15:43:49 mc: I am currently working other PRs for security. I worked also for alternateResposes. 15:44:12 mc: about #43, how to identify a directory from a TD? 15:44:41 -> https://github.com/w3c/wot-discovery/issues/43 Issue 43 15:44:59 ... we could check a context file used 15:45:16 ... but it is a bit implicit. it is better to use the type keyword 15:45:29 ... we could use both. 15:46:11 ... but it doesn't stop others to use our terms for their goals 15:46:30 ... I prefer to move the type to the core TD vocabulary. 15:49:35 cris: my point is that we need the context file anyway 15:49:49 mc: probably is best to talk with TD task force 15:50:01 rrsagent, draft minutes 15:50:01 I have made the request to generate https://www.w3.org/2021/01/18-wot-discovery-minutes.html kaz 15:50:07 mc: I'll cross reference the isse there 15:50:54 farshid: remember that we need a type for links. 15:51:04 mc: is there an issue about this topic? 15:51:20 farshid: yes it is. 15:52:10 -> https://github.com/w3c/wot-discovery/issues/54 Issue 54 15:53:25 q+ 15:53:30 ack cris 15:54:02 mc: any more issues to be linked in the issue? 15:54:22 farshid: yeah the full list is already in the first issue 15:54:38 -> https://github.com/w3c/wot-thing-description/issues/1033 TD Issue 1033 15:55:36 kaz: we have to record Christine as a guest 15:56:15 @@@ move that part to the top of the minutes 15:56:57 mc: we have a PR from Christine. However, she hasn't the permission to contribute 15:57:42 mc: We'll ping sebastian to propose her as an Invited expert 15:58:32 farshid: #109 just a minor edit 15:58:46 mc: it is fine, merged 15:59:23 i/we have a PR/topic: PR 110| 15:59:38 i|we have a PR|-> https://github.com/w3c/wot-discovery/pull/110 PR 110| 15:59:52 i|#109|topic: PR 109| 16:00:11 mc: #107 needs more discussion 16:00:35 i|#109|-> https://github.com/w3c/wot-discovery/pull/109 PR 109| 16:00:44 i|#107|topic: PR 107| 16:00:52 i|#107|-> https://github.com/w3c/wot-discovery/pull/107 PR 107| 16:00:55 [adjourned] 16:01:01 rrsagent, draft minutes 16:01:01 I have made the request to generate https://www.w3.org/2021/01/18-wot-discovery-minutes.html kaz 17:31:14 zkis has joined #wot-discovery 18:29:06 Zakim has left #wot-discovery