PlugFest schedule

Plugfest wiki

McCool: let's confirm if these slots are still OK by all

<scribe> ACTION: kaz to create a doodle to see if the proposed slots are still OK by all

McCool: what about the registration site?

registration site

McCool: the date within the title to be fixed

Kaz: will do

<scribe> ACTION: kaz to fix the date within the title of the registration site

McCool: next thing to talk about
... we should collect topics for the f2f part

<inserted> F2F topics

Ege: any open day this time?

McCool: what does "open day" mean this time?

Ege: have some people in my mind to invite

Kaz: we can add a section to the f2f wiki about possible invited guests

McCool: and we should make decision in advance
... note that we have pretty tight schedule this time

Kaz: before adding actual candidate names to the public wiki, we could have preliminary discussion on the Member list

McCool: yeah
... on the other hand, don't want to use much time for invited guests since we have limitation this time as I already mentioned
... let's discuss that during the main call

PlugFest topics

Plugfest logistics

McCool: some topics listed here so far
... Ege, what about binding templates?

Ege: nice to talk about that

McCool: 1h enough?

Ege: yes
... investigation of ROS, etc.
... by 15m

McCool: ok
... 1h + 15m for you
... what about you, Lagally?

Lagally: use cases for 2h
... and profiles for 2h

Danie: API changes for scripting?

McCool: will you talk about that yourself?

Danie: or Zoltan

McCool: 1h enough?

Danie: yes

McCool: regarding security
... review issues including OAuth2 should take 1.5h
... and plugfest report for 1h
... anything else?

Ege: TD topics like TD template?

McCool: tentatively put 2h for TD
... discovery has 1h
... got some progress on the agenda

Prototypes/Proposals

Prototypes and Proposals

McCool: test of device flow for OAuth2?
... need to go back and read the docs/specs again
... should keep consistency with open api

Danie: code flow is similar to this. right?

McCool: how to deal with credentials to respond to actual person
... need to read the spec

Farshid: possible m2m coordination as well

McCool: which flows make sense for IoT?
... any other protytypes, ideas?

Danie: look into eventing
... and dynamic TD creation
... which offers more capability
... could be part of "Hypermedia Controls"

Ege: yes

Kaz: if you want, we could add a sub-bullet point explicitly

McCool: we have MQTT protocol binding?
... any implementation?

Ege: yes
... within node-wot

McCool: note that there is a difference between the "Prototype section and the "PoC" section
... topics on the "Prototypes" section are expected to be included in the specs (directly)

Testing

Testing

McCool: we're not really sure about what to be tested this time
... need to add clarifications

Kaz: so people are encouraged to add their ideas to the "Testing" section as well

McCool: yes
... there are multiple purposes this time
... should clarify the features to be tested this time
... and then scenarios

Use cases ans scenarios

McCool: several question marks here
... for example, what kind of scenario is expected for "Smart Agriculture"?

Matsukura: some demonstration is available

McCool: demo is mainly for TPAC. right?

Matsukura: yeah

McCool: smart store is still in-flight
... smart agriculture topic is brought from Singapore as well
... so your introducing your scenario to them would be helpful
... also I could work on a possible scenario on "buying an ice-cream" for smart store
... (puts some ideas)

Kaz: so you'd like to ask Matsukura-san to clarify some possible scenario like that, wouldn't you?

McCool: right
... (shows his slides on Conexxus collab presented the other day)
... for example, a camera put on the store
... and freezer door opens based on the sensor
... and then various things there
... so would be great to have some scenario like this
... for smart agriculture use case
... e.g., temperature sensor, weather forecast, ...
... assuming those things talk with the smart greenhouse
... we should document a possible typical scenario within the use case template itself as well
... what the person does, etc.

(who/when/where/why/what/how)

McCool: and how to populate the data
... adapting the functionality to the store in this ice-cream use case
... maybe could replace some of the features
... so what I'm asking Matsukura-san is adding links to the existing materials first and also clarify the scenario (=what happens when)
... make sense?

Matsukura: yes
... will generate a possible scenario then

McCool: great
... would let you do that then

WISHI workshop

WISHI workshop part

McCool: met with the WISHI guys
... expected speakers here

requests to speak

McCool: Michael Lagally for use case process and overview
... Henry Andrews for JSON Schema
... note that we only have 3h for the workshop
... there are still 30mins left
... if someone has a topic for 30mins, please let me know

AOB

McCool: aob?

Ege: playground is getting updated but not before the plugfest this time

McCool: in that case, need to use the current version?

Ege: right
... will fix bugs
... but won't add new features yet

McCool: you can use playground as of today
... will work on the preparation topics
... anything else?

Farshid: what about directory service?

McCool: the question is if you're planning to talk about something
... would be happy to have you talk about LinkSmart work
... maybe talk about it as part of the "WoT Discovery" during the WISHI workshop
... (adds a "20+10m" slot for that)

Kaz: Farshid, are you interested in presentation? or plugfest?

Farshid: could do both

McCool: this presentation itself is for the WISHI workshop
... exposure for the IRTF guys as well
... and as far as implementations, should be handled as part of the PlugFest
... should describe where/how it works
... once your setting is done, wold be great to put the information

Farshid: would like to talk about the detail during the discovery call next Monday

McCool: ok
... (tentatively adds a talk on discovery to the WISHI workshop)
... will make sure about the logistics for the workshop

[adjourned]