14:05:30 RRSAgent has joined #wot-arch 14:05:30 logging to https://www.w3.org/2021/04/15-wot-arch-irc 14:05:43 Meeting: WoT Architecture 14:05:57 present+ Kaz_Ashimura, Michael_McCool, Michael_Lagally 14:11:30 Mizushima__ has joined #wot-arch 14:14:31 present+ Michael_Koster 14:15:59 sebastian has joined #wot-arch 14:16:52 mjk has joined #wot-arch 14:18:02 present+ Sebastian_Kaebisch 14:20:06 zakim, pick a scribe 14:20:06 Not knowing who is chairing or who scribed recently, I propose Michael_Koster 14:20:52 My audio is not connecting. I will retry 14:21:17 It wants me to raise my hand... 14:21:24 scribenick: kaz 14:21:33 can you hear us 14:21:45 Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#April_15th.2C_2021 14:22:28 topic: Minutes 14:22:32 -> https://www.w3.org/2021/03/11-wot-arch-minutes.html March-11 14:23:15 -> https://www.w3.org/2021/03/15-25-wot-minutes.html#d3 vF2F Day 3/4 14:23:39 ml: (updates the agenda wiki) 14:23:57 ... starting with the March 11 minutes 14:24:41 scribenick: mjk 14:25:20 ml: minutes approved to publish 14:26:53 -> https://www.w3.org/2021/03/15-25-wot-minutes.html#d3 vF2F Day 3/4 14:27:14 i|11-wot|subtopic: March 11| 14:27:28 i|15-25|subtopic: vF2F minutes| 14:28:32 mm: will refactor the terminology document soon 14:28:54 ml: any other concerns besides the one typo? 14:29:45 mm: Philippe Coval name seems mis-spelled 14:30:49 mm: what is Philippe's role? is it listed correctly as a guest? 14:32:03 mm: make sure he is listed for the day in which he made the comments 14:33:20 (added Coval and fixed typos) 14:34:41 ml: any objections to approving? 14:34:45 ... approved 14:35:03 rrsagent, make log public 14:35:09 rrsagent, draft minutes 14:35:09 I have made the request to generate https://www.w3.org/2021/04/15-wot-arch-minutes.html kaz 14:35:48 ml: reviewing the profile goals and scope issue discussion 14:36:30 ml: let's keep the discussion focused and avoid CoAP, MQTT< etc. 14:36:53 mm: agree, let's meet the needs for webthings as a priority 14:37:40 ml: is there any issue with the proposal around http, JSON, and default protocol binding 14:38:22 seb: this looks good for a http/JSON baseline and template for creating future profiles 14:38:59 ... we should adopt only what really makes sense based on the experience we have 14:39:21 ... we need to discuss websockets 14:39:39 rrsagent, draft minutes 14:39:39 I have made the request to generate https://www.w3.org/2021/04/15-wot-arch-minutes.html kaz 14:39:57 mm: websockets is not yet developed in our group 14:40:11 ... no really good agreed solution 14:40:36 ... let's focus on the non-controversial points 14:40:43 i|reviewing the profile|topic: Issue 73| 14:41:07 seb: maybe the items listed in brackets are considered optional 14:41:26 i|reviewing the profile|-> https://github.com/w3c/wot-profile/issues/73 wot-profile Issue 73 - Refine Goals and Scope| 14:41:40 mm: we could leave events open to implementation 14:42:01 rrsagent, draft minutes 14:42:01 I have made the request to generate https://www.w3.org/2021/04/15-wot-arch-minutes.html kaz 14:42:38 mm: http could use long polling for observe 14:43:03 ... OK if the profile leaves some things open 14:43:45 ml: read, write property and invoke action only 14:43:58 ... bare minimum 14:44:36 ml: is there any more input from the plugfest? 14:45:19 zkis has joined #wot-arch 14:45:25 mm: there was activity around TM conversion and discovery, not as much about device to device 14:45:55 ... June plugfest focused on higher level questions also 14:46:07 -> https://doodle.com/poll/mzv9x5rxsdmub5u3 doodle for the next testfest 14:46:13 s/focused/will be focused 14:46:46 mm: to test the profile we will need a test plan and two implementations 14:47:13 mm: to reduce riske we can keep it simple 14:47:20 s/riske/risks 14:47:41 mm: can replicate the current assertion mechanism for discovery and profile 14:48:01 mm: we should break out the architecture assertions separately 14:48:18 ... each spec should have its own plan, report, assertions... 14:49:05 ml: what's the process for marking up for the assertions? 14:49:14 mm: look at the TD one for examples 14:50:31 mjk_ has joined #wot-arch 14:50:48 mm: tables have some particular patterns 14:51:29 (mjk switched to mjk_ due to irc disconnect/reconnect) 14:52:26 mm: wait to see what comes from webthings 14:52:47 rrsagent, draft minutes 14:52:47 I have made the request to generate https://www.w3.org/2021/04/15-wot-arch-minutes.html kaz 14:53:35 (the irc server or connection seems to be restarting) 14:53:49 i/tables have/scribenick: mjk_/ 14:53:50 rrsagent, draft minutes 14:53:50 I have made the request to generate https://www.w3.org/2021/04/15-wot-arch-minutes.html kaz 14:57:05 mm: the implementation report is generated as a snapshot 14:57:38 ... what are the architecture assertions? 14:57:40 present+ Tomoaki_Mizushima 14:57:51 ... terminology is normative 14:58:21 rrsagent, draft minutes 14:58:21 I have made the request to generate https://www.w3.org/2021/04/15-wot-arch-minutes.html kaz 14:59:06 ml: issue #74 can be linked to the issues #75 and #76 14:59:33 i|is there any more input|topic: Implementations and test| 14:59:50 mm: the tooling needs to be set up 15:00:13 ... once set up, the tooling can identify assertions by the span markup 15:00:45 McCool has joined #wot-arch 15:00:46 mlagally has joined #wot-arch 15:01:42 -> https://github.com/w3c/wot-profile/issues/74 wot-profile Issue 74 - Highlighting assertions 15:02:07 -> https://github.com/w3c/wot-profile/issues/75 wot-profile Issue 75 - Implementation Report 15:02:38 -> https://github.com/w3c/wot-profile/issues/76 wot-profile Issue 76 - Markup of normative requirements (RFC 2119) 15:03:04 ->https://github.com/w3c/wot-architecture/issues/589 wot-architecture Issue 589 - Implementation report 15:03:10 mm: it's OK to publish a small and simple profile spec to start with 15:04:38 ml: we need to see what is in the webthings proposal 15:05:58 mm: the outline looks acceptable 15:06:33 mm: any objections? 15:07:05 seb: there are more topics to discuss, so we can leave this as is for now 15:07:25 i|it's OK to|topic: Profile| 15:07:54 i|it's OK to|-> https://github.com/w3c/wot-profile/issues/73 wot-profile Issue 73 - Refine Goals and Scope| 15:08:32 ml: we need to define action and error behavior 15:10:38 zkis has joined #wot-arch 15:10:58 rrsagent, draft minutes 15:10:58 I have made the request to generate https://www.w3.org/2021/04/15-wot-arch-minutes.html kaz 15:11:35 seb: should we wait for feedback from Ben? 15:12:14 mm: it could add 2 weeks delay 15:13:33 mm: let's note our agreement to adopt the structure of "Protocol Binding" in the issues 15:20:54 mjk: agree with the things not in brackets, and the bracketed items can be left to implementations 15:21:42 mjk: also agree that templated URIs and data schemas can be included somehow 15:21:52 mm: that's a longer discussion 15:21:59 ml: also is TD scope 15:22:23 topic: canonical TD 15:22:50 mm: still working on the specification of the canonical form 15:23:17 ... identifying assertions and thinking about implementation 15:23:39 ... need to find a library to process JCF 15:24:00 i|still working|-> https://github.com/w3c/wot-thing-description/pull/1086 wot-thing-description PR 1086 - Add section to define Canonical serialization| 15:25:35 mm: there is an issue with how to handle the defaults in TD extensions, like http vocabulary 15:26:14 ... defaults are required to be omitted in the canonical form 15:26:50 ... RDF processors will fill in the defaults 15:27:24 ... it makes round-trip processing an issue 15:28:21 ... also an issue of regenerating prefixes 15:32:34 ... (discussion around tradeoffs and issues in TD canonicalization) 15:32:38 rrsagent, draft minutes 15:32:38 I have made the request to generate https://www.w3.org/2021/04/15-wot-arch-minutes.html kaz 15:33:54 ml: canonicalization won't impact the protocol spec 15:34:14 s/protocol/profile 15:38:34 ml: the profile needs to restrict content types 15:39:24 mm: should the profile allow communication without TLS? 15:39:37 s/mm/ml 15:39:56 -> https://w3c.github.io/wot-profile/#protocol-binding WoT Profile Editor's draft - 5.2 Protocol Binding 15:40:24 mm: the local hub server can't use TLS because TLS requires some PKI infrastructure 15:41:44 ... we could provide object security with raw keys 15:44:28 mm: browsers require root certificates 15:48:54 mm: the base plan is to use HTTP without TLS 15:50:39 ... we could allow http but highly recommend https 15:51:12 ml: is there a way we can require https for remote interactions? 15:51:34 ml: we seem to be reaching a common understanding 15:51:47 ... time to close the meeting 15:52:35 ... there are a lot of outstanding issues 15:53:19 -> https://github.com/w3c/wot-profile/issues outstanding issues for wot-profile 15:53:20 mm: maybe we can defer a lot of these and some may not be relevant in the context of the simple profile 15:53:42 i/there are/topic: AOB/ 15:53:45 rrsagent, draft minutes 15:53:45 I have made the request to generate https://www.w3.org/2021/04/15-wot-arch-minutes.html kaz 15:54:57 ml: any other business? 15:55:03 ... adjourn 15:55:07 rrsagent, draft minutes 15:55:07 I have made the request to generate https://www.w3.org/2021/04/15-wot-arch-minutes.html kaz 16:18:09 zkis has joined #wot-arch 17:03:05 Zakim has left #wot-arch