W3C

- DRAFT -

WoT-PF/Testing

19 Sep 2018

Attendees

Present
Kaz_Ashimura, Ege_Korkan, Michael_Koster, Michael_McCool, Kunihiko_Toumura, Tomoaki_Mizushima, Kazuakhi_Nimura, Toru_Kawaguchi, Ryuichi_Matsukura
Regrets
Chair
McCool
Scribe
kaz

Contents


<scribe> scribenick: kaz

PRs

PRs

McCool: one from Hitachi

pr 537

McCool: merged it
... and Panasonic

pr 536

<inserted> mm: merged

McCool: and Oracle

pr 538

McCool: another one from Panasonic

pr 535

McCool: merged
... Soumya's PR has a conflict

pr 506

Oracle's update

online plugfest preparation README.md

Lagally: format a bit messed

McCool: can add tweaks
... information on how to use the Oracle IoT Cloud Service

Lagally: please let me know if you have questions

McCool: (also adds comments (ask for information) to OpenVPN as well)
... and indicate how many IPs yu need

Hitachi

McCool: update from Hitachi

preparation-hitachi.md

Toumura: we'll provide an application

McCool: we'll you provide node-red configuration?

Toumura: yes
... you can create a node-red app easily
... source code for the tool
... you need to install node-red

McCool: ok, you can share your codes

Toumura: source codes on GitHub before the online plugfest

McCool: by an email from you?
... maybe we should create a subdirectory under the 2018-sept-online area?

Koster: anyone can copy the configuration
... you could generate a node based on TD as well

Kaz: it seems Hitachi would like to use their own GitHub area for that purpose

McCool: ok
... what about "3 Checking points for the next plugfest" section?
... any authentication method?

Toumura: basic, digest, bearer, apikey would be available

McCool: depending on node-wot implementation

Toumura: will try
... use cases still under consideration
... last part
... will write how to use this tool
... just draft text so far
... will update the description

McCool: which version of node.js

Toumura: ver 10

McCool: ok
... any questions?

Panasonic

preparation-panasonic.md

Toru: section 6
... implementation guidelines
... we have online things
... devices and simulators
... how to retrieve based on the token
... server and end point
... please use curl or postman to make request
... using the parameter here
... id and password have been sent by email from me

McCool: we have scopes
... restricts access
... willing to add an additional parameter for that purpose?
... so that we can test scoping

Toru: let me discuss with my colleagues

McCool: ok
... this is good for bearer testing
... questions?

Koster: this token you get is JWT bearer token standardized?

Toru: have not checked the details
... think it should be the standard one

McCool: there is a format parameter only for JWT
... so I think it should be JWT one

Koster: ok

McCool: update on TD as well?
... so far only Panasonic provides TDs

Panasonic TDs

McCool: 2 air conditioners
... cleaner

air conditioner

McCool: on and off
... (goes through)

Toru: it's really simple
... can show the temperature
... can get/set it
... using "number"

McCool: interesting

Toru: there is a range specified by minimum and maximum

bulletin board

hue light

McCool: supports bearer token?

Toru: yes

Kaz: how to control the temperature on the UI?
... absolute number?
... or +/- like usual remote?

Toru: absolute number for this app

Kaz: so we can specify 99 degree for this app :)

Toru: right

McCool: it's a number display now

Logistics update

McCool: time slot A
... too early for Europe
... but nobody from Europe registered
... so would suggest we move the slot by 3 hours and make it 9am JST

Koster: would be 5pm US Pacific, and that would be fine

McCool: (shift the times by 3 hours)
... that would make this more useful

Lagally: please remove "-1d" from some of the slots :)

McCool: how about slot B?
... delaying B by one hour?

Lagally: would be better

McCool: (shift the times by 1 hour)
... anybody expects attendance change?
... Oracle can remove "( )"?

Lagally: yes, please

McCool: removes "()" from Oracle's attendance

Lagally: tx

McCool: don't think Europeans participate in slot C
... also would remove Tuesday slot A
... let's create the remaining 11 webex meetings
... does someone want to set up Google Hangout meetings?

Daniel: anybody who has Google account can do that

McCool: can look into that

Lagally: anybody can join the call even without Google account?

McCool: not sure

Kaz: regarding the webex calls, how long should each slot be?

McCool: would suggest one hour

Toru: how about simply allocate a webex call for the whole day?

McCool: probably very expensive

Kaz: can check with the systeam
... and if it's expensive, let's have 1.5-hour calls

McCool: 1 hour + half hour to make sure

Kaz: and I can allocate additional webex calls if needed

<scribe> ACTION: kaz to ask the systeam about the cost of webex calls

Testing update

McCool: Ege, any update?

Ege: not much updated recently
... regarding the network testing bench
... security check for Lyon

McCool: ok
... command line locally

Ege: already available online

McCool: URL?

Ege: working on the eclisp server

Daniel: will check the IP

<ege> http://plugfest.thingweb.io/playground/

Ege: also command line version

Kaz: ok to record the URL above here on the minutes?

Ege: ok

Daniel: will update the service, so will check the HTTPS setting

Next meeting

McCool: slot B on Tuesday is the first slot
... talk to you all at that time

[adjourned]

Summary of Action Items

[NEW] ACTION: kaz to ask the systeam about the cost of webex calls
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/09/21 10:08:53 $