13:59:53 RRSAgent has joined #wot-arch 13:59:53 logging to https://www.w3.org/2021/05/27-wot-arch-irc 14:00:01 meeting: Wot Architecture 14:00:06 present+ Kaz_Ashimura 14:03:55 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#May_27th.2C_2021 14:04:02 present+ Michael_Lagally 14:04:46 McCool has joined #wot-arch 14:05:05 present+ Michael_McCool 14:06:24 Mizushima has joined #wot-arch 14:09:33 scribenick: kaz 14:09:59 topic: Agenda 14:10:06 ml: goes through the agenda 14:10:21 -> https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#May_27th.2C_2021 Agenda 14:10:49 topic: Minutes 14:11:00 -> https://www.w3.org/2021/05/20-wot-arch-minutes.html May-20 14:11:10 ml: (goes through the minutes) 14:11:24 s/goes through the agenda/(goes through the agenda)/ 14:11:32 present+ Tomoaki_Mizushima 14:12:57 kaz, you are breaking up 14:15:20 (Kaz fixed the style of Lagally's mentioned three actions (McCool, Ben and Daniel)) 14:18:09 present+ Sebastian_Kaebisch 14:19:22 (minutes approved) 14:19:55 topic: PR 588 14:20:15 -> https://github.com/w3c/wot-architecture/pull/588 PR 588 - Add Discovery refs, dfn, and section 14:20:59 mm: need clear use cases 14:21:20 ... if we have strong need, we can do it 14:23:15 ... depending on fixed UR, etc. 14:23:22 ... need clarification 14:23:55 ... need to probably talk with the Eclipse Volto guys as well 14:24:27 ... the problem is that we are now holding reorganizing discussion 14:25:05 ml: we can extend the feature later 14:25:45 ... Sebastian, would you assume Thing Directory to store Thing Model? 14:25:51 sk: it's possible 14:25:58 mm: yeah, it's technically possible 14:26:22 ... Thing Model is also a JSON-based file 14:27:04 -> https://pr-preview.s3.amazonaws.com/w3c/wot-architecture/588/cdb883d...mmccool:31bf57b.html#discovery "8.4 Discovery" within the diff 14:27:12 ml: (goes through the diff) 14:28:18 mm: the 2-phase approach should be not part of the architecture but rather part of the concept 14:28:58 ... note that it's hard to change for embedded cases 14:29:33 ... we should not broadcast the detail of the device information 14:29:53 ml: ok 14:30:00 ... the language here looks fine to me 14:30:19 ... just wondering about this reference to "SOLID" 14:30:36 ... what does this link specifically help our spec? 14:30:50 mm: it's part of the W3C activity (as a CG) 14:31:02 ... related to managing access control 14:31:16 ... where does the security key come from? 14:31:27 ... how to manage the key? 14:31:37 ... SOLID provide insight for that 14:32:08 ... even the WoT security need another best practice documentation 14:32:21 ... also informative 14:32:41 ... WoT security guideline itself is also informative 14:32:58 ... make sense to include the links to those documents 14:33:10 ... should show what the best practices are 14:33:44 ml: reference to the CG report by the Solid CG 14:34:06 -> https://solidproject.org/TR/ Solid Technical Reports 14:34:43 q+ 14:35:46 (The "Solid Technical Reports" is a list of documents related to the Solid project.) 14:36:33 kaz: think we should consult with PLH and Ralph about how to deal with these resources 14:36:56 ml: ok 14:38:12 ... McCool, could you generate yet another PR to cite the actual Editor's Draft documents for Solid resources? 14:38:15 mm: will do 14:39:07 ml: any other comments? 14:39:09 (none) 14:39:44 ml: so would suggest we merge this PR itself, and McCool will create another PR for the detail 14:40:49 kaz: note that we should talk with PLH and Ralph about how to cite the information before our CR transition :) 14:41:24 topic: WoT Profile 14:42:10 https://pr-preview.s3.amazonaws.com/benfrancis/wot-profile/pull/77.html#actions 14:42:23 s/Profile/Profile PR 77/ 14:42:53 i|https|-> https://github.com/w3c/wot-profile/pull/77 PR 77 - New Protocol Binding section| 14:43:04 ml: checked the Oracle's error codes as well 14:44:25 mm: there was error code definition within TD spec as well 14:44:32 https://docs.oracle.com/en/cloud/paas/iot-cloud/iotrq/StatusCodes.html 14:44:33 ml: need to check it 14:44:40 s/https/-> https/ 14:44:54 s/html/html Oracle Cloud's error code/ 14:45:25 mm: we need a short summary of the error range as well 14:45:52 ... e.g., 20X, 40X, ... 14:46:27 ... list of the error codes 14:46:51 summary: 200-202, 204, 400-401, 403-406, 408-409, 415, 500, 503 14:47:14 mm: range of the error codes above 14:47:27 ml: ok 14:48:00 mm: we could allow 402 for a profile 14:48:10 ... additional code to be added 14:48:30 ml: would like to point out a couple of possible additional ones 14:49:10 ... (refers to RFC7231) 14:49:16 -> https://datatracker.ietf.org/doc/html/rfc7231 RFC7231 14:50:07 ml: e.g., 408 timeout errors 14:50:25 ... 414 URI Too Long 14:50:53 mm: we made payload maximum limit 14:51:05 ... profile is about limitation for consumer 14:51:25 ml: there are a couple of server errors as well (on RFC7231) 14:51:42 ... e.g., 504 Gateway Timeout 14:52:50 ... let's come back to "413 Payload Too Large"