09:58:59 RRSAgent has joined #wot-arch 09:58:59 logging to https://www.w3.org/2022/05/05-wot-arch-irc 09:59:06 meeting: WoT Architecture 09:59:10 chair: Lagally 10:01:35 presented+ Kaz_Ashimura, Michael_Lagally, Michael_McCool 10:03:09 mlagally has joined #wot-arch 10:03:33 ktoumura has joined #wot-arch 10:04:09 present+ Kunihiko_Toumura 10:04:32 McCool has joined #wot-arch 10:05:40 topic: minutes 10:06:23 ml: minutes for April 28 10:06:31 i|April|-> https://www.w3.org/2022/04/28-wot-arch-minutes.html Apr-28| 10:06:58 ... some info on security discussed prior to the meeting, should be move it or delete it? 10:07:10 ... move under issue 726 for context 10:07:32 s/be move/we move/ 10:08:06 i/minutes for/scribenick: McCool/ 10:08:30 ml: approve? 10:08:39 ... no objections, publish 10:08:46 topic: Contributions 10:08:55 subtopic: PR #742 10:09:18 ml: explainer updates, remove editor notes 10:09:29 ... add some links to profile and discovery 10:09:30 q? 10:09:56 ... replaced list of use cases with a table 10:10:10 ... removed requirements section, covered in use cases document 10:10:19 ... then have design discussion 10:10:26 ... still missing a discovery section 10:10:28 i|explainer up|-> https://github.com/w3c/wot-architecture/pull/742 PR 742 - explainer updates for profile, use cases, cleanup| 10:11:25 mm: let's merge, I can do a cleanup pass, add the discovery para 10:12:42 ml: merging 10:13:02 mm: btw name is long, it makes the URL awkward, percent-encoded spaces, etc 10:13:11 ml: ok, pls change in your cleanup PR 10:15:52 ml: I will do a small PR first to clean up some minor things 10:16:15 mm: ok, let me merge that before 10:16:24 subtopic: PR #739 10:16:28 ml: accessibility 10:17:04 Ege has joined #wot-arch 10:17:14 i|access|-> https://github.com/w3c/wot-architecture/pull/739 PR 739 - Answers to accessibility questions| 10:17:20 present+ Ege_Korkan 10:21:27 mm: tricky, because WoT systems can have UIs but we don't constrain them 10:21:59 q+ 10:22:57 kaz: also want to note got some comments from Janina, how to deal with existing IoT frameworks like Alexa, etc. 10:23:12 ... how to use WoT to deal with accessibility for users 10:23:55 ack k 10:24:54 mm: basically what I say in summary is that there can be accessibility impact, but adding such constraints was not in scope, but might be in the future 10:27:27 ktoumura has joined #wot-arch 10:28:17 q+ 10:29:11 q+ 10:29:46 ml: maybe some of these "no" answers should be "possible" 10:30:14 kaz: we haven't really seriously thought about how to incorporate UI constraints, but perhaps we should 10:30:38 ... right after last F2F meeting, Michael Cooper presented, mentioned some possible extensions 10:31:17 mm: also languages choices are themselves a kind of accessibility 10:31:49 ege: displays, a stretch, we could think of an accessibility vocabulary, have some constraints, standardized affordances, etc. 10:33:46 mm: note also these answers are for WoT as a whole, not just for TDs 10:34:49 ml: consider as a thought experiment CORBA, same answers? 10:35:03 ack k 10:35:04 ack e 10:38:31 mm: can also update the intro a bit; some things we might be able to deal with layered on top of the current architecture 10:39:11 ml: one place a "yes" could be added 10:41:52 mm: anyway, let me address the review comments, update the PR, have you check it, merge it, then mark the a*y issue as ready to review 10:49:17 mm: for internationalization, still need to do that for architecture 10:50:08 ... can look at what has already been done for TD and discovery 10:50:21 mm: I may be able to get to that next week 10:50:23 q? 10:50:24 q? 10:50:55 subtopic: PR #737 10:51:02 ml: binding related information 10:51:48 ... this PR is carrying over an annex from the binding docs, correct? 10:51:59 ege: yes, we agreed to move this to architecture 10:52:32 i|binding related in|-> https://github.com/w3c/wot-architecture/pull/737 PR 737 - Align binding related information| 10:52:34 ... currently these are in the "orphaned sections", appendix B1 10:53:34 mm: why in architecture vs. TD 10:54:43 ... concern is that it may mention things not defined in architecture, hence confusing, e.g. "op", "form", etc. 10:55:10 ml: let's see what we have already... 10:56:15 ... do have a section that defines forms and operation types in general terms 10:57:17 q+ 10:57:59 ... so maybe we need to do a bit of repair to avoid things like "readproperty" that have not been explicitly defined yet 10:58:39 ege: not that a lot of these chapters were written before the TD was finalized 10:59:26 ... also worth considering whether they should be included at all 11:00:04 ml: this PR does resolve two or three issues, but there are also some assertions 11:00:25 ... it also removes some existing assertions, new ones don't correllate 11:01:45 mm: what issues get fixed? PR combines fixes to both 11:01:46 Mizushima has joined #wot-arch 11:02:27 ege: also the assertions that were removed were ones we agreed to remove 11:02:48 ml: would be good to reference the issue where we agreed to remove issues 11:03:23 ml: please split also into fixes to separate issues; see comments on issue 11:03:54 kaz: +1 11:04:52 ege: is list from Toumura-san that we had agreed to remove... 11:05:02 ml: thought we *had* removed that... 11:05:07 https://w3c.github.io/wot-architecture/#sec-hypermedia-links 11:05:19 https://w3c.github.io/wot-architecture/#sec-hypermedia-forms 11:06:06 toumura: agree with ege that we remove the bnf assertions 11:06:26 ml: yes, we all agreed, we just need to keep the bookkeeping straight 11:06:43 ... much easier if there are multiple small PRs than one big one 11:07:37 kaz: should have a PR for each issue 11:08:40 [adjourned] 11:08:55 rrsagent, make log public 11:09:05 present+ Tomoaki_Mizushima 11:09:09 rrsagent, draft minutes 11:09:09 I have made the request to generate https://www.w3.org/2022/05/05-wot-arch-minutes.html kaz 12:02:27 zkis has joined #wot-arch 14:15:46 Zakim has left #wot-arch