10:06:01 RRSAgent has joined #wot-arch 10:06:01 logging to https://www.w3.org/2022/01/13-wot-arch-irc 10:13:16 ryuichi has joined #wot-arch 10:17:09 Mizushima has joined #wot-arch 10:17:56 ktoumura has joined #wot-arch 10:19:59 meeting: WoT Architecture 10:20:18 present+ Kaz_Ashimura, Michael_Lagally, Ege_Korkan, Kunihiko_Toumura, Sebastian_Kaebisch 10:20:55 Ege has joined #wot-arch 10:21:03 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Jan_13th.2C_2022 10:24:10 mlagally__ has joined #wot-arch 10:24:24 chair: Lagally 10:24:35 present+ Tomoaki_Mizushima 10:24:45 scribenick: sebastian 10:24:46 ML: shows the agenda 10:24:53 i/shows/topic: Agenda/ 10:25:12 i|shows|-> https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Jan_13th.2C_2022 agenda for today| 10:28:19 topic: minutes check from last meeting 10:28:35 https://www.w3.org/2021/12/23-wot-arch-minutes.html 10:30:28 present+ Ryuichi_Matsukura 10:35:09 any comments, wishes, objections? 10:35:11 no 10:35:58 approved 10:36:26 topic: new time slots 10:36:55 -> https://doodle.com/poll/ht5q6rbzs7xcbtna?utm_source=poll&utm_medium=link doodle for Architecture 10:36:58 -> https://doodle.com/poll/ce9gh5zkqg6miiya?utm_source=poll&utm_medium=link doodle for Profile 10:37:45 new time slot for Arch call will be every Wednesday 1pm, CET 10:37:53 Main call RESOLUTION: profiles at 7am ET on Wed (one hour before main call) (chairs call will be moved an hour earlier), architecture will use only the second hour of the current slot, so will be at 6am ET on Thursday. 10:38:30 -> https://www.w3.org/2022/01/12-wot-minutes.html#r01 main call resolution 10:39:24 UTC times: Profile call: each Wednesday, Noon 12:00 10:39:52 Architecture: every Thursday, 11am UTC 10:40:52 ML: we can close the doodle polls 10:40:52 topic: Spec Alignment and Publication Blockers 10:41:06 https://github.com/w3c/wot-architecture/issues?q=is%3Aissue+is%3Aopen+label%3A%22spec+alignment%22 10:42:21 ML: uses case document should be reviewed and align terminology 10:42:21 ... also see https://github.com/w3c/wot-architecture/issues/674 10:42:45 q? 10:42:52 q+ Ege 10:43:07 ML: what is the status about the Binding issue? 10:43:12 https://github.com/w3c/wot-architecture/issues/617 10:43:58 i/what is/subtopic: 617/ 10:44:00 s/https/-> https/ 10:44:24 Ege: there are some discussions about the media types 10:44:31 s/617/617 Issue 617 - Review Chapter 8.7 in relation to Binding Templates 4.1/ 10:44:38 ... should be not under the protocol binding section 10:44:50 i/use case document should/subtopic: Issue 674/ 10:45:04 ML: lets move section 8.7.3 to 8.8 10:45:22 Ege: agree 10:45:39 ack e 10:46:02 ML: will create an issue --> https://github.com/w3c/wot-architecture/issues/675 10:48:43 https://w3c.github.io/wot-binding-templates/#form-element 10:48:58 i|agree|-> https://w3c.github.io/wot-architecture/#media-types 8.7.3 Media Types 10:49:13 i|agree|-> https://w3c.github.io/wot-architecture/#sec-wot-servient-architecture-high-level 8.8 WoT System Components and their Interconnectivity| 10:49:27 Ege: Form elements in binding template should be removed or removed from the architecture 10:50:16 Ege: can be moved to the hypermedia section 10:52:26 ML: can you find a good place where to move to? 10:52:45 Ege: I can have a look --> https://github.com/w3c/wot-architecture/issues/675 10:54:33 s/https://github.com/w3c/wot-architecture/issues/675/https://github.com/w3c/wot-architecture/issues/676 10:54:54 s/https://github.com/w3c/wot-architecture/issues/675 /https://github.com/w3c/wot-architecture/issues/676 10:55:50 rrsagent, make log public 10:55:58 rrsagennt, draft minutes 10:57:01 s/rrsagennt, draft minutes// 10:57:05 rrsagent, draft minutes 10:57:05 I have made the request to generate https://www.w3.org/2022/01/13-wot-arch-minutes.html kaz 10:57:45 ML is there additional terminology needed for binding spec? 10:57:45 https://github.com/w3c/wot-architecture/issues/614 10:57:46 s/ML/ML: 10:57:46 ML: we have already content type, should be enough 10:58:46 Ege: Im agree, people know content type very well. MIME Type is old name 10:59:09 i/use cases document should/subtopic: Issue 674/ 10:59:09 ML: close issue https://github.com/w3c/wot-architecture/issues/612 10:59:36 s/subtopic: 617/subtopic: Issue 617/ 10:59:40 rrsagent, draft minutes 10:59:40 I have made the request to generate https://www.w3.org/2022/01/13-wot-arch-minutes.html kaz 11:00:02 s|i/use case document should/subtopic: Issue 674/|| 11:00:04 rrsagent, draft minutes 11:00:04 I have made the request to generate https://www.w3.org/2022/01/13-wot-arch-minutes.html kaz 11:02:42 ML: what is the status about the 'Relationship between "8.7 Protocol Bindings" and "9.5 WoT Binding Templates"' 11:02:48 https://github.com/w3c/wot-architecture/issues/608 11:03:18 new issue provided by Ben in protocol binding repo https://github.com/w3c/wot-binding-templates/issues/143 11:04:23 ML: keep this issue open and revisit again 11:05:02 topic: PR contributions 11:05:15 also see https://github.com/w3c/wot-architecture/pulls 11:05:38 present+ Ben_Francis 11:06:14 q+ 11:06:47 ML: no time to review them all 11:06:48 ... lets do this next week 11:07:56 Sebastian: if there are PRs that was already agreed on in the calls we can directly merge without spending time again in the calls 11:08:37 ack k 11:09:14 s/-->// 11:09:17 rrsagent, draft minutes 11:09:17 I have made the request to generate https://www.w3.org/2022/01/13-wot-arch-minutes.html kaz 11:09:28 ML merges PR https://github.com/w3c/wot-architecture/pull/671 11:09:55 topic: WoT profile 11:10:39 i/PR contribution/kaz: would remind we need to think about the updated schedule on spec alignment, publication blockers and other features/ 11:10:56 ML recaps the requirements that were presented in a slide set 11:10:58 i/PR contribution/ml: let's discuss that later as a separate agenda item/ 11:11:02 rrsagent, draft minutes 11:11:02 I have made the request to generate https://www.w3.org/2022/01/13-wot-arch-minutes.html kaz 11:11:31 s/uses case document/use cases document/ 11:11:46 i/use cases document should/subtopic: Issue 674/ 11:11:48 rrsagent, draft minutes 11:11:48 I have made the request to generate https://www.w3.org/2022/01/13-wot-arch-minutes.html kaz 11:11:57 q? 11:12:02 q+ 11:12:26 ack k 11:12:47 https://github.com/w3c/wot-profile/blob/main/contributions/2021-12-16-WoT-Profiles-discussion%2Brequirements%2BOOTBI.pdf 11:12:59 s/-->// 11:13:02 rrsagent, draft minutes 11:13:02 I have made the request to generate https://www.w3.org/2022/01/13-wot-arch-minutes.html kaz 11:13:16 s/https/-> https/ 11:13:22 s/pdf/pdf Lagally's slides/ 11:14:01 s/lets/let's/ 11:14:06 rrsagent, draft minutes 11:14:06 I have made the request to generate https://www.w3.org/2022/01/13-wot-arch-minutes.html kaz 11:14:34 i/would remind/scribenick: kaz/ 11:14:48 i/also see https/scribenick: sebastian/ 11:14:49 rrsagent, draft minutes 11:14:49 I have made the request to generate https://www.w3.org/2022/01/13-wot-arch-minutes.html kaz 11:15:55 ML: what does it mean oppose? 11:17:25 Ben: it's not saying that other people shouldn't have this requirement. in general, those requirements are more seen as goals. 11:19:39 Ben: we should focus on goals where is a consensus 11:21:36 ... there is also an issue about profile requirements: https://github.com/w3c/wot-profile/issues/156 11:21:58 i|recaps the|subtopic: requirements| 11:22:02 ML: Cristiano's feedback should be updated in the slides as well in the next call 11:22:05 q+ 11:22:29 -> https://github.com/w3c/wot-profile/issues/156 Issue 156 - Profile requirements| 11:22:43 s/requirements|/requirements/ 11:23:40 Ben: in last call you asked people to respond to the issue and you want to split this into lots of erperate issues. What's the purpose? 11:24:29 ML: I want to refine or rework on the requirements 11:24:51 s/erperate/seperate 11:25:30 q? 11:25:33 ack b 11:26:37 ML: lets ask Michael McCool again about the Ambiguities requirement which seems to oppose 11:27:59 s/which/which he 11:30:17 ML updates the MD file about the profile requirements https://github.com/w3c/wot-usecases/blob/main/REQUIREMENTS/profile-requirements.md 11:34:17 ML: we should not exclude any protocols. 11:34:51 q+ 11:35:43 Sebastian: a profile should pre-define a specific protocol or a set protocols. in the second case it should be clear when to use the protocols in which cases. 11:35:59 s/cases/case 11:38:21 Ben: forms can have multiple protocols. Eg., http binding also have WebSocket protocol. 11:41:40 Sebastian: what happen if you have multiple forms with the same protocol like http. You don't know which belongs to the profile implementation. 11:52:31 ML records comments in the https://github.com/w3c/wot-usecases/blob/main/REQUIREMENTS/profile-requirements.md 12:00:58 q? 12:01:02 ack b 12:01:21 q+ to whisper we're at the top of the hour :) 12:03:34 :-) 12:04:29 q- 12:07:22 rrsagent, draft minutes 12:07:22 I have made the request to generate https://www.w3.org/2022/01/13-wot-arch-minutes.html kaz 12:08:02 I need to go 12:09:59 s/I need to go/[adjourned]/ 12:10:00 rrsagent, draft minutes 12:10:00 I have made the request to generate https://www.w3.org/2022/01/13-wot-arch-minutes.html kaz 13:03:27 sebastian has joined #wot-arch 14:08:46 Zakim has left #wot-arch