W3C

- DRAFT -

Online PlugFest - slot C

27 Sep 2018

Attendees

Present
Kaz_Ashimura, Itaru_Nakagawa, Matthias_Kovatsch, Michael_Lagally, Michael_McCool, Takeshi_Sano, Kunihiko_Toumura, Michael_Koster, Benjamin_Klotz, Takeshi_Yamada, Ryuichi_Matsukura, Toru_Kawaguchi
Regrets
Chair
McCool
Scribe
kaz

Contents


PRs

McCool: merged PRs
... working with Koster

Kaz: PR 554, 553, 552?

McCool: right

https://github.com/w3c/wot/pull/554

https://github.com/w3c/wot/pull/553

https://github.com/w3c/wot/pull/552

Intel

McCool: proxies all working now
... trying CoAP stuff
... but some problem maybe due to the VPN server
... that's my working assumption
... rather than fight more, set up a bridge for physical bridges
... first thing to do tomorrow morning

Koster: that's my next step too to set up a bridge

McCool: can sent an email

Koster: would like to try any way

McCool: would send an email to Toru and Itaru
... also updated all my TDs
... only thing here

https://github.com/w3c/wot/blob/master/testing/online/intel.md

McCool: go back to the main README.md

https://github.com/w3c/wot/blob/master/plugfest/2018-sept-online/README.md

McCool: and TD

https://github.com/w3c/wot/blob/master/plugfest/2018-sept-online/TDs/Intel/OCF-TDs.json

Kaz: you changed the break line code?

McCool: also changed the IP address for VLAN
... and CoAP thing here
... protocol binding for OCF devices

Eurecom

Benjamin: included some note in the preparation.md

https://github.com/w3c/wot/blob/master/plugfest/2018-sept-online/preparation-eurecom

Kaz: the file doesn't have an identifier of ".md", so not correctly rendered

Benjamin: will fix it

McCool: do you use OAuth?

Benjamin: both OAuth and OAuth2 on the same IP address

McCool: changed the IP address on README.md
... 18.197.31.47?

Benjamin: yes

McCool: (adds ".md" to the file name of preparation-eurecom)

Panasonic

Toru: working with Oracle server
... now can access the vehicle simulator too
... Benjamin also accesses our devices

McCool: you're using local network?

Toru: Takeshi is working on that

McCool: btw, Benjamin, what's your next step?

Benjamin: a few app servients
... connected car and simulator from Oracle
... also vehicle and smart home
... and some testing
... MQTT for smart parking
... also practice with servient with different protocols

McCool: and what is the next step, Toru?

Toru: would check the remote proxy tomorrow

Hitachi

Toumura: not much updates
... would try Intel's devices using new OCF interface
... but can't access Intel devices
... will continue to work on that

McCool: portal or VLAN?

Toumura: using portal

McCool: please double check the setting
... portal is up and down for a while
... appears working now

Toumura: the URLs here correct (on README.md)?

McCool: did you get password prompt?

Toumura: can't see password prompt

McCool: does require authentication

Toumura: password for proxy and basic authentication

McCool: email later on
... hope issues will be sorted out tomorrow morning

Toumura: tomorrow would continue to build things

Siemens

Matthias: working again on node-wot
... command line tools
... parameter for config file fixed
... some improvement
... updated fest proxy
... also finished new command line tool
... exposes to Fujitsu or Oracle
... hope it makes node-wot to become local proxy
... tested API version
... registered with Fujitsu proxy, but quite slow
... not sure why

McCool: update on Thing Directory?

Matthias: Victor did some fixes
... 500 error already notified
... is the Fujitsu remote proxy operational at the moment?

Sano: it's activated now

Matthias: some delay with websocket connection
... a few seconds
... Thing doesn't come up
... wondering what the issue is

Kaz: Sano-san, do you think you can check the connectivity?

Sano: will check it

Kaz: 2 possibilities
... check the log with Matthias's case
... also can check the connectivity using Fujitsu's client

Sano: ok

Matthias: the list didn't show up so far
... there was only Panasonic's UUID devices

Sano: will check what's happening

Matthias: note that the delay might be a side effect
... bigger issue is that my client doesn't show up

Sano: ok

SmartThings

Koster: MQTT motion sensor
... cloud-reachable
... just need to add security and a couple of syntax
... no security so far

McCool: we have no security specified by "nosec"
... need to fix that

Koster: would like to enable basic auth
... on my node-red
... will be doing that
... but no way to add sensors
... don't have Internet bubble head myself
... and also would use MQTT actions
... so far working on VPN setting
... common server-side pattern

McCool: tested VLAN

Koster: could use MAC address for VLAN?

McCool: level 2 may be broadcasting

Koster: the process of discovery

McCool: definition of device class like lump
... let's try to integrate your directory and mine

Koster: we should put all the tools together?

McCool: pretty interesting

Koster: going to try node-wot scripting
... and semantic integration
... how to build all the vocabulary?

Yamada: how to get TDs from SmartThings?

Koster: not yet, but will upload my TDs on GitHub
... this morning

Oracle

Lagally: working with Panasonic for a few topics
... including the issue Toru mentioned
... monitoring applications
... work in progress

Fujitsu

Sano: Fujitsu tried to connect with CoAP devices
... from our app via proxy
... can get connected
... would control CoAP devices via the proxy
... tomorrow will try the other CoAP devices

McCool: any non-CoAP devices?

Sano: VLAN devices as well

McCool: your own implementation?
... made your own CoAP devices?

Sano: no
... we don't have any CoAP devices

McCool: ok

Panasonic (revisited)

Yamada: some problems so far
... but will fix them and get ready tomorrow

McCool: everybody has made a report
... the meeting can be adjourned
... but people can stay here if want

Lagally+Koster: can stay here

SmartThings (revisited)

<mjkoster> this TD should work

<mjkoster> https://github.com/w3c/wot/blob/master/plugfest/2018-bundang/TDs/SmartThings/td-light.json

<mjkoster> but doesn't have the security statement so it won't validate

Koster: the above TD from Bundang should work

Kaz: will we work for "C+1" and "C+2" today?

McCool: have conflict, so will work tomorrow

Kaz: in that case, please update the "possible slot" with the updated information

Matthias: would prefer the slots today

Lagally: how long should we extend this slot?
... +1h or +2h?

Kaz: Matthias, will you come back in 1h or 2h?

Matthias: think in 1h

Sano: need to leave in 0.5h

Matthias: still have some issue
... would be great if you could work on that now

Kaz: Sano-san, please try to work on that within 30mins from now
... if it's impossible to fix the issue now, you can work on that tomorrow

[slot C adjourned; but we'll stay here for 2h (at max)]

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: 2018/09/27 14:58:21 $