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