13:16:19 RRSAgent has joined #wot-discovery 13:16:19 logging to https://www.w3.org/2022/10/10-wot-discovery-irc 13:17:18 meeting: WoT Discovery 14:02:13 chair: McCool 14:02:16 ktoumura has joined #wot-discovery 14:02:17 glomb has joined #wot-discovery 14:02:28 present+ Kaz_Ashimura, Michael_McCool, Kunihiko_Toumura 14:04:33 Mizushima has joined #wot-discovery 14:04:52 JKRhb has joined #wot-discovery 14:04:55 acimmino has joined #wot-discovery 14:05:17 present+ Andrea_Cimmino, Christian_Glomb, Jan_Romann 14:06:15 cris_ has joined #wot-discovery 14:07:26 meeting starts reviewing the minutes 14:07:34 topic: review minutes 14:08:32 -> https://www.w3.org/2022/09/26-wot-discovery-minutes.html Sep-26 14:09:12 i/meeting starts/scribenick: acimmino/ 14:09:29 present+ Cristiano_Aguzzi, Tomoaki_Mizushima 14:10:10 next topic: review PRs 14:10:20 sub-topic: PR #422 14:10:48 -> https://github.com/w3c/wot-discovery/pull/422 PR 422 - Clean up Siemens/Logilab results 14:10:55 s/sub-topic:/subtopic:/ 14:11:24 this PR was merged, it updates the siemens logilab implementation results 14:12:23 +q 14:12:33 mccool: in general cr transition will be difficult to be done with current implementation results, many features are at risk 14:12:59 q+ 14:14:21 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#10_October_2022 14:14:53 mccool: it seems that only one implementation provides SPARQL capabilities. Nevertheless, there should be two. 14:15:13 i|in general|-> https://cdn.statically.io/gh/w3c/wot-discovery/daca95eefcb71a1cddda847eb1a824d3eb099e44/testing/report.html Rendered version of the Draft Implementation Report| 14:16:07 q? 14:16:18 rrsagent, make log public 14:16:22 rrsagent, draft minutes 14:16:22 I have made the request to generate https://www.w3.org/2022/10/10-wot-discovery-minutes.html kaz 14:16:53 mccool: it seems that wothive implementation used ; instead of , for the results and that messes up the table 14:17:02 mccool fixes the file 14:17:06 s/next topic:/topic:/ 14:17:08 rrsagent, draft minutes 14:17:08 I have made the request to generate https://www.w3.org/2022/10/10-wot-discovery-minutes.html kaz 14:17:48 mcool then updated the table, now it seems more of the SPARQL features are covered 14:19:02 the new table is rendered 14:19:26 q? 14:19:38 mccool: upd still has a lot of features uncovered 14:21:03 ack kt 14:21:27 s/mcool /McCool / 14:22:01 ktoumura: could you check the request I made in wot-test ? #443 14:22:37 PR is merged adding the assertions 14:23:29 mccool updates the table with the new implementation report 14:23:36 i|PR is|-> https://github.com/w3c/wot-testing/pull/443 wot-testing PR 443 - Update Implementation Description etc.| 14:26:32 mccool: it seems that no at risk is changed with this new report 14:28:53 cris: there are two problems. One is the fact we do not check the code 404 for the SPARQL 14:29:14 mccool adds the ttd-unsoported-feature to the manual assertion csv 14:29:55 cris: the second is about the anonymous id 14:31:49 mccool: it seems that at the time is been tested no implementation performs this operation 14:32:10 cris: I think farshid's implementation should provide this feature 14:32:21 also, cris implementation should cover this feature 14:32:50 mccool: the spec should be clearer about this 14:33:14 mcool: cris and farshid take over this 14:34:00 mccool: now we have the manual test 14:34:07 s/mcool:/mccool:/ 14:34:32 ...only two implementations are describe as discoverer 14:34:40 ...we may need more 14:35:33 ...I'm concern that node-wot does not implements discoverer 14:35:57 cris: we are currently working on this, probably it will be done in two weeks 14:36:41 mccool: also concern about discoverer-td-identify since all discoverer should implement this 14:36:49 ...seems that hitachi is failing on this one 14:37:11 ....ktoumura is that fixable? 14:39:17 mccool: also first three features at risk are implemented by 0 implementations 14:39:28 this is odd since these describe how to talk to a directory 14:41:12 q? 14:41:15 ack c 14:41:23 q+ JKRhb 14:41:25 ack J 14:42:12 q+ 14:42:36 mccool: these features do not entail automatic following of links, is more providing means to follow things to users 14:43:55 mccool: it seems nobody has implemented thing link 14:44:34 mccool: personally, if this feature is dropped it is fine, but it may bring problems if we do 14:45:08 because a bunch of stuff depends on it, so we should check if dropping this may bring derived problems 14:45:25 or it would be great if we can implement these, which would also solve the problem 14:46:27 ack c 14:46:28 mccool: security boostraping, I'm sure people is implementing these features but it is not filled in the table we should review 14:46:43 mccool: who is doing coap-based service 14:47:05 jan_romann: I'm dealing also with coap 14:47:27 mccool: that's good but we still need another one 14:47:37 cris: I think also node-wot implements it 14:49:21 mccool: similar issues occur with different representations 14:49:55 q+ 14:50:59 another odd assertion is that a successful response should return the correct content-type header 14:51:46 another assertion with 0 implementations is the CoRE 14:52:09 jan_romann: we implement it 14:52:22 mccool: ok, we can make it informative, but it we need two implementations 14:53:26 mccool: ok, these were the technical ones, now let's move to the security one 14:53:49 mccool: we will try to request that for security we will only need one implementation 14:57:04 security bootstraping using HTTP should be easy to provide 14:57:37 q+ cris_ 14:57:44 ack c 14:59:17 mccool: we are out of time, but I do not feel confortable with these results 14:59:45 we should update and improve the results during this one week updating the manual results 15:00:06 but if we have all these at risk we will need to delay the PR 15:00:17 s/we should/... we should/ 15:00:22 s/but if/... but if/ 15:00:28 q+ 15:00:37 rrsagent, draft minutes 15:00:37 I have made the request to generate https://www.w3.org/2022/10/10-wot-discovery-minutes.html kaz 15:01:30 s/because a bunch of/... because a bunch of/ 15:01:38 q+ 15:01:46 https://github.com/mmccool/wot-discovery/blob/oct-2022-testfest-updates/testing/report.html 15:04:53 ack ac 15:04:54 ack cr 15:04:57 ack k 15:05:13 kaz: is that draft report different from the Statically version on the agenda? 15:05:15 https://w3c.github.io/wot-discovery/testing/report.html 15:06:14 mccool: yes, and need to update the Statically version link as well 15:06:17 [adjourned] 15:06:21 rrsagent, draft minutes 15:06:21 I have made the request to generate https://www.w3.org/2022/10/10-wot-discovery-minutes.html kaz 15:07:28 i/is that/scribenick: kaz/ 15:07:28 rrsagent, draft minutes 15:07:28 I have made the request to generate https://www.w3.org/2022/10/10-wot-discovery-minutes.html kaz 15:07:59 s/another assertion/... another assertion/ 15:08:01 rrsagent, draft minutes 15:08:01 I have made the request to generate https://www.w3.org/2022/10/10-wot-discovery-minutes.html kaz 15:08:16 s/or it would be g/... or it would be g/ 15:08:20 rrsagent, draft minutes 15:08:20 I have made the request to generate https://www.w3.org/2022/10/10-wot-discovery-minutes.html kaz 15:09:08 s/another odd/... another odd/ 15:09:10 rrsagent, draft minutes 15:09:10 I have made the request to generate https://www.w3.org/2022/10/10-wot-discovery-minutes.html kaz 15:09:41 s/this is odd sin/... this is odd sin/ 15:09:42 rrsagent, draft minutes 15:09:42 I have made the request to generate https://www.w3.org/2022/10/10-wot-discovery-minutes.html kaz 15:10:42 s/security boo/... security boo/ 15:10:43 rrsagent, draft minutes 15:10:43 I have made the request to generate https://www.w3.org/2022/10/10-wot-discovery-minutes.html kaz