11:57:12 RRSAgent has joined #wot 11:57:12 logging to https://www.w3.org/2022/09/22-wot-irc 11:57:23 meeting: WoT Post-TPAC Meeting - Day 3 12:01:41 ryuichi has joined #wot 12:03:20 McCool has joined #wot 12:03:34 present+ Kaz_Ashimura, Michael_McCool, Kunihiko_Toumura 12:03:38 ktoumura has joined #wot 12:05:24 agenda: https://www.w3.org/WoT/IG/wiki/F2F_meeting,_September_2022#Thursday.2C_September_22 12:06:02 dape has joined #wot 12:06:46 present+ Sebastian_Kaebisch, Ege_Korkan, Tomoaki_Mizushima 12:06:56 present+ Daniel_Peintner 12:06:57 Mizushima has joined #wot 12:07:47 sebastian has joined #wot 12:08:45 zakim, who is on the call? 12:08:45 Present: Kaz_Ashimura, Michael_McCool, Kunihiko_Toumura, Sebastian_Kaebisch, Ege_Korkan, Tomoaki_Mizushima, Daniel_Peintner 12:09:44 topic: Opening 12:09:56 -> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2022-09-hybrid-f2f/2022-09-22-WoT-F2F-Opening-McCool.pdf McCool's slides 12:10:08 mm: (gives latest updates on Architecture) 12:10:52 CR on Oct 12/13; PR on Dec 14/15 earliest 12:10:58 scribenick: sebastian 12:11:09 i/gives/scribenick: kaz/ 12:11:15 topic: CG/Marketing Split 12:11:35 MM: how we make progress on the split? 12:11:57 q+ 12:11:59 Ege: we will have a meeting on Monday and let you know about the outcome 12:14:21 MM: CG is mainly designed to be short term. The main goal should be to build a community. 12:15:50 MM: there is the concerns about publications topics such as RECs etc. CG, however, is not to intended to do so 12:17:49 q? 12:18:01 Ege: the W3C structure such as /WoT/wg/ and /WoT/ig/ is already there for a long time 12:18:57 q+ Studio24 12:19:07 q- Studio24 12:19:15 q+ to Studio24 12:19:52 https://www.w3.org/2022/Talks/0907-deliverables-ka/ 12:21:25 https://www.w3.org/groups/ig/wot this is the automatic page 12:22:52 Kaz: We should reconsidere the relationship between the official w3c managed / system pages (auto-generated) and our manuell creted content 12:23:09 s/creted/created 12:23:18 s/reconsidere/reconsider/ 12:23:25 q? 12:23:31 ack k 12:23:32 ack d 12:23:32 dape, you wanted to Studio24 12:23:37 q+ 12:23:42 q? 12:23:44 q+ 12:24:23 Daniel: it would be great if we could extract the content of the official pages 12:25:00 MM shows https://www.w3.org/groups/wg/wot 12:26:07 q? 12:26:09 Daniel: when we started to work on the new web page, the W3C started to redisign the webpages by Studio24 12:26:11 ack d 12:26:17 ... Im wondering about the status 12:27:38 Kaz: the current proposal of the redisgn is not appropriate 12:28:40 s/redisgn/redesign 12:29:05 Kaz: we should rethink how we can refer to the official auto-generated again. 12:29:11 q? 12:29:13 q+ 12:29:26 ... each group should have own page 12:30:41 q+ 12:31:24 ack dape 12:31:52 Daniel: I see Kaz points, however, for people from the outside do not understand this different groups 12:32:12 Ege: I think also people inside have problems to understand 12:32:21 MM: I agree 12:33:36 Kaz: W3C has an official approach how to represent the groups 12:33:37 q+ 12:34:03 zakim, who is on the call? 12:34:03 Present: Kaz_Ashimura, Michael_McCool, Kunihiko_Toumura, Sebastian_Kaebisch, Ege_Korkan, Tomoaki_Mizushima, Daniel_Peintner 12:34:08 q+ 12:34:17 present+ Cristiano_Aguzzi 12:34:54 ack k 12:36:37 Kaz: I'm not objecting our manuel created webpage. Just want that we consider the relation to the auto-generated content again. 12:38:05 Cris: lets assume the WG stop working, what would be happen with the manuel pages? 12:38:23 q? 12:38:30 ack m 12:39:06 cris_ has joined #wot 12:39:09 s/manuel/manual 12:39:13 s/objecting/objecting to/ 12:39:24 s/manual/manually/ 12:39:37 q+ 12:39:42 ack s 12:41:19 s/created webpage/created WoT landing page, or I'm not saying the page is useless./ 12:41:49 s/Just want that we/Just want to say that we should/ 12:42:03 s/relation to/relationship to/ 12:42:04 ack s 12:42:45 ack e 12:43:38 -> https://www.w3.org/publishing/ Publishing@W3C page 12:44:43 Ege: I think our webpage is a publishing activity webpage since we cover IG and WG 12:48:28 I will be back in 10min 12:48:39 i/I will/kaz: @@@ 12:48:56 mm: what should we do next? 12:49:21 kaz: I want to make sure that everybody understand what this means 12:50:17 mm: what are the next issues? 12:51:08 ek: what are the implications? 12:51:23 kaz: it is in the old process document, it is deleted 3 years ago 12:52:11 ek: can we use our own word? 12:52:15 kaz: no 12:54:01 kaz: it would imply going back to the old process document 12:54:12 mm: why was it removed? 12:55:21 kaz: activity was used to group related groups, old process used to include more stages for going to rec 12:56:17 mm: it would be a disadvantage to go back to the old process 12:56:42 kaz: maybe we can use activity without going back to the old process. We should have a resolution first and go to W3M 12:56:45 s/@@@/As I've been repeatedly mentioning, if we really want to use the term of "Activity" to treat all the WoT-related groups as a chunk, we need to make a whole group resolution, and talk with the W3M/ 12:57:21 https://github.com/w3c/wot/issues/1042 12:57:38 mm: let's continue the agenda 12:57:39 s/use activity/use the term of "Activity"/ 12:58:03 s/We should have/However, we should have/ 12:59:10 mm: kaz can you post further explanation in the issue 12:59:23 rrsagent, make log public 12:59:32 rrsagent, draft minutes 12:59:32 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 12:59:53 q+ 12:59:58 ack k 13:00:03 ack k 13:00:15 chair: McCool/Sebastian 13:00:22 q+ 13:00:31 i/As I've/scribenick: kaz/ 13:00:41 i/what should we/scribenick: Ege/ 13:01:08 rrsagent, draft minutes 13:01:09 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:01:15 ack e 13:01:16 ack d 13:01:20 https://www.w3.org/2022/07/wot-wg-2022.html#other-deliverables 13:01:28 dp: I have been looking in the old charter 13:01:33 s/lets/let's/ 13:01:35 rrsagent, draft minutes 13:01:35 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:02:04 ... and scripting was just another deliverable 13:02:56 s/I want to make sure that everybody understand what this means/Before continuing this discussion, I want to make sure everybody understands what is defined the latest W3C Process and what used to be defined by the old W3C Process documents./ 13:03:02 rrsagent, draft minutes 13:03:02 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:03:19 dp: the consensus was to stick to the current way 13:03:34 mm: is scripting ig or wg? 13:03:37 ek: wg 13:03:39 I'm back, I can take the minutes again 13:03:51 ack dape 13:04:15 s/it is in the old process document, it is deleted 3 years ago/"Activity" was defined in the old W3C Process Document but deleted several years ago./ 13:04:37 mm: I will go in order 13:04:41 s/can we use our own word?/can we use "Activity" as our own word?/ 13:05:23 s/it would imply going back to the old process document/It would imply we (WoT WG) would like to run the group based on the old Process document./ 13:06:07 MM shows the Security Deliverable Proposal PR 13:06:25 https://github.com/w3c/wot/pull/1031 13:06:51 subtopic: security deliverable proposal 13:07:20 q? 13:07:22 q+ 13:07:31 MM: new topic is onboarding 13:07:31 s/can we use "Activity" as our own word?/can we use our own word?/ 13:07:41 rrsagent, draft minutes 13:07:41 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:08:24 ... this should consider security aspects 13:08:27 mm: I have attended the rdf signing 13:08:52 MM: another is about Signing 13:08:57 q+ 13:09:04 s/another/another topic 13:09:14 i|other deliverables|topic: Finalize Deliverable Priorities for next charter| 13:09:24 rrsagent, draft minutes 13:09:24 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:09:35 ... approach should be consistent with RDF/JSON-LD 13:10:56 Matthias Kovatsch mention that we should have a look on IETF JSON Web Proofs 13:11:14 i|#other-deliverables|topic: Finalize Deliverable Priorities for next charter| 13:11:17 rrsagent, draft minutes 13:11:17 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:11:33 s/mention/mentioned 13:12:01 i|I have been|subtopic: Scripting API| 13:12:06 MM: agree, we should also consider IETF activites 13:12:23 s/subtopic: security deliverable proposal// 13:12:26 MM: another topics is about secruity scheme ontology 13:12:46 i|MM shows the Security Deliverable Proposal PR|subtopic: Security| 13:12:48 rrsagent, draft minutes 13:12:48 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:12:58 ... security schemes changes over time 13:12:59 q+ 13:13:17 ack s 13:13:38 i/MM shows/scribenick: sebastian/ 13:13:41 rrsagent, draft minutes 13:13:41 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:13:50 q+ 13:14:20 ... it would be better to have seperated dpcuements to adopt changes faster 13:14:23 ack e 13:14:33 q- 13:14:50 this topic is also relevant for OPC UA security 13:14:58 s/mm: I have attended the rdf signing// 13:15:01 rrsagent, draft minutes 13:15:02 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:15:12 q+ 13:15:45 s/Matthias/sk: Matthias/ 13:16:18 s/what is defined the/what is defined by the/ 13:16:35 q? 13:16:43 rrsagent, draft minutes 13:16:43 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:18:48 Ege: would it possible to have abstract schemes that can be applied to multiple protocols. Eg, basic scheme 13:20:55 kaz: @@@ 13:21:34 Kaz: I'm agree with MM proposal. We should be careful about the content, we should check it with existing work at the W3C 13:21:54 s/@@@// 13:22:06 subtopic: Thing Description 2.0 13:22:27 https://github.com/w3c/wot/pull/1033 13:23:03 MM: there are some feedback about actions from Ben 13:23:53 ... I miss the WebThink protocols for the payload driven protocols 13:24:07 s/I'm agree with MM proposal. We should be careful about the content, we should check it with existing work at the W3C/I basically agree with McCool's proposals. We should be consistent with the VCWG's work. Also should use standardized vocabularies to define the WoT Security features. On the other hand, we should be careful about how to use the content within the Security deliverables, because part of that should be transferred to the other WoT 13:24:07 deliverables like TD later./ 13:24:22 rrsagent, draft minutes 13:24:22 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:24:55 s/this topic is also/sk: this topic is also/ 13:24:59 rrsagent, draft minutes 13:24:59 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:25:25 s|deliverables like TD later./|| 13:25:54 s/to the other WoT/to the other WoT deliverables like TD later./ 13:25:56 rrsagent, draft minutes 13:25:56 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:26:25 MM: we have TM for TD directory. How about TM for Thing Shadows? 13:26:36 s/kaz: // 13:26:37 rrsagent, draft minutes 13:26:37 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:26:49 .. is this a topic for TD? 13:27:29 s/WebThink/WebThing/ 13:28:11 q+ 13:28:51 q+ 13:29:05 q- later 13:30:44 q+ 13:31:38 q+ 13:31:41 cris_ has joined #wot 13:31:51 q+ 13:32:20 ack 13:32:26 ack s 13:32:43 dezell has joined #wot 13:32:48 present+ 13:32:55 present+ David_Ezell 13:33:03 sk: we should also consider to have a "Consumer Description". TD mainly address Producer, but we have nothing for consumer. 13:33:16 ack m 13:33:40 Kaz: we should comment on github 13:34:50 q+ 13:34:53 ack k 13:36:04 ack e 13:36:22 s/we should comment on github/we should create another topic and issue for the need for a potential "Consumer Description", and I'd like to go back to the discussion on the time-series data./ 13:36:34 q+ 13:37:40 kaz: @@@ 13:37:41 Ege: about consumer description, there is a use case coming from profile about the web hooks discussion 13:38:06 q+ 13:39:35 s/@@@/regarding the time-series data, I think we should think about video stream data as well. During TPAC 2022, I attended the MEIG meeting as well and there was discussion on handling video stream data using Web Transport, etc., and surveillance video output was also included there./ 13:39:48 Cris: I'm interested in video streams. I have some examples and contribute here (I have a node-wot implementation that I can share) 13:39:55 ack c 13:40:07 q- 13:41:23 ... I have some concern about the consumer description. It is hard to clearify who need a consumer desctipion 13:42:22 q+ 13:45:11 ack mc 13:45:31 ack s 13:45:50 13:46:40 q? 13:47:55 q+ 13:48:01 q+ 13:48:03 ack k 13:48:07 ack k 13:48:17 kaz: agree to gather ideas (brainstorming) today 13:48:33 ... and we need to look into what those ideas would mean next 13:48:46 ... also as a general comment @@ 13:49:02 Ege has joined #wot 13:49:33 s/@@/we should revisit the inputs from the other SDOs, e.g., ECHONET, like history management and grouping of actions./ 13:49:38 rrsagent, draft minutes 13:49:38 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:49:41 q+ 13:49:46 ack cris 13:50:33 i/agree to/scribenick: kaz/ 13:50:58 rrsagent, draft minutes 13:50:58 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:52:01 topics around TD should be discussed in the next TD call. 13:52:04 i/regarding the time/scribenick: kaz/ 13:52:14 i/about consu/scribenick: sebastian/ 13:52:16 rrsagent, draft minutes 13:52:16 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:52:36 subtopic: Profiles 13:52:40 q+ 13:52:53 https://github.com/w3c/wot/pull/1034 13:53:11 s/topics around/Ege: topics around/ 13:53:23 MM: we should discuss this in the next main call. is this ok? 13:53:39 rrsagent, draft minutes 13:53:40 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:54:25 q+ 13:54:42 i/topics around/scribenick: sebastian/ 13:54:43 rrsagent, draft minutes 13:54:44 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz 13:56:14 q? 13:56:16 ack s 13:56:17 ack s 13:56:19 ack e 13:56:19 ack e 13:56:25 sk: new profiles should be designed together with other SDOs 13:57:22 kaz: we should clarify what is expected for a Profile or Profiles a bit more 13:57:22 subtopic: Binding Templates 13:57:28 s/we/also we/ 13:57:37 i/we should/scribenick: kaz/ 13:57:43 scribenick: sebastian 13:57:46 ack k 13:58:03 https://github.com/w3c/wot/pull/1035 13:58:21 13:59:20 q+ 13:59:31 q+ 13:59:42 ack c 13:59:55 topic: Planning 14:00:06 MM: we have a TestFest next week 14:00:26 ... I will send a mail about organiziation 14:00:38 ack m 14:00:40 ack k 14:01:17 mm: let's stick with webex, I have problems with zoom 14:01:41 i|let's|scribenick: Ege| 14:01:44 q+ 14:01:56 ... we need implementations for the architecture 14:02:33 ack k 14:03:40 kaz: we need to get well-prepared, so need to let people know about what they need to do :) 14:03:57 mm: that is all, let's review minutes in anothecall 14:04:13 s/anothcall/another call/ 14:04:19 [adjourned] 14:04:24 rrsagent, draft minutes 14:04:25 I have made the request to generate https://www.w3.org/2022/09/22-wot-minutes.html kaz