14:03:35 RRSAgent has joined #wot-discovery 14:03:35 logging to https://www.w3.org/2022/05/23-wot-discovery-irc 14:03:46 cris_ has joined #wot-discovery 14:04:24 present+ Kaz_Ashimura, Michael_McCool, Cristiano_Aguzzi, Farshid_Tavakolizadeh, Kunihiko_Toumura 14:04:27 chair: McCool 14:05:02 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#23_May_2022 14:06:29 topic: minutes review 14:06:40 scribenick: cris_ 14:06:54 -> https://www.w3.org/2022/05/16-wot-discovery-minutes.html May-16 14:06:59 mc: notice that the explainer was not ready for review 14:07:50 ... minor typo it should be objections 14:07:54 ... anything else? 14:08:11 ... ok minutes approved 14:08:15 topic: explainer 14:08:30 mc: I have still to check new feedback 14:08:35 ... there was one comment 14:08:47 ... about HTTP only that we'll resolve in a different discussion 14:09:12 ... given the current reviews we only have this issue with HTTP 14:09:32 ... we have a PR that might solve this 14:09:40 ... but let's discuss it later 14:10:12 present+ Tomoaki_Mizushima 14:10:14 farshid: I have still to complete the review of the explainer 14:10:38 cris: me too 14:10:48 mc: ok we'll wait for the next week 14:10:52 topic: PRs 14:11:44 acimmino has joined #wot-discovery 14:11:46 mc: PR 318 and 317 are realated and should be easy to fix 14:11:48 i|I have still|-> https://github.com/w3c/wot-discovery/pull/309 PR 309 - Draft Explainer| 14:11:50 s/fix/merge/ 14:12:04 subtopic: PR 318 14:12:24 mc: there was a duplicate assertion 14:12:44 i|there was|-> https://github.com/w3c/wot-discovery/pull/318 PR 318 - UTF-8 Constraints and Language Negotiation| 14:13:04 ... I did changes on 3-cr index.html but I moved them back to main index.html 14:13:35 farshid: did you fix the duplicate assertion issue? 14:13:50 mc: let's see the preview 14:15:12 JKRhb has joined #wot-discovery 14:15:14 ... things like queries (e.g. sparql queries) might be supported 14:15:45 ... therefore I don't want to touch the accept content type assertion 14:16:28 farshid: ok 14:17:24 mc: should directory support content-language? I don't think so, TD is already multilang 14:18:06 cris: I agree 14:18:44 farshid: there was a little bit of confusion at first 14:19:22 ... but also what about searches? 14:19:30 mc: it is best effort 14:21:43 https://github.com/w3c/wot-discovery/issues/315 14:23:40 cris: have you check 315? 14:24:05 ... I would like to charset parameter add to content-type 14:25:11 s/https/-> https/ 14:25:15 mc: right, suggesting to add it to thing model and text 14:25:27 s|/315|/315 Issue 315 - Return charset parameter in content-type| 14:26:10 farshid: it is related to another issue from Ben 14:26:28 ... he wants to have a less strict constraint about content-type 14:28:03 mc: let's deal with it separately 14:28:15 farshid: I can volunteer 14:31:27 rrsagent, make log publici 14:31:38 s/publici// 14:31:41 rrsagent, make log public 14:31:51 rrsagent, draft minutes 14:31:51 I have made the request to generate https://www.w3.org/2022/05/23-wot-discovery-minutes.html kaz 14:32:48 mc: ok any objections with PR 318 ? 14:32:52 ... ok merged 14:32:59 subtopic: PR 317 14:33:05 mc: I have to resolve some points 14:33:13 subtopic: 313 14:33:23 mc: long discussion 14:33:42 meeting: WoT Discovery 14:33:54 ... I have still to look into all comments 14:34:06 present+ Jan_Romann, Andrea_Cimmino 14:34:08 rrsagent, draft minutes 14:34:08 I have made the request to generate https://www.w3.org/2022/05/23-wot-discovery-minutes.html kaz 14:34:10 farshit: I just want to mention that is not a full solution for security bootstraping 14:34:29 ... is not solving the problem 14:34:55 i|I have to re|-> https://github.com/w3c/wot-discovery/pull/317 PR 317 - Internationalization Questionnaire updates| 14:35:06 cris: is it something that we should ourselves ? 14:35:34 i|long discussion|-> https://github.com/w3c/wot-discovery/pull/313 PR 313 - Security Bootstrapping| 14:35:40 mc: I would like to use existing mechanisms, http has bootstraping features that people already use 14:36:00 farshid: in practice is really useful 14:36:11 mc: I will be using directory services from browser 14:36:55 ... Ben prefers to allow retrival of html rendered document 14:37:04 ... but it is a different topic 14:37:19 ... I tried to summarize on the github discussion 14:38:13 farshid: one comment: providing a TD is different from exposing it 14:38:20 mc: ok, right 14:39:02 farshid: federated directories TDs can be nested in the master directory 14:39:18 ... I would not force to self-describing 14:39:24 mc: it would not a big deal 14:39:44 ... optional features might be problematic 14:40:01 ... any objections to make directories no- self describing 14:42:54 cris: maybe is a wording problem, is not about self describing but about always providing a TD for TDDs 14:43:54 mc: maybe you are right, I agree that a TD can be hosted somewhere else 14:44:42 ... ok if we commit with this, the figure needs to be updated 14:46:57 ... we also need to clarify that any enpoints that return TD must suppor security bootstrapping 14:47:30 farshid: just one thing before continuing 14:47:49 ... I left a comment about oauth 2 14:47:58 ... is not solving really the security bootstrapping 14:49:07 mc: good point 14:49:26 farshid: we can still defer to 1.1 version 14:51:58 farshid: things id is problematic 14:53:39 ... cause we can only support a subset of TD securityDefinitions in bootstrapping 14:53:41 mc: right 14:53:52 ... I'm capturing it on the comment 14:54:13 cris: I also agree with 2 but I would like to see a better explanation about the fact that no sec can be used 14:55:58 mc: do we have a consensu for 2 ? 14:56:40 s/consensu/consensus/ 14:56:46 ... ok 14:57:06 mc: do we agree to leverage on existing mechanisms ? 14:57:23 s/on/on HTTP/ 14:57:37 farshid: if they are good enough yes. 14:58:07 mc: also can we limit discovery to HTTP ? 14:58:26 farshid: I don't think we can, 14:58:38 ... I don't think it is sufficient 14:59:22 ... maybe use cases definition is helpful 14:59:54 mc: UI is one of those 15:00:43 ... public service 15:02:15 ... do we want to add complexity to our spec 15:02:17 present+ Ben_Francis 15:02:28 ... what's your take on this Ben? 15:02:53 ben: I agree if you already have the credential the whole process is not needed 15:03:17 ... however for UI it makes sense cause you can ask the user to input credentials 15:03:30 ... we have a concrete use case 15:04:44 ... "all things are public" scenario is a no go 15:05:22 mc: ok I'll do my best to capture all points, but I also consider dropping it if I am not satisfied 15:05:42 ben: are we sure that www-authenticate is not enough ? 15:06:02 farshid: on browsers it works because there's a man in the loop 15:06:17 ... there are some use cases were it does not work 15:06:38 ben: I agree in that situation 15:06:47 ... but is already out of scope 15:07:06 rrsagent, draft minutes 15:07:06 I have made the request to generate https://www.w3.org/2022/05/23-wot-discovery-minutes.html kaz 15:09:03 mc: we need to do a WD 15:09:06 ... and than updated 15:09:14 s/than/then/ 15:09:30 ... let's do what we can 15:09:39 ... but next week I want to publish a WD 15:10:22 [adjourned] 15:10:25 rrsagent, draft minutes 15:10:25 I have made the request to generate https://www.w3.org/2022/05/23-wot-discovery-minutes.html kaz 16:00:34 JKRhb has joined #wot-discovery 17:10:36 Zakim has left #wot-discovery