14:59:56 <RRSAgent> RRSAgent has joined #wot
14:59:56 <RRSAgent> logging to https://www.w3.org/2022/09/14-wot-irc
15:00:22 <kaz> meeting: WoT TPAC F2F - Day 2
15:00:43 <benfrancis1> benfrancis1 has joined #wot
15:00:54 <ktoumura> ktoumura has joined #wot
15:02:18 <kaz> present+ Kaz_Ashimura, Shinya_Takami, Michael_McCool, Sebastian_Kaebisch
15:03:06 <kaz> present+ Javad, Kevin_Dean, Kawada
15:03:13 <kaz> present+ Brent
15:04:25 <kaz> present+ Ben_Francis, Hiroki_Endo, Christian_Glomb, Hiroki_Endo, Kunihiko_Toumura, Jiye_Park, Motoki_Mizusako
15:04:34 <kaz> present+ Tomoaki_Mizushima
15:05:00 <kaz> present+ Richard_Worth
15:05:20 <kaz> present+ Geunhyung_Kim
15:05:37 <kaz> present+ Seukyoon_Kang
15:05:44 <kaz> rrsagent, make log public
15:05:48 <kaz> rrsagent, draft minutes
15:05:48 <RRSAgent> I have made the request to generate https://www.w3.org/2022/09/14-wot-minutes.html kaz
15:05:56 <jiye> jiye has joined #wot
15:06:10 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/F2F_meeting,_September_2022#Wednesday.2C_September_14
15:06:19 <kaz> topic: Logistics
15:06:29 <cris_> cris_ has joined #wot
15:06:35 <cris_> present+ Cristiano_Aguzzi
15:07:09 <furoshiki> furoshiki has joined #wot
15:07:19 <kaz> -> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2022-09-hybrid-f2f/2022-09-14-WoT-F2F-Opening-Sebastian.pdf Day 2 logistics
15:07:37 <kaz> present+ Bradley_Needham
15:07:48 <kaz> present+ Hiroshi_Fujisawa
15:07:55 <McCool> q?
15:07:57 <furoshiki> q+
15:07:59 <kaz> present+ Kinji_Matsumura
15:08:03 <javadch> javadch has joined #wot
15:08:03 <McCool> present?
15:08:04 <bneedham> bneedham has joined #wot
15:08:24 <kaz> zakim, who is on the call?
15:08:24 <Zakim> Present: Kaz_Ashimura, Shinya_Takami, Michael_McCool, Sebastian_Kaebisch, Javad, Kevin_Dean, Kawada, Brent, Ben_Francis, Hiroki_Endo, Christian_Glomb, Kunihiko_Toumura, Jiye_Park,
15:08:27 <Zakim> ... Motoki_Mizusako, Tomoaki_Mizushima, Richard_Worth, Geunhyung_Kim, Seukyoon_Kang, Cristiano_Aguzzi, Bradley_Needham, Hiroshi_Fujisawa, Kinji_Matsumura
15:08:43 <Geun-Hyung_Kim> Geun-Hyung_Kim has joined #wot
15:08:51 <furoshiki> p+
15:08:55 <Geun-Hyung_Kim> present+
15:08:59 <sebastian> q?
15:09:03 <bneedham> p+
15:09:04 <furoshiki> present+ Hiroshi_Kawada
15:09:16 <shiestyle> shiestyle has joined #wot
15:09:18 <endo> endo has joined #wot
15:09:24 <Brent> Brent has joined #wot
15:09:25 <shiestyle> present+
15:09:39 <Brent> present+
15:12:23 <kdeangs1> kdeangs1 has joined #wot
15:12:35 <jiye> present+
15:12:56 <kdeangs1> present+
15:13:12 <kaz> q+
15:13:15 <kaz> ack f
15:13:16 <sebastian> q?
15:14:36 <kaz> topic: Scibe
15:14:47 <kaz> kaz: will do for the 1st part
15:15:04 <kaz> s/kaz: will do for the 1st part//
15:15:16 <kaz> Ben for the 1st part; Kaz for the 2nd part
15:15:27 <kaz> scribenick: benfrancis
15:15:40 <hfujisawa> hfujisawa has joined #wot
15:15:48 <kaz> i/Logistics/scribenick: kaz/
15:15:53 <kaz> rrsagent, make log public
15:15:58 <kaz> rrsagent, draft minutes
15:15:58 <RRSAgent> I have made the request to generate https://www.w3.org/2022/09/14-wot-minutes.html kaz
15:16:06 <kaz> topic: Overview
15:16:16 <kaz> -> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2022-09-hybrid-f2f/2022-09-14-WoT-Overview-McCool.pdf McCool's slides
15:16:35 <benfrancis1> McCool: The biggest problem with IoT is fragmentation
15:17:03 <kaz> i/The b/scribenick; benfrancis1/
15:17:10 <kaz> scribenick: benfrancis
15:17:17 <benfrancis> Thing Descriptions describe the network interface of a Thing, and some metadata. Currently working on Thing Description 1.1
15:17:51 <benfrancis> A TD is an information model, serialised as JSON-LD, which means it can be imported into a RDF database and queried with SPARQL
15:18:10 <benfrancis> You can import external ontologies (e.g. schema.org) to do things like units
15:18:16 <benfrancis> Things must have a Thing Description
15:18:38 <benfrancis> Not just HTTP, we can also describe CoAP and MQTT and are currently working on standards for others like OPC-UA
15:19:03 <benfrancis> Thing Description describes an abstraction based on properties, actions and events at a high level, then protocol bindings to tell a Consumer how to carry out those interactions over a protocol
15:19:26 <benfrancis> Provides an abstraction so in theory a Consumer does not need to worry about the details of a protocol
15:19:59 <benfrancis> One of the problems with discovery is privacy, so we use a two stage approach to discovery
15:20:06 <benfrancis> Introduction, then exploration
15:20:52 <benfrancis> The initial URL used in the introduction phase has no private information, then you do a GET on the URL, authenticate, and use a standard API for a web service to get metadata about devices
15:21:12 <benfrancis> When describing brownfield devices, the TD can come from somewhere else, the devices themselves don't need to support the Web of Things
15:21:45 <benfrancis> One thing we didn't get to is geolocation-based search, but we are trying to figure out a way to do it through extension mechanisms in the short term, then address it in the next version
15:22:08 <benfrancis> Orchestration - there is a scripting API with an implementation called node-wot through the Eclipse Foundation
15:22:48 <benfrancis> Deliverables. We are hoping to go into CR (candidate recommendation) for Architecture, TD and Discovery, with a vote on September 21st, right after TPAC
15:23:02 <benfrancis> Aiming for a resolution by the end of the year
15:23:17 <benfrancis> w3.org/WoT is a website which links to everything else
15:23:46 <benfrancis> Recent activity. We have done PlugFests, the last one was a couple of weeks ago reading for CR and PR transition.
15:24:11 <benfrancis> In good shape for implementations of discovery. Also working on IETF registrations for various things.
15:24:23 <benfrancis> Currently discussing the next charter. There are some proposals about what to do next.
15:24:52 <benfrancis> There has been a lot of interest in WoT for smart buildings - building information systems
15:25:43 <benfrancis> Siemens have a project with the Desigo CC  BIM, Takenaka Corporation have the CGLL platform, Bosch have the Ditto project
15:25:48 <sebastian> q?
15:25:59 <kaz> ack k
15:26:12 <benfrancis> This presentation is available on GitHub
15:26:30 <shiestyle> shiestyle has joined #wot
15:26:35 <David-Clarke> David-Clarke has joined #wot
15:26:59 <benfrancis> sebastian: We are currently finalising the charter which is running until the end of January. We are already designing a new charter and discussing the topics you would like to address. Use the chance to see what you would like to see in Web of Things "2.0".
15:27:35 <benfrancis> McCool: If you go to the wot repo you will see a bunch of PRs (pull requests), with a set of proposals.
15:28:46 <benfrancis> sebastian: We can go to the first talk about the Community Group. The CG has existed for almost 10 years, Cristiano and Ege have re-started this group and are the current chairs. I'd like to ask if they can provide an insight into this new group.
15:28:59 <endo> endo has joined #wot
15:29:30 <benfrancis> topic: WoT Community Group
15:30:04 <benfrancis> ege: Have changed from an incubation to an outreach activity. It may mean we have some conflicts with the WoT Interest Group, so need to work on a new setup.
15:30:27 <Ege> Ege has joined #wot
15:30:33 <kaz> i|Have|-> https://www.w3.org/2022/09/13-wot-cg-minutes.html Sep-13 WoT CG minutes|
15:30:33 <cris_> https://www.w3.org/events/meetings/05b36b01-51bf-4885-88ea-eac638159f71
15:30:34 <benfrancis> cris: We are organising an event a week from now. We are using the W3C calendar.
15:30:51 <dape> dape has joined #wot
15:30:56 <kaz> q+
15:31:11 <benfrancis> cris: We already had some new people attend, which is our first success.
15:31:32 <benfrancis> cris: We will have a presentation about the SIFIS Home project (European project)
15:31:46 <benfrancis> Philipp Blum will talk about building a community
15:32:02 <benfrancis> We want to process to be a democratic process
15:32:16 <benfrancis> ege: The event is next Thursday.
15:32:48 <benfrancis> ege: We had maybe 20 people join, quite a few people we haven't met before. Some people were expecting a summary of the Web of Things. We maybe should have prepared something.
15:33:09 <benfrancis> Specific interest for smart cities and digital twins
15:33:22 <benfrancis> We had an idea to have an initial brainstorming/ideas session which is focused on digital twins
15:33:39 <benfrancis> Maybe we should take smart cities more seriously
15:34:12 <benfrancis> After TPAC we will use the marketing call for discussions regarding the collaboration with the CG
15:34:21 <benfrancis> Feel free to join the marketing calls on Tuesdays
15:34:25 <sebastian> q+
15:34:30 <kaz> ack k
15:34:36 <kaz> q+
15:34:36 <benfrancis> cris: We can jumpstart some discussion right now?
15:34:44 <McCool> q?
15:34:51 <McCool> ack s
15:35:16 <benfrancis> sebastian: Maybe you can talk about the web page, tooling, spaces for people who are interested in latest news and so on
15:35:25 <shiestyle> shiestyle has joined #wot
15:36:10 <dezell> dezell has joined #wot
15:36:15 <benfrancis> Ege: Here you can see the Web of Things web page. You can find information about the Web of Things Working Group activities, events.
15:36:18 <dezell> present+ David_Ezell
15:36:35 <kaz> present+ Jan_Roann
15:36:53 <benfrancis> There is a developers section for people outside our activities with a variety of tools and software packages that have specific purposes. WoT is an open standard not a framework.
15:36:54 <kaz> present+ Daniel_Peintner
15:37:08 <benfrancis> We have learnt that the documentation page is the most popular page. Provides an introduction to the Web of Things.
15:37:11 <kaz> present+ David_Clarke
15:37:27 <kaz> present+ Shinjiro_Urata
15:37:46 <kaz> present_ Sunghyun_Yoon, Mun-Hwan_Choi
15:37:53 <benfrancis> There is a videos section with some introductory videos, in-depth tutorials, results of previous meetings
15:37:53 <kaz> q?
15:38:10 <benfrancis> You can find us on GitHub and Twitter
15:38:24 <dape> present+ Daniel_Peintner
15:38:26 <McCool> q+
15:38:34 <McCool> ack k
15:38:43 <benfrancis> kaz: I am very concerned about the mixing up of Marketing work and WoT CG work. What is your rationale?
15:39:01 <benfrancis> Ege: We will discuss this in the Marketing call.
15:39:22 <benfrancis> kaz: You are saying you would like to transfer the marketing activity to the WoT CG group? What is your rationale?
15:40:26 <cris_> qq
15:40:33 <benfrancis> McCool: There are a lot of activities under the IG that we probably want to transfer to the CG. We have a timeslot where we do this, proposing we replace that timeslot with a CG call. If we have a marketing task force call and it's actually an IG call then that's fine but it's an IG meeting. Shouldn't have a call that is both because it's confusing
15:40:33 <benfrancis> from the point of view of the patent policy.
15:40:48 <benfrancis> Ege: The marketing call is not a CG call.
15:41:06 <sebastian> q+
15:41:12 <benfrancis> McCool: In the future when we set an IG call, let's not use the marketing task force time slot. Let's be clear that it's a marketing task force call or a CG call, it can't be both.
15:41:24 <benfrancis> Ege: It is an IG marketing call, there is no regular CG call.
15:41:46 <benfrancis> kaz: We have been holding an IG marketing call regularly. You would like to invite CG people to that call regularly. That is a problem.
15:42:13 <surata> surata has joined #wot
15:42:39 <benfrancis> cris: Probably a misunderstanding. We are not going to have this mixed call. We will have discussions separately, then when the time comes we will connect together.
15:42:49 <benfrancis> kaz: When and who will organise what meeting and talk about what topics?
15:43:19 <benfrancis> Ege: IG organises the marketing call, IG members can come to that call to discuss what they are OK with giving to the CG. Once there's an agreement that can be passed to the CG.
15:43:33 <benfrancis> kaz: You are expecting that the IG would like to transfer deliverables to the CG.
15:43:42 <benfrancis> Ege: The marketing task force has no deliverables.
15:44:08 <benfrancis> McCool: We are running out of time. The IG needs to discuss this on the IG call. Only IG members will be attending.
15:44:27 <benfrancis> kaz: Please have internal discussions within the CG group separately and clarify the expectations of participants first.
15:44:35 <benfrancis> McCool: I think we agree.
15:45:08 <benfrancis> kaz: Do they want to work for the IG task force instead? If so, please discuss that point with them.
15:45:26 <benfrancis> kaz: We need to clarify the relationship between the IG and CG.
15:45:37 <benfrancis> Ege: I agree.
15:45:48 <benfrancis> kaz: You have not been doing any discussion about deliverables on the CG side?
15:45:51 <Mizushima> +1 kaz
15:46:39 <benfrancis> sebastian: I am surprised by this discussion. The CG has a charter definition which clearly states the scope. Perhaps the confusion is that we see the same people active in the CG, IG and WG. Perhaps there is some confusion regarding which group you are acting under.
15:46:43 <McCool>               q?
15:46:56 <McCool> (we really need to move on with the agenda)
15:47:07 <McCool> q?
15:47:10 <McCool> ack m
15:47:31 <benfrancis> sebastian: I think we should be careful about what we are considering. When I was active in the marketing task force, we agreed that it is complicated to be isolated only within the WG because we receive a lot of input from people not in the IG.
15:48:13 <benfrancis> Sometimes there are touch points between CG and IG marketing. In my understanding there are separate CG meetings for people who are not members of the IG and are not invited to the marketing call.
15:48:14 <McCool> s/I think we agree/I think we are in violent agreement/
15:48:33 <McCool> ack s
15:48:37 <McCool> q+
15:48:55 <benfrancis> kaz: We carefully removed mixing up from the community group charter, but that mixture has started again.
15:49:07 <McCool> ack m
15:49:33 <benfrancis> sebastian: Next is Tomoaki-san who will talk about the Japanese CG
15:49:41 <benfrancis> Yes please kaz
15:49:43 <kaz> scribenick: kaz
15:49:56 <kaz> topic: WoT Japanese CG
15:49:59 <kaz> @@@ slides
15:50:10 <kaz> mizu: will introduce the activity
15:50:18 <kaz> ... [slide 2]
15:50:25 <kaz> ... Web of THings (WoT)
15:50:40 <kaz> ... (gives basic overview of WoT in general)
15:50:45 <kaz> ... [slide 3]
15:50:52 <kaz> s/TH/Th/
15:51:05 <kaz> ... Our expectation for the future society using WoT
15:51:06 <McCool> (actually, my apologies, it seems we still had a lot of time in the agenda.  However, while I do think we need to resolve this, I don't think we should spend 15m on this issue right now)
15:51:36 <kaz> (agree; and would suggest we continue the discussion carefully)
15:51:58 <kaz> mizu: would like to promote WoT in Japan
15:52:03 <kaz> ... 4 goals here
15:52:15 <kaz> ... outreach, deployment, use cases and translation
15:52:48 <kaz> ... [slide 5]
15:53:06 <kaz> ... 4 TFs to achieve the goals
15:53:10 <kaz> ... [slide 6]
15:53:14 <kaz> ... Outreach TF
15:53:26 <kaz> ... promote WoT in the JP industry
15:53:48 <kaz> ... organized 5 events
15:54:14 <kaz> ... kickoff, demo, ECHONET collaboration, use cases, smart buildings
15:54:51 <kaz> i/4 goals here/... [slide 4]/
15:54:58 <kaz> ... [slide 7]
15:55:02 <kaz> ... Deployment TF
15:55:10 <kaz> ... to provide guidelines and manuals
15:55:25 <kaz> ... generating a portal site
15:55:31 <kaz> ... [slide 8]
15:55:37 <kaz> ... Translation TF
15:55:55 <kaz> ... Japanese localization
15:56:10 <kaz> ... WoT Architecture 1.0 done and transferred to TTC
15:56:24 <kaz> ... [slide 9]
15:56:29 <kaz> ... Use Cases TF
15:56:41 <kaz> ... colect industrial us cases
15:57:11 <kaz> ... upcoming events: hackathon, ideathon
15:57:16 <kaz> ... [slide 10]
15:57:21 <kaz> ... SDO collaboration
15:57:36 <kaz> ... introduce and discuss the availability of WoT
15:57:47 <kaz> ... EHONET, IPA DADC, IEC SC3D
15:57:54 <kaz> s/EHO/ECHO/
15:58:08 <kaz> ... smart home, smart buildings, IoT vocabulary
15:58:15 <kaz> ... [slide 11]
15:58:26 <kaz> ... Relationship with WoT-WG/IG
15:58:42 <kaz> ... cooperation via information exchange
15:58:45 <McCool> q+
15:59:03 <kaz> mm: slides are available on GitHub
15:59:20 <kaz> ... question on translation
15:59:28 <kaz> ... 1.1 version?
15:59:44 <kaz> mizu: planning to work on them as well
15:59:48 <kaz> ... so far working on 1.0
16:00:01 <kaz> mm: wondering about the timing
16:00:09 <dape> q+
16:00:15 <kaz> ... it takes a lot of time to translate the specs
16:00:28 <kaz> ... would assume you work on 1.1 versions as well
16:00:32 <kaz> ... maybe post PR
16:00:45 <kaz> ack m
16:00:46 <kaz> ack d
16:00:52 <kaz> dape: similar question
16:01:08 <kaz> ... going to automatic?
16:01:18 <kaz> ... or translate chapter by chapter?
16:01:19 <kaz> q+
16:01:35 <kaz> mizu: automatic translation is nice
16:01:48 <kaz> ... but unfortunately, there are still problems
16:01:55 <kaz> ... so we need to review it
16:02:15 <sebastian> ack k
16:02:48 <kaz> kaz: helped them work on the translation
16:02:51 <Mizushima> ?
16:03:13 <kaz> ... actually, there was a nice translation generated by a great translater, Kamitsuna-san
16:03:19 <McCool> (ege, can you check in slides on github)
16:03:25 <kaz> ... they used it as the basis
16:03:30 <kaz> rrsagent, draft minutes
16:03:30 <RRSAgent> I have made the request to generate https://www.w3.org/2022/09/14-wot-minutes.html kaz
16:04:24 <Ege> the link for the CG presentation: https://docs.google.com/presentation/d/1jTlSKw7VfIx5J2degldyugGwJFjxPZ_p/edit?usp=sharing&ouid=106655031772979203612&rtpof=true&sd=true
16:05:03 <Mizushima> s/@@@ slides/-> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2022-09-hybrid-f2f/2022-09-14-WoT-F2F-WoT-JP-CG-Mizushima.pdf WoT-JP CG slide
16:10:26 <Ege> mccool the slides as pdf are uploaded to GitHub
16:10:27 <Ege> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2022-09-hybrid-f2f/2022-09-13-WoT-CG-TPAC.pdf
16:10:56 <kaz> topic: TPAC Brakouts
16:11:01 <kaz> subtopic: WoT Demo
16:11:35 <kaz> present+ Michael_Lagally
16:12:10 <kaz> mm: WoT demo breakout will be at 3:00pm-4:00pm
16:12:25 <kaz> ... Smart Cities breakout will be at 4:30pm-5:30pm
16:13:03 <kaz> ... McCool and Ezell to show retail, home assistance integration
16:13:33 <kaz> -> https://www.w3.org/2022/Talks/0914-smartcities-ka/20220914-dt-sc-ka.pdf Kaz's slides
16:14:01 <bkardell_> bkardell_ has joined #wot
16:14:01 <kaz> s/slides/subtopic: Smart Cities/
16:14:02 <mlagally> mlagally has joined #wot
16:15:30 <benfrancis> kaz: A presentation about smart cities and how to proceed. Discusses ECHONET
16:15:53 <benfrancis> ISO/IEC JTC1
16:16:13 <benfrancis> IEC SC3D
16:16:19 <benfrancis> IPA DADC
16:16:31 <benfrancis> ITU-T SG20
16:16:36 <benfrancis> OGC
16:16:56 <benfrancis> W3C
16:17:27 <benfrancis> What is still missing for smart cities, next steps
16:17:32 <McCool>      q+
16:17:57 <benfrancis> Smart cities is a large topic, maybe start with web-based digital twins
16:18:33 <benfrancis> McCool: Have discussed a smart cities IG. Kaz is suggesting we narrow it and talk about digital twins. Digital twins are also a big topic. SDOs we need to work with. Tabled for the next charter, but not decided.
16:19:48 <benfrancis> Digital twins. One aspect is physical metadata. Right now we have a lot of metadata about the network interface, but not much about the physical thing. E.g. location, user interface. Things you care about for a digital twin. Have been talking to accessibility group. May want to annotate a digital twin, translate into different sensory modalities.
16:19:48 <benfrancis> TD doesn't currently talk about the physical interface.
16:20:35 <benfrancis> kaz: What is missing.... Guidelines for real world engineering, data transfer and distribution
16:20:52 <benfrancis> kaz: W3C as a central hub for collaborative discussion
16:21:12 <benfrancis> McCool: Complicated. I can think of another half dozen organisations not on this list. So many organisations.
16:21:41 <kaz> q?
16:21:45 <kaz> ack m
16:22:26 <benfrancis> mlagally: We see all the SDOs on this list, there are already many of those. Need to start working on focused use cases. Don't think complete twin of a city down to a smart home will be a requirement, need a focused discussion. May be some additional work required here.
16:22:35 <benfrancis> q+
16:22:54 <benfrancis> McCool: Geolocation comes up a lot
16:23:54 <benfrancis> McCool: Need workshops to explore use cases. Workshops we've had have had very few attendees from actual cities. Need them to tell us what their use cases are.
16:24:05 <benfrancis> mlagally: We already have some use cases
16:24:20 <benfrancis> McCool: I think there will be many more. One target of the group is to generate a use cases document to identify gaps.
16:24:37 <kaz> ack b
16:25:04 <kaz> ben: people treating digital twins differently
16:25:44 <benfrancis> q?
16:26:07 <kaz> ml: we have looked into several kinds of meta data
16:26:32 <McCool> q+
16:26:33 <kaz> ... go into individual approach by those SDOs is important
16:26:57 <kaz> ... possible requirements for TD and Profile, etc.
16:27:00 <mlagally> mlagally has joined #wot
16:27:14 <kaz> mm: we've started to talk with Microsoft DTDL as well
16:27:15 <mlagally> zakim, who is on the call?
16:27:15 <Zakim> Present: Kaz_Ashimura, Shinya_Takami, Michael_McCool, Sebastian_Kaebisch, Javad, Kevin_Dean, Kawada, Brent, Ben_Francis, Hiroki_Endo, Christian_Glomb, Kunihiko_Toumura, Jiye_Park,
16:27:18 <Zakim> ... Motoki_Mizusako, Tomoaki_Mizushima, Richard_Worth, Geunhyung_Kim, Seukyoon_Kang, Cristiano_Aguzzi, Bradley_Needham, Hiroshi_Fujisawa, Kinji_Matsumura, Geun-Hyung_Kim,
16:27:18 <Zakim> ... Hiroshi_Kawada, shiestyle, jiye, kdeangs, David_Ezell, Jan_Roann, Daniel_Peintner, David_Clarke, Shinjiro_Urata, Michael_Lagally
16:27:40 <kaz> ... need to think about how to satisfy the gaps in this area
16:27:45 <McCool> ack m
16:29:22 <benfrancis> q+
16:29:32 <benfrancis> q-
16:30:52 <kaz> mm: fyi, there will joint discussion on RDF canonicalization
16:31:04 <kaz> brent: will have joint discussion with them
16:31:32 <kaz> s/canonicalization/canonicalization on Friday, Sep. 16/
16:32:13 <kaz> topic: AOB
16:32:25 <kaz> mm: voice integration for accessibility purposes
16:32:50 <kaz> ... home assistance integration to be shown during the breakout session
16:33:00 <kaz> ... e.g., Google Home
16:33:11 <kaz> q+
16:33:27 <benfrancis> q+
16:33:40 <discjock> discjock has joined #wot
16:33:47 <discjock> 💨Don’t miss this chance to be Rich... (full message at <https://matrix.org/_matrix/media/r0/download/matrix.org/uEizNYZCjXipImqnYCoNuAey>)
16:34:20 <kaz> kaz: we should consider those existing mechanisms in addition to the SDO collaboration
16:34:24 <kaz> q?
16:34:27 <kaz> ack k
16:34:42 <kaz> ack b
16:35:04 <kaz> ben: the Web Thing CG will have a meeting tomorrow, Sep 15
16:35:15 <kaz> ... 8-10am PDT
16:35:31 <benfrancis> https://www.w3.org/events/meetings/c7ce6c53-6436-4c09-91c9-97ec01ffe7f3
16:35:53 <benfrancis> Correction: 08:30 - 10:30 PDT
16:35:54 <kaz> topic: DID and VC
16:36:12 <kaz> mm: (shows Kaz's smart cities slides including WoT+DID+VC)
16:36:33 <kaz> ... possible resolution mechanism via DID
16:36:55 <kaz> ... VC will meet on Friday
16:37:11 <kaz> ... TD signing for the next WoT Charter
16:37:20 <kaz> manu: sounds great
16:37:33 <shiestyle> shiestyle has joined #wot
16:37:34 <kaz> ... we have Brent as the WG Chair as well
16:37:55 <kaz> ... using DID for identifying IoT devices would make sense
16:38:02 <kaz> ... could be small binary data
16:38:21 <McCool> q+
16:38:29 <kaz> ... DID key has been expressed as public key
16:38:42 <shiestyle> shiestyle has joined #wot
16:38:57 <shiestyl_> shiestyl_ has joined #wot
16:38:58 <kaz> ... some basic version of encryption, e.g., 64-bit or 256-bit
16:39:26 <kaz> ... as either a primary identifier or a secondary identifier
16:39:56 <kaz> mm: one possible solution for the identifier for IoT purposes
16:40:19 <kaz> ... a typical question with home IoT
16:40:32 <kaz> .... need some kind of standardized mechanism
16:41:05 <kaz> manu: have your had discussion on identification of valid devices?
16:41:12 <kaz> mm: the issue is
16:41:20 <kaz> ... need process to list
16:41:35 <kaz> ... issue about onboarding is on the list
16:41:53 <kaz> ... OPC UA device is one think
16:41:56 <kaz> s/think/thing/
16:42:18 <kaz> ... get back to the challenge of the current DID mechanism
16:42:24 <kaz> ... so many DID methods there
16:42:33 <kaz> ... think about requirements first
16:42:51 <kaz> ... or starting with methods?
16:43:05 <kaz> manu: DID holding rechartering discussion
16:43:25 <kaz> brent: DID Rubric
16:43:32 <kaz> ... trying registry of DIDs
16:43:48 <kaz> ... as a mean of using different DID methods based on the need
16:44:09 <kaz> ... looking at the possibility of standardization for specific DID methods
16:44:23 <kaz> ... end-to-end DID-based mechanism
16:44:53 <kaz> ... related discussion by did.com on IoT purposes
16:44:58 <sebastian> q?
16:45:17 <kaz> mm: we're discussing minimum size of IoT devices
16:45:24 <kaz> ... minimum functionality and cost
16:45:30 <hfujisaw_> hfujisaw_ has joined #wot
16:45:44 <kaz> ... also there is an immerging standard named Matter
16:46:00 <Geun-Hyung_Kim> s/did.com/DIDComm
16:46:35 <kaz> manu: speaking to payload sizes
16:47:02 <McCool> q?
16:47:02 <kaz> ... discussion on minimize the data size, e.g., using CBOR
16:47:14 <kaz> ... includes digital signature
16:47:34 <kaz> ... another set of work done as well
16:47:44 <kaz> ... canonicalization template
16:48:01 <kaz> ... inject data into the message
16:48:16 <Geun-Hyung_Kim> s /CBOR/CBOR-LD
16:48:20 <kaz> ... their mechanism to reduce the memory footpoint
16:48:43 <kaz> mm: we're discussing an alternative data format than TD
16:48:55 <kaz> ... CBOR is an option
16:49:05 <kaz> ... also template for TD
16:49:17 <kaz> ... that is Thing Model (TM)
16:49:45 <kaz> manu: hash linking, etc., has been discussed as well
16:49:58 <kaz> mm: the other point is canonicalization
16:50:16 <kaz> s/zation/zation of the HASH tag/
16:50:40 <kaz> manu: from the privacy viewpoint
16:51:14 <kaz> ... the best practice is downloading the cache
16:51:28 <kaz> mm: meant to be open for WoT
16:51:49 <kaz> ... downloading the cache would be good for the proxy
16:52:05 <kaz> manu: particular use cases for that purpose
16:52:13 <kaz> ... another point on canonicalization
16:52:20 <McCool> q?
16:52:25 <kaz> ... working on data integrity
16:52:39 <kaz> ... use different canonicalization algorithm
16:52:45 <kaz> ... using JCS
16:53:13 <kaz> ... if you want to, you can define your own canonicalization algorithm
16:54:25 <kaz> mm: one issue is generation of HASH
16:54:46 <kaz> ... what if you have CBOR or YAML serialization
16:55:10 <McCool> q?
16:55:22 <kaz> manu: should think about what might be the best use cases
16:55:30 <kaz> q?
16:55:33 <kaz> ack m
16:55:38 <McCool> ack m
16:56:04 <kaz> ml: if we WoT want to go VC and JCS, what would be the time frame?
16:56:26 <kaz> manu: would not be difficult to integrate JCS algorithm
16:56:33 <kaz> q+
16:57:04 <kaz> kaz: would suggest we continue collaborative discussions
16:57:12 <kaz> mm: yeah, let's continue offline discussions
16:57:15 <kaz> ack k
16:57:26 <kaz> present+ Manu_Sporny
16:57:31 <kaz> rrsagent, draft minutes
16:57:31 <RRSAgent> I have made the request to generate https://www.w3.org/2022/09/14-wot-minutes.html kaz
16:57:42 <kaz> rrsagent, make log puclic
16:58:01 <kaz> rrsagent, make log public
16:58:10 <kaz> topic: Post-TPAC meeting
16:58:30 <kaz> sk: we'll continue discussion next week as the Post-TPAC meeting
16:58:32 <Geun-Hyung_Kim> present+
16:58:46 <bneedham> bneedham has left #wot
17:07:36 <stevelee> stevelee has joined #wot
17:18:36 <kaz> [adjourned]
17:18:44 <kaz> rrsagent, draft minutes
17:18:44 <RRSAgent> I have made the request to generate https://www.w3.org/2022/09/14-wot-minutes.html kaz
18:07:29 <kaz> kaz has joined #wot
18:27:53 <shiestyle> shiestyle has joined #wot
18:37:40 <shiestyle> shiestyle has joined #wot
18:38:09 <stevelee> stevelee has joined #wot
19:07:44 <shiestyle> shiestyle has joined #wot
19:15:31 <Zakim> Zakim has left #wot
20:18:20 <shiestyle> shiestyle has joined #wot
21:35:14 <kaz> kaz has joined #wot
21:53:07 <kaz> kaz has joined #wot
22:00:01 <bneedham> bneedham has joined #wot
22:01:04 <bneedham> bneedham has left #wot
22:02:17 <dezell> dezell has joined #wot
22:05:48 <javadch> javadch has joined #wot
22:06:02 <javadch> javadch has left #wot
22:07:01 <ogawa> ogawa has joined #wot