10:47:44 RRSAgent has joined #wot-arch 10:47:44 logging to https://www.w3.org/2022/01/27-wot-arch-irc 10:59:20 meeting: WoT Architecture 11:00:16 mlagally_ has joined #wot-arch 11:01:56 present+ Kaz_Ashimura, Michael_Lagally, Michael_McCool 11:02:01 Mizushima has joined #wot-arch 11:05:32 present+ Ege_Korkan 11:05:38 present+ Ryuichi_Matsukura 11:05:54 McCool has joined #wot-arch 11:06:09 ryuichi has joined #wot-arch 11:06:09 topic: minutes 11:06:32 ml: noticed a few things, font on point 0 is strange 11:06:53 ... and a typo, Editors spelling 11:07:33 i|noticed|-> https://www.w3.org/2022/01/20-wot-arch-minutes.html Jan-20| 11:08:53 ml: hearing no objections, minutes approved 11:08:59 topic: publication timeline 11:09:02 i/hearing/(fixed)/ 11:09:08 ml: let's confirm current plan 11:09:21 ... Feb 4 is next week's call 11:09:32 ... normative sections; is an issue for that, by next week 11:09:38 ... also normative feature freeze 11:10:14 present+ Sebastian_Kaebisch, Tomoaki_Mizushima 11:10:23 mm: would be helpful to have an updated list of assertions 11:10:25 rrsagent, make log public 11:10:29 rrsagent, draft minutes 11:10:29 I have made the request to generate https://www.w3.org/2022/01/27-wot-arch-minutes.html kaz 11:10:46 mm: want to make sure that if we wanted to move an assertion it was done 11:11:11 q+ 11:11:48 kaz: need to check document level consistency first, and then assertions 11:12:02 ktoumura has joined #wot-arch 11:12:15 ... document consistency is Feb 4 11:12:35 mm: what does document consistency entail? 11:13:13 ... I assume is also means checking terminology, etc. 11:13:28 ... basically I'm saying a more detailed checklist would be helpful 11:13:46 ml: ok, let's create an issue 11:13:56 ... to review document consistency 11:14:22 ... verifying terminology 11:14:26 ... checking text 11:14:38 ... in normative chapters 11:14:54 ... verifying assertions are fit for purpose 11:15:13 ... proposing additional normative text if required 11:15:59 mm: if someone notices an issue, please create a PR to fix it so we can resolve it next week 11:17:23 mm: should we separate internal and inter- document consistency? 11:19:07 ml: that work has been ongoing for a while 11:19:26 mm: not saying we do the work next week, just that we check it has been done and confirm it 11:20:49 ml: will assign all task force leads 11:21:31 chair: Lagally 11:22:03 present+ Kunihiko_Toumura 11:22:14 ml: please review entire doc, not just a few sections... looking for consistency problems 11:23:20 mm: I assume we will also be suppressing empty sections, editor's comments, etc? 11:23:44 ml: depends on the case 11:24:08 mm: ok, then let's flag issues in such sections if we see them, e.g. normative text inside an editor's comment 11:25:40 topic: contributions 11:27:38 ml: what about hubs PR? 11:27:50 mm: still needs to be finished, is important, but is not normative 11:28:03 ml: ok, PR #658 11:28:13 ... Improve Section Structure 11:28:51 ... fixed a missing closing tag, and also fixed a reference to use cases that used a fixed section number 11:29:24 ... changed name of "System Components" to "System Concepts" 11:29:41 ... and 6.9, System Integration, is a subsection 11:31:14 mm: also cross-domain collab very similar, makes sense to have these be siblings 11:31:51 ml: propose merging 11:31:55 mm: concur 11:32:04 ml: merged 11:32:14 ml: pr #665 11:32:22 ... placeholder section on orchestration 11:33:52 i|what about hubs|subtopic: PR 603| 11:34:13 i|what about hubs|-> https://github.com/w3c/wot-architecture/pull/603 PR 603 - WIP: Define and Discuss "Hubs"| 11:34:31 i|ok, PR #658|subtopic: PR 658| 11:35:00 i|ok, PR #658|-> https://github.com/w3c/wot-architecture/pull/658 Improve section structure| 11:35:17 i|p #665|subtopic: PR 665| 11:35:26 mm: not sure it belongs under digital twins 11:35:44 i|p #665|-> https://github.com/w3c/wot-architecture/pull/665 PR 665 - placeholder section on orchestration| 11:36:23 ... but think we can put it in for now, and reorganize later 11:36:47 mm: pr #667 11:36:56 ... virtual things 11:37:05 i|pr #667|subtopic: PR 667| 11:37:33 i|pr #667|-> https://github.com/w3c/wot-architecture/pull/667 PR 667 - adding placeholder section for virtual things| 11:38:19 mm: are we sure it doesn't appear somewhere else? 11:39:10 q? 11:39:14 ack k 11:39:17 q+ Ege 11:39:19 ack e 11:39:26 mm: definition is also a little odd, just components, not other things we have discussed, eg. room 11:40:04 ege: composition mechanism deals with rooms, etc. 11:40:40 q+ 11:41:08 -> https://en.wikipedia.org/wiki/Virtual_device Virtual device 11:41:13 -> https://en.wikipedia.org/wiki/Digital_twin Digital twin 11:41:42 mm: agree we need a more detailed description of this concept 11:41:58 kaz: are some wikipedia entries for this term also we should look at 11:42:02 q+ 11:42:07 ack k 11:42:52 seb: want to mention we have a definition of virtual thing, since arch 1.1 11:43:42 ml: so you're saying we have a definition and should not touch it 11:44:36 seb: so why are we bringing this up now? 11:44:56 mm: I think the problem is we just don't have enough discussion of its purpose 11:47:07 mm: is it like a "virtual class" (no affordances) or a non-physical service (e.g. a simulation) 11:47:55 ml: placeholder section only for now 11:48:17 mm: agree we should add the section, then capture input in the issue, have a consensus, then add content 11:48:33 q? 11:48:35 ack s 11:48:37 ml: PR #668 11:48:44 ml: merged 11:48:51 ml: pr #669 11:48:53 i|PR #668|subtopic: PR 668| 11:49:15 i|PR #668|-> https://github.com/w3c/wot-architecture/pull/668 PR 668 - remove remove-arch-op-wellknown-compare assertion| 11:49:26 i|PR #669|subtopic: PR 669| 11:49:53 ml: Producer 11:50:07 i|PR #669|-> https://github.com/w3c/wot-architecture/pull/669 PR 669 - Producer definition| 11:50:07 mm: note "Exposer" has been used before, and is more consistent 11:50:44 ... but I think Producer sounds better 11:51:03 q+ 11:51:31 mm: just noting it is inconsistent, not suggesting we change it 11:51:50 kaz: right now Producer is used just once 11:52:02 ... but Expose verbs are used a lot more 11:52:36 mm: suggesting we allow both Exposer and Producer as synonyms 11:52:47 kaz: Producer implies generation as well 11:53:35 mm: right, Exposer does not imply generation, and there cases where the Thing exposing a TD is not generating it 11:53:42 ... e.g. a proxy 11:53:51 ack k 11:54:14 ml: also note that events also use the verb producer 11:55:32 mm: maybe we should hold off on this PR until we gather more input 11:55:55 ml: proposed text also have "specific" thing 11:56:22 ... also "create" 11:56:43 mm: perhaps "create" should be "makes available", since again, it may not "generate" it 11:56:57 ... case of the proxy again, or even just a database 11:57:13 ... e.g. a database 11:57:19 ml: pr #677 11:57:34 ml: removing table 1, we discussed this at length already 11:57:46 ml: conflicts, can we agree to merge it? 11:57:59 mm: concur 11:58:40 ml: seems to be no objections 11:59:22 ml: pr #679 11:59:27 mm: a draft 11:59:34 i|pr #677|subtopic: PR 677| 11:59:39 ml: but may be good to merge so people know about the issue 12:00:01 mm: ok, then I'll work on a separate PR with actual new considerations 12:00:11 i|pr #677|-> https://github.com/w3c/wot-architecture/pull/677 PR 677 - removing table 1| 12:00:21 i|pr #679|subtopic: PR 679| 12:00:48 ml: issue #678 12:00:50 i|pr #679|-> https://github.com/w3c/wot-architecture/pull/679 PR 679 - Update Security and Privacy Considerations| 12:01:08 ml: respec errors, please volunteer to clean up if you can 12:01:10 i|issue #678|subtopic: Issue 678| 12:01:48 i|issue #678|-> https://github.com/w3c/wot-architecture/issues/678 Issue 678 - Fix Respec errors| 12:01:50 [adjourned] 12:01:54 rrsagent, draft minutes 12:01:54 I have made the request to generate https://www.w3.org/2022/01/27-wot-arch-minutes.html kaz 13:59:32 Zakim has left #wot-arch 15:00:48 zkis has joined #wot-arch 15:19:21 kaz has joined #wot-arch 16:16:54 zkis has joined #wot-arch 16:31:25 zkis has joined #wot-arch 16:47:55 zkis_ has joined #wot-arch 16:49:52 sebastian has joined #wot-arch