W3C

WoT PlugFest

14 April 2021

Attendees

Present
Ege_Korkan, Kaz_Ashimura, Kunihiko_Toumura, Michael_Koster, Michael_McCool, Philipp_Blum, Tomoaki_Mizushima
Regrets
-
Chair
McCool
Scribe
mjk_

Meeting minutes

agenda bashing

<kaz> agenda

minutes review

<kaz> March-10

McCool: no objections, minutes published

review plugfest report slides

<kaz> Plugfest slides

vF2F minutes

<kaz> vF2F minutes

McCool: any objections or corrections ?

<McCool> flattening

McCool: noted some typos for correction

McCool: no objections noted, allow one more week for final review

testfest

McCool: how many implementation reports?
… profile, architecture, TD, and discovery
… we need four separate plans
… testing gaps are OK if the plan addresses how to resolve the gaps
… the gaps need to be resolved by September 1st

Ege: we should document the things that are more at risk

Ege: can we make a short list? new security scheme and pointer resolution scheme

McCool: discussion of result file locations

Ege: we need to discuss the discovery testing more

McCool: one issue is the two types of queries
… we need two implementations to support both query types

Ege: what about service discovery on the LAN?

McCool: we can manually test service discovery

McCool: we can cross-test using one implementation tests on the other

Ege: what about profile testing?

McCool: it could be a TD test extension

Ege: we could change the logic of the assertions in the TD test

McCool: there are additional assertions and need to figure out how to mark profile TDs

McCool: (discussion of schedule for resolving issues over the summer)

<Ege> https://github.com/w3c/wot-profile/issues/74

Ege: need to mark the test assertions in the spec documents

McCool: there is a css class for assertions

McCool: need to sync up mid-August

Ege: not available most of August and September

getting started tutorials and example implementations

Kaz: need to fix the URI for the doodle poll

<kaz> for the June Testfest.com/poll/mzv9x5rxsdmub5u3 doodle

McCool: need something besides the coffee pot that has actual hardware
… examples to show how WoT is useful
… also coverage of features in WoT
… temperature sensor, door sensor, buzzer, light?
… what are the hardware options? Raspberry Pi or M5Stack/nodemcu
… http or coap?

Ege: already replied and have some examples based on ESP nodes

<Ege> https://github.com/tum-esi/wot-sys/tree/master/Devices/ESP-lightsensor

<Ege> https://github.com/tum-esi/wot-sys/tree/master/Devices/nodewot-sensehat

<Ege> https://github.com/tum-esi/wot-sys/tree/master/Devices/ESP32-ledSwitch

McCool: what is the stack used on ESP?

Ege: micropython and HTTP

Philipp: had difficulty with the riotOS on windows, not for beginners

McCool: the M5Stack HW uses the Arduino IDE

McCool: we should also offer a node-wot version

McCool: there will be a delay in publishing the mccool examples, maybe Ege has something

any other business?

McCool: please fill in the doodle poll for the June testfest

McCool: adjourn

Minutes manually created (not a transcript), formatted by scribe.perl version 127 (Wed Dec 30 17:39:58 2020 UTC).