Agenda

<inserted> scribenick: McCool

plugfest todo, including dev meetup scenarios

https://github.com/w3c/wot/blob/master/plugfest/2018-lyon/Scenarios.md

Oracle

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

oracle results, graph showing combinations

also have node-wot script

and a bridge servient integrating with Panasonic's devices

tried, but ran out of time

for cloud service, have information coming

from festo plant and keti sensor

then orchestrate actions based on events

rgb light simulator

also fixed convertor during plugfest, outputs TDs that validate

no support for observe at the moment

looked at use cases

see screeshots

home environment

simulated KETI device

can trigger other events, eg change color of the lamp

industrial use case

distributed assets

can visualize on a map and navigate

this is what I would advocate for next plugfest

let's build on what we have working

Look at Scenarios.md...

https://github.com/w3c/wot/blob/master/plugfest/2018-lyon/Scenarios.md

what do we do with Dev Meetup?

Lagally: maybe one table home, one industrial

McCool: remote or local?

Lagally: more interesting to look at remote sites

McCool: I like the idea of two separate demos

Lagally: what about video streams?

McCool: I'm guessing 95% certainty that google hangouts will work

<inserted> scribenick: kaz

Kaz: who will attend the dev meetup?

lagally, mccool, koster, matthias, daniel, sebastian, kaz, dave (from the discussion at the main call)

toumura, yamada (confirmed now)

McCool: let's see who to bring what

(updates the Scenarios.md with the information on devices/applications)

Initial discussion on Demo planning

one home demo and one industrial demo

remote demo but need a fallback to local one

also fallback via simulators

home demo based on Panasonic's devices

industrial demo using festo plant

directory search, orchestrate devices from SmartThigns and Intel

possibly 3 demos above

McCool: remote: home demo and industrial demo
... local fallback by node red orchestrating devices from Intel/SmartThings
... motion/button activates light, camera, speech output
... (categorize three demos)
... home scenario, industrial demo and local fallback

Kaz: btw, diving into the planning is fine
... but there are reports from Panasonic and Hitachi as well
... quick report by them?

Panasonic

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

Yamada: report above
... summary diagram here
... doted line shows some issues
... 3.2.7 Security
... bearer token: The browser could access Remote proxy (Fujitsu) only after bypassing CORS checking at the browser.
... OAuth2: The browser could not access MyCarThing (Eurecom) even after bypassing CORS checking at the browser. It was caused by "https + self-signed certificate".
... the issues should be resolved

McCool: requires changes for TD?
... looks like proxy implementation issue
... and self-signed certificate
... did you try accessing devices using nod-wot?

Yamada: just Panasonic ones
... not node-wot

Kaz: this issue implies a question if we should think about CORS for node-wot

McCool: should consider that
... discussion during the security calls about bearer token and OAuth

Hitachi

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

Toumura: result above
... connected with KETI, Panasonic, Oracle, Fujitsu
... this diagram is automatically generated by some script using graphviz
... (shows the source code)
... issue on 3.2.2 read property
... Multiple form entries in single property. How can I select suitable entry from them? For example, if first form in the TD contains an URL which is accessible from local net only, remote clients (access from the Internet) must skip the form and search another form to access the Thing. I think it is useful to prepare some guidelines for implementing WoT stack.
... last part on use cases
... used KETI sensor and Panasonic bulletin board
... also Oracle simulator
... Panasonic Hue groups, Intel LED, Fujitsu beacon light as well

Kaz: can we ask Panasonic and Hitachi as well for demo scenario based on their experience?

McCool: yeah, let's continue the discussion during the next call
... would see node-wot scenario as well
... both industrial ones and home ones
... different application orchestration
... node red is also compelling
... also would see good semantic examples
... semantic search

[adjourned]