W3C

- DRAFT -

WoT PlugFest at TPAC 2019

18 Sep 2019

Attendees

Present
Rob_Sanderson, gkellogg, Gregg_Kellogg, Kaz_Ashimura, Hiroki_Endo, Michael_McCool, JohnRochford, Masa, Mashita, Kunihiko_Toumura, Ryuichi_Matsukura, Takahisa_Suzuki, Sebastian_Kaebisch
Regrets
Chair
McCool
Scribe
kaz

Contents


mm: presentation plus demo
... walk through scenarios
... we're looking at PlugFest to see interoperability

kaz: please join the IRC at #wot-pf and also "present+" you name

mm: (goes through the slides)
... [W3C Web of Things]
... we're middle of rechartering the WG
... will have 2-day sessions to discuss the plan
... [W3C Web of Things - Building Blocks]
... building blocks here
... TD is general metadata based on JSON-LD
... [Published CRs]
... (Thing Description example on the right side)
... [PlugFest picture]
... actually several things here
... several scenarios working together

<Mizushima> preset+ Tomoaki_Mizushima

mm: devices provided by different vendors
... the basic idea is describing what the device does
... devices can be provided in various ways
... [PlugFest Devices]
... end point devices as sensors/actuators
... devices in a homenetwork here
... you may create a proxy for proper security
... Fujitsu has a proxy system here
... Intel as well
... Mozilla provides gateway mechanism
... light switches from different vendors
... possibly could be cloud services
... this time NHK provides a TV set including the Hybridcast technology
... Panasonic provides a lot of things
... some of the are here in Fukuoka locally
... and some others are remote
... much more devices could be included
... Oracle provides cloud simulators
... Siemens also has a simulator
... TUM provides bunch of sensor devices
... [Scenario 1]
... different scenarios here
... two scenarios
... one is about smart home
... smart building is something like a hotel
... integrate those together
... authentication problem is interesting
... enabling accessibility is also an important/interesting point for the scenario
... maybe you have a door bell and synchronized with a flash
... we have speech synthesizer as well
... also smart storage battery
... [another photo]
... Fujitsu's devices (and Mozilla gateway)
... door bell, buzzer and flash
... motion sensor as well
... you can use a gateway for zigbee devices
... Fujitsu box here is a proxy
... also Google home device can be connected
... interesting to have a local proxy as a hub rather than going out to a cloud service
... [Scenario 2]
... Industrial scenario
... different kind of requirements for authentication and security
... one use case here
... functional safety application
... you want to get alarm
... when people go to wrong places
... Oracle simulator image
... on the right screen
... simulating HVAC system and fest plant
... good for IoT training
... many industrial controls are expected
... has Thing Descriptions included
... [Siemens screen]
... car charging service

dp: buildings representing smart buildings
... power consumption is detected
... also on the left side electric power charger
... the devices have different interface for each

mm: for smart grid, there are various interfaces
... we can see energy bi-directional
... house to car vs car to house
... very interesting/important question
... ecoG, Siemens subsidiary, working on the mechanism
... natural thing to happen
... car charging stand is kind of like gas stand
... could be collocated with convenience stores
... could have distributed power management system
... [NHK Hybridcast Integration]
... [picture as well]

endo: our demo describes Hybridcast system
... working with the WoT framework
... broadcasting content can transfer events as a trigger for that purpose
... we use "node-wot" as the basis for the interface
... the orange application here on the slide catches the event from the broadcasting content
... and handle the external devices

mm: [NHK TV content]

endo: application data on the right side
... start/stop a robot cleaner

mm: broadcast content includes signal to kick the application
... we have an informative Note on protocol binding
... [Orchestration]
... next issue is orchestration
... currently have two ways
... Node-RED and node-wot
... you can find the code of node-wot on GitHub
... node-wot is a library based on Node.js
... [WoT Workshop: Munich 2019]
... had a W3C workshop the other day
... pretty nice systems running here
... you can see a BMW car as part of the WoT PlugFest
... described by Thing Description
... upper right is Mozilla gateway
... [W3C WoT Resources]
... that's it for my presentation
... uploaded on GitHub
... the main repo is "wot" under w3c

McCool's slides

mm: finish a bit earlier
... and would invite you all to the lunch place for actual demo
... questions?

(none)

mm: ok
... in that case, please come to the lunch place for the actual demo
... tx!

[presentation done; people move to the lunch place for actual demo]

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/09/18 05:05:06 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s|@@@link|McCool's slides|
Present: Rob_Sanderson gkellogg Gregg_Kellogg Kaz_Ashimura Hiroki_Endo Michael_McCool JohnRochford Masa Mashita Kunihiko_Toumura Ryuichi_Matsukura Takahisa_Suzuki Sebastian_Kaebisch
No ScribeNick specified.  Guessing ScribeNick: kaz
Inferring Scribes: kaz

WARNING: No "Topic:" lines found.


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]