16:01:08 <RRSAgent> RRSAgent has joined #wot-arch
16:01:08 <RRSAgent> logging to https://www.w3.org/2021/03/04-wot-arch-irc
16:01:15 <kaz> Meeting: WoT Architecture
16:05:58 <kaz> present: Kaz_Ashimura, Michael_Lagally, Philipp_Blum, Tomoaki_Mizushima
16:06:13 <kaz> present+ Michael_McCool
16:06:54 <kaz> scribenick: kaz
16:06:58 <kaz> topic: prev minutes
16:07:08 <kaz> -> https://www.w3.org/2021/02/25-wot-arch-minutes.html Feb-25
16:07:15 <kaz> ml: (goes through the minutes)
16:08:12 <kaz> present+ Sebastian_Kaebisch
16:08:48 <kaz> Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#March_4th.2C_2021
16:09:10 <sebastian> sebastian has joined #wot-arch
16:09:46 <kaz> ml: any problems?
16:10:01 <kaz> (none; approved)
16:10:14 <kaz> topic: vF2F
16:11:05 <kaz> -> https://www.w3.org/WoT/IG/wiki/F2F_meeting,_March_2021#Agenda vF2F agenda
16:11:34 <kaz> ml: (goes through the agenda for March 22)
16:12:14 <kaz> ... terminology, ITU-T liaison, ...
16:12:39 <kaz> ... partial TD discussion?
16:13:02 <kaz> mm: terminology discussion? or use case discussion?
16:13:33 <kaz> ... maybe could move this topic earlier during the terminology session
16:13:49 <kaz> ml: (moves "partial TD" topic to the terminology session
16:14:03 <kaz> s/session/session)
16:14:18 <kaz> mm another issue is validation
16:14:44 <kaz> ml: (adds "TD validation" as well to the terminology session)
16:14:52 <kaz> ... ("framing" too)
16:15:09 <kaz> s/mm another/mm: another/
16:15:24 <kaz> mm: also should discuss here or during the TD day
16:15:58 <kaz> ... relate to both TD and discovery, so during the Architecture call makes sense
16:16:22 <kaz> ... not only terminology but also part of TD discussion
16:16:57 <kaz> sk: btw, some kind of introductory talk at the beginning would be useful, wouldn't it?
16:17:04 <kaz> q+
16:17:25 <kaz> ml: good point
16:17:49 <kaz> mm: each subsection from each day has assigned owner
16:18:02 <kaz> ... and those owners are to generate some introduction
16:19:27 <kaz> ml: will clean up the remaining issues on GitHub
16:19:42 <kaz> ... and assign them to proper people
16:20:29 <kaz> mm: my expectation is closing all the terminology issues during the vF2F
16:20:31 <kaz> ml: ok
16:20:58 <kaz> ack k
16:21:05 <mlagally_> mlagally_ has joined #wot-arch
16:21:49 <kaz> kaz: just wanted to make sure the introduction at the beginning is strictly focused on the topics from that day
16:21:52 <kaz> all: right
16:22:08 <kaz> kaz: also should make sure the introduction should be brief enough :)
16:23:34 <kaz> ... we already have introduction session on the first day, March 15
16:24:08 <kaz> ... so please make sure to use the additional introduction sessions on other days in a productive manner ;)
16:24:21 <kaz> mm: let's have some more discussion during the main call
16:24:30 <kaz> ml: (moves ahead)
16:24:41 <kaz> ... what about Profiles?
16:25:16 <kaz> mm: need to get resolution about one or multiple profiles
16:25:44 <kaz> sk: core profile now and additional profiles later?
16:25:57 <kaz> ml: that's my understanding as well
16:26:17 <kaz> sk: my question is still about the term of "core", though
16:27:29 <kaz> mm: if we have constrained devices, do we want to define some profile for them?
16:27:57 <kaz> sk: WoT as a whole doesn't care about what the devices are actually are
16:28:09 <kaz> s/devices are/devices/
16:28:39 <kaz> ml: having the information about the expected classes to avoid confusion on the gateways, etc.
16:29:16 <kaz> sk: wondering about concrete use cases for this approach
16:29:36 <kaz> ml: we're working on a use case
16:29:52 <kaz> sk: what is the real use case and scenario then?
16:30:19 <kaz> q?
16:30:25 <kaz> q+
16:31:45 <kaz> kaz: so we're generating some concrete use case description now
16:31:59 <kaz> ... and will discuss that during the vF2F
16:32:56 <kaz> ack k
16:33:12 <kaz> ml: (shows RFC7228 as the basis of the class definition)
16:33:23 <citrullin> citrullin has joined #wot-arch
16:33:50 <kaz> -> https://tools.ietf.org/html/rfc7228 RFC 7228
16:34:43 <kaz> ml: this definition is just a proposal at the moment
16:35:08 <kaz> mm: btw, class 3 might be for something like gateway
16:35:30 <kaz> ... on the other hand, class 4/5 are more for something like Raspberry Pi
16:35:39 <kaz> ... and Class 6 can be a server
16:36:02 <kaz> ... the classes are defined by IETF by an RFC
16:36:59 <kaz> ... and what to do next is thinking about what capacity is required for what purposes
16:37:18 <kaz> ... target platform based on some given function
16:37:49 <kaz> sk: even a constrained device can generate some big Thing Description
16:37:58 <kaz> q+
16:38:38 <kaz> kaz: in that case, maybe we need to think about TAT as well as the hardware power
16:38:40 <citrullin> The minutes about some potential issue with contrained devices in security -> https://www.w3.org/2021/02/15-wot-sec-minutes.html
16:38:44 <kaz> mm: also thought about that
16:39:09 <kaz> ... but memory, etc., are easier to start with
16:39:19 <kaz> kaz: ok, starting with easier point is fine
16:39:25 <kaz> ack k
16:40:19 <kaz> mm: do we keep it as a PR to see the preview?
16:40:38 <kaz> ml: can push the changes so that we can see them
16:41:03 <kaz> ... (push some updates to PR 70)
16:42:54 <kaz> -> https://pr-preview.s3.amazonaws.com/w3c/wot-profile/70/594c374...c4b57d1.html#device-categoriesdevices PR 70 - 5. Device Categories
16:43:30 <kaz> mm: would fill in something from the security viewpoint
16:44:08 <kaz> ... minimal requirements for secure systems
16:44:33 <sebastian> q+
16:44:52 <kaz> topic: Terminology (revisited)
16:45:45 <kaz> -> https://pr-preview.s3.amazonaws.com/w3c/wot-architecture/582/c0c8113...mmccool:31e933d.html#terminology PR 582 - 3. Terminology
16:46:10 <kaz> ml: (goes through the changes)
16:46:21 <kaz> mm: partial TD
16:46:23 <kaz> ... Shadow
16:46:26 <kaz> ... TDD
16:46:51 <kaz> ... TD Element - replacement of "TD Fragment"
16:47:35 <kaz> ml: note we need another entry for "Thing Description Element"
16:47:38 <kaz> mm: right
16:48:23 <kaz> ... there is a definition a bit below (after "Thing Model")
16:48:46 <kaz> ... still need further work here
16:49:36 <kaz> ... my hope is leave this PR 582, get more feedback, and finalize the terminology during the vF2F
16:49:50 <kaz> ml: ok
16:50:22 <kaz> mm: we should separate the definition itself and the name of terms
16:50:24 <kaz> ml: ok
16:50:41 <kaz> mm: please do give comments on the PR 582
16:50:43 <kaz> ml: ok
16:50:50 <kaz> ... will ask the group to do so
16:50:58 <kaz> ... AOB?
16:51:01 <kaz> (none)
16:51:07 <kaz> q?
16:51:09 <kaz> ack s
16:51:18 <kaz> s/(none)//
16:51:45 <kaz> sk: still have an impression that my concern is not handled seriously enough...
16:52:20 <kaz> mm: let's see what the real issues here
16:54:43 <kaz> sk: would like to see the actual purpose of the profile
17:08:00 <kaz> kaz: would suggest we clarify what we want to have by defining "profiles"
17:08:58 <kaz> ... and see use cases and scenarios based on some concrete device settings
17:09:33 <kaz> sk: would be nice to create an issue to collect concrete scenarios
17:09:35 <kaz> mm: ok
17:11:24 <kaz> -> https://github.com/w3c/wot-profile/issues/71 Issue 71
17:12:00 <kaz> s/Issue 71/Issue 71 - Collect Use Cases and Scenarios for Profiles/
17:12:02 <kaz> r
17:12:05 <kaz> s/r//
17:12:08 <kaz> [adjourned]
17:12:12 <kaz> rrsagent, make log public
17:12:17 <kaz> rrsagent, draft minutes
17:12:17 <RRSAgent> I have made the request to generate https://www.w3.org/2021/03/04-wot-arch-minutes.html kaz
17:47:45 <zkis> zkis has joined #wot-arch
18:59:22 <Zakim> Zakim has left #wot-arch