14:00:30 RRSAgent has joined #wot-arch 14:00:30 logging to https://www.w3.org/2021/05/20-wot-arch-irc 14:00:58 meeting: WoT Architecture 14:01:07 present+ Kaz_Ashimura 14:01:13 chair: Lagally 14:02:03 present+ Michael_McCool 14:02:40 McCool has joined #wot-arch 14:03:38 fighting with webex ... 14:05:03 s/fighting with webex ...// 14:09:34 Mizushima has joined #wot-arch 14:10:54 https://www.w3.org/2021/04/29-wot-arch-minutes.html https://www.w3.org/2021/05/06-wot-arch-minutes.html 14:11:06 i/https/topic: Minutes/ 14:11:40 present+ Daniel_Peintner, Michael_Lagally, Tomoaki_Mizushima 14:11:45 present+ Michael_Koster 14:12:03 scribenick: McCool 14:13:41 mm: ml was not available, so we merged mostly editorial PRs, then created a pre-restructure branch so more radical PRs would still have a convenient rollback point 14:15:17 mm: btw, it seems some people are assuming directories will follow the profile but I had not previously considered this to be a requirement. But it MAY may sense... we will have to explicitly discuss in the next call 14:15:27 ml: any objections to publishing the minutes 14:15:34 s/minutes/minutes?/ 14:15:46 ml: hearing no objections, minutes are approved 14:16:08 Action items: 14:18:01 Topic: Discovery PR #588 14:18:36 mm: basically just added a couple of paragraphs that describe the purpose and basic architecture of the Discovery service 14:19:42 mm: notice the strong emphasis on security and privacy 14:21:10 i|basically|-> https://github.com/w3c/wot-architecture/pull/588 wot-architecture PR 588 - Add Discovery refs, dfn, and section| 14:23:41 ml: we should be explicit about what is normative 14:24:10 mm: in particular, it is not required that discovery be done using WoT Discovery, that there is a WoT TDD, or that peer-to-peer is supported 14:24:30 ... so I would suggest merging this but I can add another paragraph in a new PR to make these points explicit 14:25:06 ... probably a "MAY NOT" assertion? Not sure 14:25:24 ryuichi has joined #wot-arch 14:26:12 mm: we probably do want to *encourage* use of WoT discovery, but not require it 14:26:17 Mccool: check the pagination response codes in the discovery spec Ben: double check the list of error codes in WebThings Lagally: check error codes of Oracle's digital twin implementation Daniel: double check node-wot's error codes, are there error response payloads?https://github.com/w3c/wot-architecture/issues/591 14:27:28 topic: carry over requirements to use cases #72 14:27:52 ml: housekeeping, just merge; carried over to use case repo 14:28:02 ... is in the repo, not the document 14:28:04 https://github.com/w3c/wot-profile/pull/72 14:29:20 s/https/-> https/ 14:29:44 mm: should we reschedule the arch call? 14:29:53 s/72/72 wot-profile PR 72 - carry over requirements to use cases TF/ 14:30:00 ml: let's try contacting ben first to see if he has an ongoing problem 14:30:01 present+ Ryuichi_Matsukura 14:30:17 s/ ben / Ben / 14:30:23 Summary of action items Mccool: check the pagination response codes in the discovery spec Ben: double check the list of error codes in WebThings Lagally: check error codes of Oracle's digital twin implementation Daniel: double check node-wot's error codes, are there error response payloads? 14:30:54 [adjourned] 14:30:58 rrsagent, make log public 14:31:03 rrsagent, draft minutes 14:31:03 I have made the request to generate https://www.w3.org/2021/05/20-wot-arch-minutes.html kaz 16:55:02 Zakim has left #wot-arch