IRC log of wot on 2021-10-27
Timestamps are in UTC.
- 00:00:29 [dsr]
- dsr has joined #wot
- 01:01:23 [dsr]
- dsr has joined #wot
- 02:02:12 [dsr]
- dsr has joined #wot
- 03:02:49 [dsr]
- dsr has joined #wot
- 03:33:34 [kaz]
- kaz has joined #wot
- 04:03:36 [dsr]
- dsr has joined #wot
- 04:58:34 [kaz]
- kaz has joined #wot
- 04:59:03 [kaz]
- kaz has joined #wot
- 05:04:30 [dsr]
- dsr has joined #wot
- 06:00:23 [dsr]
- dsr has joined #wot
- 07:03:21 [zkis_]
- zkis_ has joined #wot
- 08:55:46 [stevelee]
- stevelee has joined #wot
- 09:21:50 [pchampin]
- pchampin has joined #wot
- 11:36:41 [zkis_]
- zkis_ has joined #wot
- 11:52:49 [kaz]
- rrsagent, bye
- 11:52:49 [RRSAgent]
- I see no action items
- 11:52:55 [RRSAgent]
- RRSAgent has joined #wot
- 11:52:55 [RRSAgent]
- logging to https://www.w3.org/2021/10/27-wot-irc
- 11:53:07 [kaz]
- meeting: WoT vF2F in October - Day 4
- 11:53:13 [kaz]
- present+ Kaz_Ashimura
- 11:57:04 [kaz]
- rrsagent, make log public
- 11:57:11 [kaz]
- rrsagent, draft minutes
- 11:57:11 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/27-wot-minutes.html kaz
- 11:58:13 [kaz]
- chair: Sebastian, McCool
- 11:58:36 [takio]
- takio has joined #wot
- 11:59:05 [McCool]
- McCool has joined #wot
- 11:59:53 [Tomoaki_MIzushima]
- Tomoaki_MIzushima has joined #wot
- 12:00:11 [kaz]
- present+ Michael_McCool, Takio_Yamaoka
- 12:00:37 [kaz]
- present+ Peter_Bruhn_Andersen
- 12:01:03 [kaz]
- -> https://www.w3.org/Consortium/Patent-Policy-20170801/ W3C Patent Policy
- 12:01:24 [kaz]
- present+ Michael_Lagally
- 12:01:35 [kaz]
- present+ Kunihiko_Toumura
- 12:01:57 [ktoumura]
- ktoumura has joined #wot
- 12:03:05 [Ege]
- Ege has joined #wot
- 12:03:12 [kaz]
- present+ Fady_Salama
- 12:03:18 [mlagally]
- mlagally has joined #wot
- 12:03:25 [kaz]
- present+ Ege_Korkan
- 12:03:27 [fady]
- fady has joined #wot
- 12:03:32 [kaz]
- present+ Ari_Keranen
- 12:03:39 [dape]
- dape has joined #wot
- 12:03:42 [kaz]
- present+ Daniel_Peintner
- 12:03:43 [Fady_]
- Fady_ has joined #wot
- 12:03:53 [kaz]
- zakim, who is on the call?
- 12:03:53 [Zakim]
- Present: Kaz_Ashimura, Michael_McCool, Takio_Yamaoka, Peter_Bruhn_Andersen, Michael_Lagally, Kunihiko_Toumura, Fady_Salama, Ege_Korkan, Ari_Keranen, Daniel_Peintner
- 12:04:12 [kaz]
- present+ Tomoaki_Mizushima
- 12:04:20 [kaz]
- present+ Sebastian_Kaebisch
- 12:04:32 [sebastian]
- sebastian has joined #wot
- 12:04:51 [kaz]
- present+ Albrecht_Schwarz
- 12:05:33 [kaz]
- present+ Cristiano_Aguzzi
- 12:06:19 [kaz]
- topic: Agenda
- 12:07:37 [kaz]
- -> https://www.w3.org/WoT/IG/wiki/F2F_meeting,_October_2021#Oct_27 Oct-27
- 12:07:45 [kaz]
- @@@Sebastian's slides
- 12:08:35 [kaz]
- s|@@@Sebastian's slides|-> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2021-10-online-f2f/2021-10-27-WoT-F2F-Opening-Kaebisch.pdf Sebastian's slides|
- 12:09:10 [kaz]
- sk: scribe: Sebastian and @@@
- 12:09:14 [kaz]
- present+ Michael_Koster
- 12:09:21 [Ege]
- me, daniel, fady took minutes
- 12:09:28 [kaz]
- s/@@@/Cristiano/
- 12:09:33 [mjk]
- mjk has joined #wot
- 12:10:10 [kaz]
- sk: Architeture, Profile, (break), Scripting API, Marketing and Wrap-up
- 12:10:15 [kaz]
- ... any guest today?
- 12:10:32 [kaz]
- as: Albrecht Schwarz
- 12:10:43 [kaz]
- -> https://www.w3.org/Consortium/Patent-Policy-20170801/ W3C Patent Policy
- 12:10:45 [kaz]
- q+
- 12:11:40 [kaz]
- sk: please be aware of the W3C Patent Policy
- 12:12:00 [kaz]
- ... note that everything will be published publicly
- 12:12:18 [kaz]
- ... so confidential information should not be shared during this call
- 12:12:25 [kaz]
- as: agree
- 12:13:04 [kaz]
- ack k
- 12:13:09 [kaz]
- sk: next
- 12:13:17 [kaz]
- ... we're using IRC for taking notes
- 12:13:43 [kaz]
- ... also use q+ / q- to manage the speaker queue
- 12:13:55 [kaz]
- q+ ka
- 12:13:58 [kaz]
- q- ka
- 12:14:10 [kaz]
- ... resources
- 12:14:34 [kaz]
- ... wiki page here https://www.w3.org/WoT/IG/wiki/F2F_meeting,_October_2021
- 12:14:52 [kaz]
- ... presentations available at https://github.com/w3c/wot/tree/main/PRESENTATIONS/2021-10-online-f2f
- 12:14:55 [sebastian]
- q?
- 12:15:10 [kaz]
- ... and then would like Lagally to take over the moderator role
- 12:15:22 [kaz]
- scribenick: sebastian
- 12:15:35 [kaz]
- topic: Architecture and Profiles
- 12:16:05 [PeterAndersen]
- PeterAndersen has joined #wot
- 12:16:30 [kaz]
- @@@ Lagally's slides
- 12:16:53 [kaz]
- present+ Ryuichi_Matsukura, Zoltan_Kis
- 12:17:45 [sebastian]
- ML: shows the agenda for architecture and profile
- 12:18:34 [sebastian]
- ... architecture is responsible for the abstract architecture and interoperabiity profiles for WoT
- 12:18:59 [sebastian]
- ... thanks to the contributors of the Arch and Profile document
- 12:20:35 [sebastian]
- ... Arch specifies the abstract architecture, terminology and building blocks of WoT
- 12:21:05 [kaz]
- present+ Takashi_Minamii
- 12:21:22 [ryuichii]
- ryuichii has joined #wot
- 12:21:23 [sebastian]
- ... <shows toc of Arch document>
- 12:21:35 [tm]
- tm has joined #wot
- 12:21:44 [kaz]
- rrsagent, draft minutes
- 12:21:44 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/27-wot-minutes.html kaz
- 12:22:20 [sebastian]
- ... <shows toc of Profile document>
- 12:22:40 [kaz]
- i/Sebastian and Cristiano/scribenick: kaz/
- 12:22:42 [kaz]
- rrsagent, draft minutes
- 12:22:42 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/27-wot-minutes.html kaz
- 12:22:57 [McCool]
- (it occurs to me that if these are just ed drafts, we need to have a FPWD by Jan 13!)
- 12:23:02 [sebastian]
- ML: lets go to the Arch. document
- 12:23:23 [sebastian]
- ... currently working on terminology alignment
- 12:24:45 [sebastian]
- ... some specifications have their own terminology section, need to align and move common definitions to architecture
- 12:24:55 [sebastian]
- q+
- 12:25:07 [Ege]
- sorry for skipping the queue sebastian
- 12:25:17 [sebastian]
- no problem
- 12:25:32 [Ege]
- q+
- 12:25:35 [kaz]
- ack s
- 12:25:39 [McCool]
- q+
- 12:25:49 [kaz]
- sk: we had similar discussion before
- 12:26:28 [kaz]
- ... we made the terminology section informative
- 12:26:36 [kaz]
- q+
- 12:26:40 [kaz]
- q-
- 12:26:41 [kaz]
- qq+
- 12:27:15 [sebastian]
- I remember that PHL recommended to have terminology non-normative, however, I cannot remember what was the reason
- 12:27:51 [mjk]
- q?
- 12:27:56 [kaz]
- ack k
- 12:27:56 [Zakim]
- kaz, you wanted to react to sebastian
- 12:28:16 [sebastian]
- Kaz: Terminology section have no nomative assertions. Personally I do not see the motivation to make it normative
- 12:28:31 [kaz]
- q?
- 12:28:33 [kaz]
- ack e
- 12:28:53 [kaz]
- qq+
- 12:29:39 [McCool]
- (I plan to mention the schedule constraint; we need to do all FPWD's by Nov 25 to hit CR by March 17)
- 12:29:58 [kaz]
- ack k
- 12:29:58 [Zakim]
- kaz, you wanted to react to Ege
- 12:30:25 [kaz]
- ack m
- 12:30:26 [sebastian]
- Ege: If the termonology section is normative, it does not prevent disalignment.
- 12:31:27 [sebastian]
- ML: thats right
- 12:31:38 [sebastian]
- MM: I do not have a hard opionen of that.
- 12:31:45 [kaz]
- i/I do not/kaz: yeah, so from my viewpoint, what is important is not whether the terminology is normative or not, but the alignment itself/
- 12:31:51 [kaz]
- q?
- 12:32:03 [dezell]
- dezell has joined #wot
- 12:32:14 [dezell]
- present+ David_Ezell
- 12:32:18 [McCool]
- (never mind, it seems both Arch and Profiles have had FPWDs already)
- 12:32:23 [sebastian]
- ML: another work is on protocol bindings
- 12:33:05 [kaz]
- present+ Jennifer_Strickland
- 12:33:06 [sebastian]
- ... introduction section needs an update
- 12:33:52 [sebastian]
- ... there also some places with editorial notes that announce additional content
- 12:34:16 [kaz]
- rrsagent, draft minutes
- 12:34:16 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/27-wot-minutes.html kaz
- 12:34:22 [sebastian]
- ML: next steps would to work on implementation report, ...
- 12:34:39 [kaz]
- s/would/would be/
- 12:35:24 [sebastian]
- ML: regarding publication schedule it is planned to dreeze the features Jan 31, 2022
- 12:35:36 [sebastian]
- s/dreeze/freeze
- 12:35:37 [kaz]
- present+ Tomoya_Asai
- 12:35:55 [sebastian]
- ... we expect to have the charter extension
- 12:35:57 [kaz]
- q?
- 12:36:12 [sebastian]
- MK: thats about the architecture TF
- 12:36:33 [kaz]
- s/MK:/ML:/
- 12:37:01 [kaz]
- q?
- 12:37:06 [sebastian]
- kaz thanks
- 12:37:12 [McCool]
- q+
- 12:37:28 [sebastian]
- ack m
- 12:38:04 [kaz]
- q?
- 12:38:15 [sebastian]
- MM: we should focus on Profile
- 12:38:49 [sebastian]
- ML: <gives an overview of the open issues in the Arch repo>
- 12:39:11 [sebastian]
- https://github.com/w3c/wot-architecture/issues
- 12:40:29 [kaz]
- q+
- 12:40:36 [sebastian]
- ML: we need to take care on accessibility
- 12:40:46 [sebastian]
- its important when it comes to TAG review
- 12:41:00 [sebastian]
- MM: we should be also check internationalization
- 12:41:20 [sebastian]
- s/be/
- 12:42:15 [sebastian]
- ML: I will create a issue that take care of it
- 12:42:44 [kaz]
- -> https://www.w3.org/Guide/documentreview/ How to do Wide Review
- 12:43:20 [sebastian]
- Kaz: there is a guideline about the document review. We should follow it
- 12:43:50 [kaz]
- q?
- 12:43:52 [kaz]
- ack k
- 12:44:58 [sebastian]
- ML: <creates an issue about group wide review>
- 12:45:31 [sebastian]
- topic: WoT Profile
- 12:45:45 [sebastian]
- ML: what is a WoT Profile?
- 12:46:10 [sebastian]
- ... normative subset of WoT TD with a normative binding
- 12:47:39 [sebastian]
- ... <shows some drawings in the slides>
- 12:48:07 [sebastian]
- q+
- 12:49:08 [kaz]
- s/topic: Architecture and Profiles/topic: Architecture/
- 12:49:17 [kaz]
- rrsagent, draft minutes
- 12:49:17 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/27-wot-minutes.html kaz
- 12:49:36 [sebastian]
- just for clearification: profile do not develop specific binding like http, it simple reuse existing definition
- 12:49:51 [sebastian]
- s/definition/definitions
- 12:50:20 [sebastian]
- ML: <shows use cases as drawing>
- 12:54:11 [Ege]
- q+
- 12:54:12 [sebastian]
- ... important use case is the "out of the box interoperability" use case
- 12:54:18 [sebastian]
- ack s
- 12:54:19 [sebastian]
- ack e
- 12:54:39 [kaz]
- q+
- 12:54:40 [McCool]
- q+
- 12:55:36 [sebastian]
- Ege: there is a problem with the "out of the box interoperability", even http is not interoperability since everyone can use in own style
- 12:55:51 [sebastian]
- s/use/use it
- 12:56:01 [kaz]
- s/not interoperability/not interoperable/
- 12:57:17 [kaz]
- q?
- 12:58:48 [sebastian]
- q+
- 12:58:48 [kaz]
- ack m
- 12:59:39 [sebastian]
- q-
- 13:00:10 [kaz]
- present+ Leigh_Anne_Mazure
- 13:00:16 [Ege]
- ack e
- 13:01:49 [sebastian]
- Kaz: W3C does not provide a certification for interoperability.
- 13:03:27 [kaz]
- s/interoperability./interoperability, but we can and should explain what is expected for WoT interoperability./
- 13:03:36 [sebastian]
- ... we can provide a minimum set of requriments
- 13:03:40 [kaz]
- q?
- 13:03:47 [kaz]
- ack k
- 13:03:53 [bkardell_]
- bkardell_ has joined #wot
- 13:04:59 [kaz]
- s/requirements/requirements. Also from my viewpoint, what kind of vocabulary to be used for what kind of industry area is another important point for interoperability./
- 13:05:11 [kaz]
- present+ Riaz_Aimandi
- 13:05:47 [kaz]
- rrsagent, draft minutes
- 13:05:47 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/27-wot-minutes.html kaz
- 13:06:01 [sebastian]
- ML: There are some core requirements such as for data model and protocol binding
- 13:06:32 [kaz]
- s/requriments/requirements. Also from my viewpoint, what kind of vocabulary to be used for what kind of industry area is another important point for interoperability./
- 13:06:33 [kaz]
- rrsagent, draft minutes
- 13:06:33 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/27-wot-minutes.html kaz
- 13:09:05 [sebastian]
- q+
- 13:09:45 [kaz]
- ack s
- 13:10:50 [sebastian]
- there is not a 'common' data model
- 13:11:08 [sebastian]
- ML: right, I will change this to 'restricted'
- 13:11:26 [McCool]
- q+
- 13:12:25 [sebastian]
- ML: currently there is work on the baseline for HTTP binding, identifying constraints and rules on the data model
- 13:12:45 [sebastian]
- ... inambiguous interaction semantics
- 13:12:53 [sebastian]
- ... constraints on payload formats
- 13:13:10 [sebastian]
- .. protocol binding semantics
- 13:13:27 [sebastian]
- ... best practice security requirements
- 13:13:33 [sebastian]
- ... compliance
- 13:15:37 [McCool]
- https://github.com/w3c/wot-security-best-practices
- 13:16:07 [McCool]
- general guidelines and considerations are here: https://github.com/w3c/wot-security
- 13:16:26 [sebastian]
- ML: there are open issues in the data model sections like about the data model constraints
- 13:16:44 [McCool]
- my suggestion is to lean heavily on the security-best-practices doc, which is currently being updated
- 13:17:15 [McCool]
- but even so we will have to define at least two contexts, because of the annoying situation with TLS on LANs
- 13:17:36 [kaz]
- q?
- 13:17:46 [McCool]
- ack m
- 13:20:01 [sebastian]
- ML: regarding eventing model there is a 'Push' proposal
- 13:20:37 [sebastian]
- q+
- 13:20:42 [Ege]
- q+
- 13:21:30 [kaz]
- ack s
- 13:21:33 [kaz]
- ack e
- 13:21:38 [Ege]
- q+
- 13:21:56 [kaz]
- q+
- 13:22:17 [kaz]
- ack e
- 13:23:08 [kaz]
- present+ Philipp_Blum
- 13:23:41 [stevelee]
- stevelee has joined #wot
- 13:24:24 [sebastian]
- ML: Webhooks are used in many solutions like in github, paypal, atlassian and wordpress
- 13:24:39 [McCool]
- q+
- 13:26:04 [sebastian]
- Ege: we have no imlementations of webhooks in the testfest so far
- 13:26:48 [sebastian]
- ... we should also check what is implemented in OpenHub as example
- 13:27:28 [sebastian]
- ML: there is the chance to have this in the Oracle binding
- 13:27:44 [sebastian]
- Daniel: I think, this is not the case. But Im not 100% sure
- 13:28:18 [McCool]
- ack k
- 13:29:09 [kaz]
- ack m
- 13:29:37 [sebastian]
- Kaz: Im agree with Ege. We should involve ECHONET, NHK, Netzo etc. in the discussion and ask them for opinion
- 13:30:07 [kaz]
- s/Im agree with Ege/I partly agree with Ege's points/
- 13:30:45 [kaz]
- s/involve/ask WoT implementers about their approaches, e.g., /
- 13:31:08 [kaz]
- s/Netzo etc./Takenaka and Netzo./
- 13:31:33 [McCool]
- q+
- 13:31:37 [kaz]
- s/ in the discussion and ask them for opinion//
- 13:31:40 [kaz]
- q?
- 13:32:04 [sebastian]
- ML: introduces Cloud Events
- 13:32:41 [sebastian]
- ... is a specification for describing event data in common way
- 13:32:43 [sebastian]
- q+
- 13:33:05 [kaz]
- rrsagent, draft minutes
- 13:33:05 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/27-wot-minutes.html kaz
- 13:34:29 [sebastian]
- MM: Im wondering if this implementable for the profile on time?
- 13:34:40 [kaz]
- q+ to suggest we concentrate on the current features
- 13:34:42 [dape]
- q?
- 13:34:44 [sebastian]
- ML: for Oracle it would be important
- 13:35:05 [dape]
- q+
- 13:35:13 [kaz]
- ack mc
- 13:36:51 [ryuichii]
- q+
- 13:37:00 [ryuichii]
- q-
- 13:38:56 [kaz]
- sk: want to ask about the Cloud Events
- 13:39:09 [kaz]
- ... is that a standard or de facto?
- 13:39:21 [kaz]
- ml: pretty small specification
- 13:39:23 [kaz]
- @@@link
- 13:39:44 [mlagally]
- https://cloudevents.io/
- 13:39:58 [kaz]
- pb: it's run by the Linux Foundation
- 13:40:02 [McCool]
- (cloudevents is typical of "cloud" standards; someone publishes something, but is there an SDO? Not necessarily...)
- 13:40:19 [kaz]
- ask
- 13:40:22 [kaz]
- s/ask//
- 13:40:23 [kaz]
- ack s
- 13:40:34 [kaz]
- sk: any experience?
- 13:40:36 [McCool]
- (but if enough people use it... it's a "standard")
- 13:40:45 [kaz]
- ml: my colleague is working
- 13:40:56 [kaz]
- qq+ ege
- 13:40:59 [kaz]
- ack ege
- 13:40:59 [Zakim]
- ege, you wanted to react to sebastian
- 13:41:19 [kaz]
- ml: we have to work on the detail separately
- 13:41:30 [kaz]
- ack k
- 13:41:30 [Zakim]
- kaz, you wanted to suggest we concentrate on the current features
- 13:43:01 [sebastian]
- Kaz: I'm wondering of the next step of the profile based on the provided MM schedule plans. I think it make sense to consider this for the next version
- 13:44:05 [kaz]
- s/version/version. A possibility is our going for Living Standards instead of RECs so that we can add any necessary features whenever we want but that would be a bigger question./
- 13:44:13 [kaz]
- q?
- 13:44:17 [sebastian]
- ML: we should plan this in the 1.0 release
- 13:45:30 [kaz]
- s/1.0/current/
- 13:45:54 [citrullin]
- citrullin has joined #wot
- 13:45:57 [citrullin]
- q+
- 13:46:19 [kaz]
- s/next version/next version. We can start initial survey in parallel, though./
- 13:46:23 [kaz]
- q?
- 13:46:25 [kaz]
- ack d
- 13:46:38 [sebastian]
- Daniel: i think its quite late for considering webhook and cloud events
- 13:46:40 [McCool]
- q?
- 13:47:08 [sebastian]
- ... I like to understand what is the consequences when we put those in?
- 13:47:38 [sebastian]
- MM: we plan to have tests fest Mid February
- 13:47:59 [sebastian]
- s/tests fest/testfest
- 13:48:25 [kaz]
- q?
- 13:48:35 [kaz]
- ack cit
- 13:48:46 [sebastian]
- q+
- 13:48:56 [Ege]
- q+
- 13:49:12 [sebastian]
- Philipp: we had a simple discussion with SenML
- 13:49:27 [kaz]
- rrsagent, draft minutes
- 13:49:27 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/27-wot-minutes.html kaz
- 13:49:27 [sebastian]
- .. there was many discussion about this like the structure
- 13:49:36 [kaz]
- s/many/much/
- 13:49:58 [kaz]
- s/this like the/this kind of/
- 13:50:24 [kaz]
- i/want to ask/scribenick: kaz/
- 13:50:35 [kaz]
- i/I'm wondering of/scribenick: sebastian/
- 13:50:38 [kaz]
- rrsagent, draft minutes
- 13:50:38 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/27-wot-minutes.html kaz
- 13:50:39 [kaz]
- q?
- 13:50:45 [kaz]
- qq+ Ege
- 13:50:48 [kaz]
- ack ege
- 13:50:48 [Zakim]
- Ege, you wanted to react to citrullin
- 13:51:27 [kaz]
- ack s
- 13:51:58 [kaz]
- sk: our discussion on SenML was mainly about the payload structure
- 13:52:08 [McCool]
- (time check...)
- 13:52:11 [kaz]
- pb: how to integrate it with TD
- 13:52:49 [mlagally]
- q?
- 13:53:08 [kaz]
- ack e
- 13:53:38 [Ege]
- ah sorry I remember now what I wanted to really ask
- 13:53:38 [Ege]
- q+
- 13:54:30 [sebastian]
- ML: the next steps are the push mechanism, rework data mode, implementation report, compliance section, authentication and securiry, uncioorate PlufFest findings
- 13:54:44 [sebastian]
- s/mode/model
- 13:55:26 [kaz]
- s/NHK,/NHK, the other Plugfest participants, /
- 13:55:30 [sebastian]
- ML: future work will cover other protocols like MQTT, ECHONET Lite, OPC-UA
- 13:55:33 [kaz]
- rrsagent, draft minutes
- 13:55:33 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/27-wot-minutes.html kaz
- 13:55:36 [kaz]
- q?
- 13:55:44 [kaz]
- s/@@@link//
- 13:55:58 [kaz]
- qq+ McCool
- 13:55:58 [sebastian]
- ... provide requirements for TD 2.0
- 13:56:03 [kaz]
- ack M
- 13:56:03 [Zakim]
- McCool, you wanted to react to Ege
- 13:56:28 [kaz]
- i/our discussion on SenML/scribenick: kaz/
- 13:56:37 [sebastian]
- ML: Publication schedule is to freeze Jan 31, 2022
- 13:56:38 [kaz]
- i/the next steps are/scribenick: sebastian/
- 13:56:42 [kaz]
- rrsagent, draft minutes
- 13:56:42 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/27-wot-minutes.html kaz
- 13:57:03 [kaz]
- ack e
- 14:00:03 [cris]
- cris has joined #wot
- 14:00:08 [kaz]
- [10-min break; then Scripting API (35mins) and Marketing]
- 14:00:15 [kaz]
- rrsagent, draft minutes
- 14:00:15 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/27-wot-minutes.html kaz
- 14:03:10 [Ege]
- cloudevents is from cloud native foundation instead of linux foundation right? @citrullin?
- 14:06:23 [zkis]
- zkis has joined #wot
- 14:11:35 [cris]
- topic: Scripting API
- 14:12:10 [cris]
- dape shows Scripting API slides
- 14:12:33 [cris]
- dape: new options for consumer and exposer applications
- 14:12:43 [cris]
- ... action state control
- 14:12:45 [cris]
- ... discovery
- 14:12:50 [kaz]
- present+ CAabye
- 14:12:56 [cris]
- ... current node-wot status
- 14:13:13 [cris]
- subtopic: Consume and Expose options
- 14:13:58 [cris]
- dape: pick one particular security scheme or protocol
- 14:14:41 [cris]
- ... currently there's an interaction level option object to deal with particular binding.
- 14:15:03 [cris]
- ... consume options will help with this task
- 14:15:24 [cris]
- ... is a non-breaking change
- 14:16:06 [cris]
- ... similarly for the exposed side
- 14:16:25 [cris]
- ... node-wot offer a lot of different protocol bindings
- 14:16:26 [kaz]
- present- CAabye
- 14:16:33 [kaz]
- present+ Christian_Aabye
- 14:16:51 [cris]
- ... there's no practical way to configure the exposing algorithm
- 14:17:04 [cris]
- ... like specify what is going to be exposed.
- 14:17:42 [cris]
- ... but you need also a way to know is supported. In other words, enumerate runtime capabilites
- 14:17:56 [cris]
- subtopic: Action state and control
- 14:18:26 [cris]
- dape: there're some new proposal about how actions should behave in the WoT world
- 14:18:52 [cris]
- ... we are planning to introduce new APIs to control Actions status
- 14:19:17 [cris]
- ... we are thinking about a Control object to manipulate an Action State
- 14:19:37 [cris]
- ... it's a breaking change
- 14:20:03 [cris]
- ... but we need the discussion to settle in other spec (TD and Profile)
- 14:20:22 [cris]
- ... there's no way to properly handle action queue
- 14:21:02 [cris]
- ... we need to understand the security model for Action states
- 14:21:35 [cris]
- subtopic: Discovery
- 14:21:49 [cris]
- dape: we are trying to cover also the discovery spec
- 14:22:10 [cris]
- ... we are waiting for a stable discovery document
- 14:22:24 [cris]
- ... we can alredy support basic discovery spec
- 14:22:44 [cris]
- ... however for scripts is beneficial to discover things easier
- 14:23:09 [cris]
- mc: regarding this we don't have time to push new features in Discovery
- 14:23:19 [kaz]
- q?
- 14:23:24 [kaz]
- q+ McCool
- 14:23:24 [cris]
- ... we can add this to the next charter
- 14:23:26 [kaz]
- ack m
- 14:24:05 [cris]
- ... it all nails down to which introduction mechanism you want to support in Scripting API
- 14:24:06 [kaz]
- q+
- 14:24:12 [kaz]
- qq+ Zoltan
- 14:24:12 [cris]
- zoltan: the names are just examples
- 14:24:16 [kaz]
- ack z
- 14:24:16 [Zakim]
- Zoltan, you wanted to react to McCool
- 14:25:16 [cris]
- dape: how to solve nearby?
- 14:25:36 [cris]
- mc: bluetooth beacon introduction would work
- 14:26:13 [cris]
- dape: we are still considering how to split the two discovery phases
- 14:26:23 [cris]
- mc: I would propose just second phase
- 14:26:42 [cris]
- dape: the issue here is that we still need introduction mechanism
- 14:26:49 [cris]
- mc: we are missing that
- 14:26:59 [cris]
- ... we have to include on-boarding
- 14:28:40 [cris]
- zoltan: I think the introduction belong to another API
- 14:29:55 [zkis]
- but we need to make a difference between discovering directories vs TDs
- 14:30:14 [cris]
- dape: I think onboarding could be specified inside Scripting API
- 14:30:44 [cris]
- mc: let's have a joint meeting asap
- 14:30:57 [cris]
- subtopic: consquences of recent changes
- 14:31:11 [cris]
- dape: ExposedThing does not extends ConsumedThing
- 14:32:03 [cris]
- ... how to properly test an ExposeThing?
- 14:32:20 [cris]
- ... how to use it as a ConsumedThing?
- 14:32:42 [cris]
- subtopic: node-wot status update
- 14:32:55 [cris]
- dape: now it supports Readable Streams
- 14:33:05 [cris]
- ... it took us a while
- 14:33:19 [cris]
- ... it is going to be updated soon
- 14:33:57 [cris]
- ... should we first implement than update??
- 14:34:20 [cris]
- s/update/update spec/
- 14:34:29 [cris]
- ... what people think about this approach?
- 14:34:45 [cris]
- ... it would take longer to change the spec
- 14:35:47 [cris]
- ... contributions are always welcomed
- 14:36:44 [cris]
- ... node-wot is increasing download count per day
- 14:36:59 [cris]
- s/day/month/
- 14:37:15 [mlagally]
- q+
- 14:37:22 [sebastian]
- q+
- 14:37:25 [kaz]
- q?
- 14:37:51 [kaz]
- ack ml
- 14:37:59 [kaz]
- q-
- 14:38:03 [kaz]
- q+
- 14:38:11 [cris]
- ml: do have statistics about users?
- 14:39:19 [cris]
- dape: we can't know for sure
- 14:39:26 [cris]
- ... but we are getting more contributions
- 14:39:40 [cris]
- ... we also have newcomers contributions
- 14:39:49 [cris]
- ... also outside of the group
- 14:39:53 [cris]
- ml: it is good to see
- 14:40:00 [kaz]
- ack s
- 14:40:42 [cris]
- seb: we released in march and April our new web page. Maybe that increased the download.
- 14:40:50 [cris]
- ... web page and youtube video
- 14:41:12 [cris]
- ... if you look carefully the growth started right after April
- 14:41:17 [kaz]
- q?
- 14:41:42 [cris]
- subtopic: next goals
- 14:41:53 [cris]
- dape: allign with all the TD features
- 14:42:03 [cris]
- ... todo: canonicalization
- 14:42:12 [cris]
- ... todo: discovery
- 14:42:16 [McCool]
- q+
- 14:42:30 [cris]
- ... todo: wot profile? is it in scope?
- 14:42:56 [cris]
- ... let us know if there's anything you would like to see
- 14:43:24 [cris]
- zoltan: we are focuses on interactions
- 14:43:36 [cris]
- s/focuses/focus/
- 14:43:45 [dape]
- q?
- 14:43:46 [kaz]
- s/focus/focusing/
- 14:43:52 [cris]
- dape: please join our call if anything
- 14:44:13 [cris]
- kaz: echonet used node-wot for plug-fest
- 14:44:45 [cris]
- ... even if Scripting API is a group note, it would be nice to publish a new note soon
- 14:45:09 [cris]
- mc: scripting api should be consistent with node-wot implementation
- 14:45:09 [kaz]
- s/echonet/I confirm echonet/
- 14:45:25 [kaz]
- s/even/next point, even/
- 14:46:14 [cris]
- mc: we may don't need canonicalization yet
- 14:46:28 [kaz]
- s/soon/soon. It would be nice to publish updated Notes regularly when it becomes stable./
- 14:46:28 [cris]
- zoltan: we discussed about versioning and node-wot alligment
- 14:46:37 [mlagally]
- q+
- 14:46:38 [kaz]
- s/may don't/may not/
- 14:46:40 [kaz]
- ack k
- 14:46:42 [kaz]
- ack mc
- 14:47:52 [cris]
- zoltan: node-wot should be alligned with normative spec
- 14:48:02 [dape]
- q?
- 14:48:34 [cris]
- ml: why are we withdraw canonicalization?
- 14:48:52 [cris]
- mc: we can't have it without breaking backward compatibility
- 14:49:06 [kaz]
- s/withdraw/withdrawing/
- 14:49:06 [kaz]
- q?
- 14:49:10 [kaz]
- ack ml
- 14:49:52 [cris]
- topic: marketing
- 14:50:14 [cris]
- seb: time issue... maybe it is better to split it
- 14:50:26 [mlagally]
- ml: I'm raising serious concerns if the TD removes the canonical form. Profile is dependent on it
- 14:51:00 [kaz]
- q+ to suggest we discuss that during the Editors call
- 14:51:23 [kaz]
- ack k
- 14:51:24 [Zakim]
- kaz, you wanted to suggest we discuss that during the Editors call
- 14:52:04 [cris]
- ege: marketing task force
- 14:52:21 [cris]
- subtopic: chair changings
- 14:52:31 [cris]
- ege: Sebastian leaved as chair
- 14:52:43 [kaz]
- q+
- 14:52:45 [zkis]
- present- Zoltan_Kis
- 14:52:58 [cris]
- ... after TPAC Fady Salama will chair testing
- 14:53:22 [cris]
- ... and Ege Korkan will take over marketing
- 14:53:30 [cris]
- kaz: notice it is just a proposal
- 14:53:43 [cris]
- subtopic: news
- 14:53:47 [cris]
- ege: explainer video
- 14:53:57 [cris]
- ... improved web page
- 14:54:20 [cris]
- ... new logo animation
- 14:54:38 [kaz]
- s/notice it is just a proposal/I'm kind of surprised to see this "change" now. You should have mentioned this proposal beforehand. So would suggest this slide says "Chair Change Proposal" for today./
- 14:54:49 [cris]
- ... new task force descriptions
- 14:55:17 [cris]
- ... sebastian contributed with a new documentation page
- 14:55:23 [cris]
- ... just a quick overview
- 14:55:43 [cris]
- ... new tutorials by Philpp and a new one from TUM/Siemens
- 14:56:05 [cris]
- ... we organized all the videos in our web page
- 14:56:27 [cris]
- ... on twitter we are now 332 followers
- 14:56:51 [cris]
- ... we have 6.1K impressions
- 14:57:20 [cris]
- ... we now have 10.8K impression
- 14:57:49 [cris]
- ... the video alone generated alone 13K
- 14:58:02 [cris]
- ... content is critical to get good impression count
- 14:58:11 [pchampin]
- pchampin has left #wot
- 14:58:27 [dape]
- q+
- 14:58:31 [kaz]
- q-
- 14:59:04 [kaz]
- ack d
- 14:59:32 [cris]
- dape: statistics are very useful, but we need information about website visits
- 14:59:39 [sebastian]
- +1
- 14:59:41 [kaz]
- q+
- 14:59:49 [cris]
- ege: w3c is already tracking but we don't have access to them
- 14:59:59 [cris]
- ... no response from w3c managment
- 15:00:31 [cris]
- kaz: there were actually responses from w3c managment
- 15:00:44 [cris]
- ... we just did not reach a final agreement yet
- 15:00:47 [kaz]
- s/management/system team/
- 15:00:48 [kaz]
- s/management/system team/
- 15:01:24 [cris]
- sebastian wraps up the session
- 15:01:48 [dape]
- q+
- 15:01:53 [kaz]
- q-
- 15:02:42 [cris]
- dape: there's an error in the agenda
- 15:02:43 [dape]
- ack dape
- 15:02:49 [cris]
- seb: true it is 3 hours
- 15:03:01 [kaz]
- [adjourned]
- 15:03:06 [kaz]
- rrsagent, draft minutes
- 15:03:06 [RRSAgent]
- I have made the request to generate https://www.w3.org/2021/10/27-wot-minutes.html kaz
- 15:05:04 [takio]
- takio has left #wot
- 17:03:23 [Zakim]
- Zakim has left #wot
- 19:04:20 [zkis]
- zkis has joined #wot