Meeting minutes
<bneedham> p+
Overview
McCool: would adapt Web tech to IoT
… fragmentation issue with IoT
… mashing up various IoT mechanisms by WoT
… WoT Thing Description 1.0 REC published during the previous Charter
… we're extending its capability now
… [Descrptive Interoperability: TDs]
… [Discovery]
… The other thing for this Charter period is WoT Discovery
… obtain TD of interest from devices
… not limited to local network
… 2-phase access
… introduction and exploration
… open and controlled, respectively
… variety of introduction mechanisms
… URL, DID ,QR code, etc.
… can be a directory service
… [Orchestration]
… consume TD
… node-gen based on Node-RED
… and node-wot uisng the WoT Scripting API
… [Deliverables]
… links to the current EDs
… Architecture 1.1, D 1.1, Discovery and Profile
… also Notes
… [Recent Activity]
… focused on testing for CR/PR transition
… commercial usages
… directory implemetation
… [Applications]
… Takenaka Corporation, Siemens, Netzo and ditto project
… [Resources and Contacts]
… www.w3.org/WoT
Demos
McCool: switch to demos
McCool/Ezell - Retail, Home Assistant Integration, Node-RED, Discovery
McCool: convenience stores and gas stations
… [Outline]
… [Applications]
… [Test Scenario: Cooler Monitor]
… devices provided by different vendors
… probably would have a local proxy
… various protocol translation
… [Why Hubs]
… [Desired Behavior]
… door open alert, etc.
… [Devices]
… test devices and commercial devices
… [Video: System Demo]
… (shows a video uploaded to YouTube)
… both commercial devices and test devices work collaboratively
… very simple application
… [Two implementation]
… home assistant native rules, Node RED
… home assistant based on an opensource
… automation rules underneath with YAML
… [Node-RED/WoT Discovery]
… [Node-RED subflows]
… fetch TD, extract payload
Toumura - Discovery (mDNS-SD, TD Directory)
Toumura: [Node-RED - WoT Discovery Integration
… two tools added: node generator (node-gen) and Thing Explorer
… Explorer can be easily added to the ordinary Node RED environment as plugin
… [Supported Discovery Methods]
… several methods available
… [Visualize relationship between Thing]
… [Visualization Example]
… black circle is a Thing
… the arcs are relationship between Things
… [Demo]
… generate nodes by dragging them
… configure relationship
… [Lessons Learned]
… "tdid" contains the "id" of the target TD
Endo - NHK Hybridcast Connect
Toumura: [Outline]
… objective
… previous proposed media use cases
… demo
… WoT-enabled Hybridcast Connect
… commercial TV also available for that purpose
… [Objective]
… integration of contents from broadcast wave and Web
<McCool> (please use "q+" if you have a question, and we will take them in order when Endo-san is done)
Toumura: [Previous Proposed Media Use Case from NHK]
… TPAC 2019, 2020 and 2021
… commercial TV certified by IPTV Forum available
… [Demo]
… TV shows a soccer program
… but air cleaner makes noise
… if the TV receives event message to "replay" many times, the air cleaner will reduce the noise
… [Demo System Configuration]
… TV, Node RED app, and Node RED dashboard UI
… [WoT-enabled Hybridcast Connect]
… Hybridcast app on TV - Hybridcast Conect WoT node - user app (as a WoT Consumer) - ECHONET WoT node - air cleaner emulator
… broadcasting services can be cnnected to various devices now!
… various possible use cases for WoT
… [Open source software tools]
<Zakim> kaz, you wanted to ask (1) any gateway between tv and UI, and (2) how to specify the rules
Kaz: wondering about connection mechanism;
… but can you go back to connections diagram, slide 9
… use have a user app as the WoT consumer
… air cleaner is a Thing, using ECHONET
… what is the hybridcast TV itself? Is it an app?
McCool: there is a TD for the TV, so is it a Thing?
Endo: in this demo scenario, tv can emit information only
Kaz: so tv could also automatically repeat based on noise, for example?
Kaz: second question, was how to specify rules
… depending on the user application? just using node-RED? JS? What is your model?
Endo: this demo is just a very simple if-then algorithm
McCool: required by user requiring rules
… maybe the smart tv can make prompt to the user asking what to do
… potentially
Endo: yes, that's possible
… this time we used simple replay scenario but some kind of schema model could be applied
… and the use app can catch user's input
McCool: question for Toumura-san then
… could you please pick up your slides?
… local area network applications
… how to make that unique?
… you're using URN as an ID
… also allows DID
… what can be used instead of HTTP URL?
… raising an interesting point
… related to an issue on global DNS and CA
Toumura: difficult to handle local network id
McCool: hostname is also kind of dangerous
… need to avoid collisions
Toumura: if we use some random ID, would get another kind of problem
McCool: right
… let's have more discussion about IDs
… HTTPS on browsers depend on CAs
<Zakim> dezell, you wanted to remark on similarities of the roles between "Hybridcast Connect" and "Home Assistant" in two demos.
David: great demos
… sort of same pattern
… more or less, smart assistant as home gateway
… Endo-san used Node RED
… that pattern makes sense
… Node RED plays important role for WoT
… the other thing
… a question about how this mechanism works with browsers
… collaboration would be nice
McCool: we need to look at trust management, etc.
Kaz: and we should continue with the DAS WG guys as well :)
[adjourned]