12:55:19 RRSAgent has joined #wot 12:55:23 logging to https://www.w3.org/2023/01/19-wot-irc 12:55:29 meeting: WoT WG Charter - Day 4 12:55:37 present+ Kaz_Ashimura 13:00:48 McCool has joined #wot 13:01:30 Ege has joined #wot 13:02:33 present+ Ege_Korkan, Erich_Barnstedt, Kunihiko_Toumura Michael_Koster, Michael_McCool 13:02:33 ktoumura has joined #wot 13:02:53 q+ 13:03:02 present+ Sebastian_Kaebisch 13:03:17 q- 13:03:22 sebastian has joined #wot 13:03:24 dape has joined #wot 13:04:08 present+ Tetsushi_Matsuda 13:04:31 matsuda has joined #wot 13:04:40 Mizushima has joined #wot 13:04:53 q? 13:06:42 present+ Kunihiko_Toumura 13:06:59 q+ 13:07:15 q+ 13:07:36 ack e 13:07:44 scribenick: sebastian 13:08:02 present+ Ben_Francis 13:08:30 mlagally_ has joined #wot 13:08:37 13:09:11 https://github.com/w3c/wot/issues/1051 13:09:33 kaz: agree we need further discussion, and need to see good slot using Doodle. @@@ 13:10:23 q+ 13:10:25 MM: should collect the points in the issue 13:11:18 Kaz: Charter is an abstract plan for the next 2 years. 13:11:33 cris_ has joined #wot 13:11:34 s/@@@/However, before holding further discussion, we should clarify what to be described for the Charter./ 13:12:09 ack k 13:12:36 s/2 years./2 years, so it's different from C language code or programming script. So we need to review the whole Charter document section by section./ 13:12:39 q? 13:12:42 ack b 13:13:05 q+ 13:13:13 Ben: please do not forget profile. Question to Kaz: how much details is needed? 13:14:08 present+ Tomoaki_Mizushim 13:14:16 present- Tomoaki_Mizushim 13:14:20 present+ Tomoaki_Mizushima 13:14:20 Kaz: We should clearify our plan, also about the cooperation partners. Too much details is not needed 13:14:34 s/details/detail/ 13:15:40 13:15:41 s/not needed/not needed. On the other hand, we need to identify what document we would like to generate, which of them are normative. Also joint deliverables based on official liaison with external SDOs./ 13:15:51 topic: Profile 13:15:59 13:16:20 -> https://github.com/w3c/wot/pull/1056 13:16:52 MM: Im ok merging this. However the term "interoperability profile" sounds strange. 13:16:56 +1 13:16:59 s/topic: Profile/subtopic: Profile/ 13:17:10 i/subtopic: Profile/topic: Deliverables/ 13:17:38 s|pull/1056|pull/1056 PR 1056 - WG 2023 Charter - Profile Work Items| 13:17:47 rrsagent, make log public 13:17:52 rrsagent, draft minutes 13:17:53 I have made the request to generate https://www.w3.org/2023/01/19-wot-minutes.html kaz 13:18:14 chair: McCool 13:18:33 13:18:47 present+ Cristiano_Aguzzi, Michaeel_Lagally 13:18:49 rrsagent, draft minutes 13:18:51 I have made the request to generate https://www.w3.org/2023/01/19-wot-minutes.html kaz 13:19:00 q+ 13:19:02 q? 13:19:05 q+ 13:19:30 Ben: Complete the transition, Normatively define one or more profiles which specify how to observe properties and subscribe to events over HTTP, Consider defining other profiles and Stretch goal 13:20:03 q+ 13:20:23 qq+ 13:20:55 q- Mc 13:21:02 ML: we should finalize Profile 1.0 in the current charter to avoid complicated versioning 13:21:05 q- Mc 13:21:10 q- ml 13:21:28 i/McCool ask the group/topic: Organization/ 13:21:37 i/agree we need/scribenick: kaz/ 13:21:53 i/should collect the points/scribenick: sebastian/ 13:22:08 ack mccool 13:22:08 MM: Proposal is do not mention any version number to be on the safe side 13:22:11 q+ 13:22:25 ack ege 13:22:41 Ege: we should not do detail discussion yet 13:23:15 dezell has joined #wot 13:23:41 present+ David_Ezell 13:24:21 q? 13:24:26 ack k 13:24:47 Kaz: we should be careful what is our expectations on profile in the charter 13:25:32 Ben: Im ok removing version number 13:26:20 s/we should/agree. Again, a Charter document is abstract plan on our 2-year Charter period. So we should just explain what "WoT Profile" is like./ 13:26:22 q? 13:26:25 q+ 13:27:02 topic: Publication status 13:27:31 kaz: Profile WD was published yesterday, and TD 1.1, Discovery and Architecture 1.1 were published today./ 13:27:39 mm: will update the schedule 13:27:43 ack mc 13:27:44 Ben: Profile document should be independent and not depend on Architecture 13:27:45 ack k 13:27:52 scribenick: kaz 13:28:05 i/Profile/scribenick: kaz/ 13:28:11 i/Ben:/scribenick: sebastian/ 13:28:34 topic: Liaisons 13:28:52 sk: we have good baseline for our building blocks 13:29:03 ... should think about how to adopt to the other SDOs 13:29:16 ... the next Charter should cooperate with well known SDOs 13:29:33 ... which are focusing on industry standards 13:29:49 ... e.g., ECLASS 13:30:13 q+ 13:30:38 i|we have|@@@ url| 13:30:47 sk: strong connection with OPC as well 13:31:20 q+ 13:31:40 mm: don't think we can say "will" here 13:32:10 ... that's too strong word to put here 13:32:28 ... then the target should be OPC UA 13:32:30 q? 13:32:32 ack mc 13:32:44 eb: good organization with 900 Members 13:33:03 ... working on industry interoperability standards 13:33:26 ... Sebastian and I are thinking about potential mapping between OPC UA and WoT 13:33:41 mm: absolutely agree with the cooperation itself 13:33:52 ... but we need to work with the W3M about the liaison 13:33:56 q? 13:34:01 q+ 13:34:24 ... new W3C should be interested in industry adoption 13:35:00 present+ Daniel_Peintner 13:35:09 ack k 13:35:22 -> https://www.w3.org/2021/10/sdw-charter.html sdw wg charter 13:36:37 kaz: I suggested we look at the SDW WG Charter as an example @@@ 13:36:59 sk: agree Charter is basic policy and plan 13:37:33 ... however, there have been discussions between OPC and W3C 13:37:50 kaz: I know, but we don't need to explain the history within the Charter 13:37:52 ack ml 13:38:02 ml: this is important initiative 13:38:36 ... would it be possible to ask them to actively participate in the W3C WoT standardization work? 13:38:42 mm: who do you mean? 13:39:08 sk: there is a huge list here 13:39:18 q? 13:39:20 q+ 13:39:26 ack k 13:40:17 (we should discuss how to make them participate separately) 13:41:21 q? 13:41:23 sk: (talks about Industrial Digital Twin Association) 13:41:48 q+ 13:41:54 ... official liaison and close exchange to be done 13:42:37 q+ 13:42:39 ml: call out Platform 4.0? 13:42:46 sk: it's also included 13:42:56 q? 13:43:01 ack ml 13:43:03 ack e 13:43:20 ek: copied others from the current Charter 13:43:29 ... and we should review this list again 13:43:37 q+ 13:44:23 mm: (shows the rendered version) 13:44:30 ... separate out the previous list 13:44:34 ... pointing out the longer list 13:44:49 ... which ones to be expected for collaboration? 13:45:13 ek: should be a single list in the end 13:45:44 q? 13:46:45 kaz: I'm OK with merging this PR as the starting point with candidates 13:47:23 q+ 13:47:40 ... but as I've been asking, we need to clarify how to get what kind of feedback 13:47:41 [[ 13:47:41 xample deliverable template for liaisons: 13:47:41 What: Binding Templates, Vocabulary and Ontology, Conformance tests 13:47:41 How: A separate joint WG?, WoT WG as a joint WG?, a TF within the WoT WG?, just part of the TD/Binding discussion? 13:47:42 Who: Editors from W3C, OPC and/or ECHONET? 13:47:44 Resources: Technical Requirements for OPC UA liaison 13:47:46 ]] 13:48:33 s/feedback/feedback from whom. For example, directly to the WoT WG, via the WoT IG, via the WoT CG or via the WoT-JP CG/ 13:49:01 sk: agree we should make another iteration 13:49:05 s/xample/Example/ 13:49:28 q+ Erich 13:49:31 ack k 13:49:32 ack ml 13:49:39 ack eri 13:49:43 q+ mlaglly_ 13:50:00 q+ 13:50:51 mm: need to capture the content for each org 13:51:25 ml: would suggest we put some specific examples 13:51:31 ... in some areas 13:51:41 ... asking about the purpose of this list 13:51:50 ... we should have good understanding 13:52:05 ack ml 13:52:11 q+ 13:52:16 +1 13:52:19 +1 13:52:23 ... exchanging opinions, asking reviews, etc. 13:52:38 mm: complete list would be huge 13:52:54 ... may be open-ended 13:53:10 ... could list only new ones 13:53:19 ml: sounds like a good idea 13:54:40 q+ 13:54:42 q? 13:55:05 kaz: would make sense to categorize our expectations and explain the expectation instead of the huge list 13:55:17 ... can have actual list outside of the Charter doc 13:55:20 ack k 13:55:22 ack s 13:55:43 sk: agree with Lagally that we should not just have a simple list 13:56:10 ... we could tidy up the list a bit 13:56:25 ... and need to identify why we need to have whom there 13:56:33 mm: yeah, that's right 13:56:37 q+ 13:57:01 ... on the other hand, we still have connection with SDOs from the prev Charter as well 13:57:24 ml: for example, working closer with those SDOs on use cases, etc. 13:57:45 bf: glad to see Digital Twin there 13:58:05 ... but some of the listed entities are not SDOs 13:58:09 eb: good question 13:58:18 ... standardization takes long 13:58:39 ... most of the reference implementation is done by DTC, for example 13:58:42 q+ 13:58:51 s/there/Consortium there/ 13:59:01 ack b 13:59:15 eb: I'm working on WoT within MS 13:59:19 q+ 13:59:36 ml: we should some gap analysis 14:00:08 ... coordination and alignment would be good 14:00:12 q? 14:00:13 ack ml 14:00:15 ack m 14:01:17 kaz: as mentioned 5 mins ago... 14:01:33 mm: would have a link to a wiki page, for example 14:01:44 ... let's continue the discussion on GitHub 14:01:51 q+ 14:01:53 ... and find time for further discussion 14:01:55 ack k 14:02:01 ack e 14:02:28 ek: we're asked to to think about the WoT CG collaboration as well 14:02:29 q+ 14:02:37 I have to go to next meeting 14:02:39 https://github.com/w3c/wot/pull/1064 14:02:54 ek: need review for the above PR 1064 14:03:13 mm: unfortunately, we need much more time to finalize the Charter 14:03:43 [adjourned] 14:03:45 q- 14:03:51 rrsagent, draft minutes 14:03:52 I have made the request to generate https://www.w3.org/2023/01/19-wot-minutes.html kaz 15:38:08 zkis has joined #wot 16:22:40 Zakim has left #wot