<McCool> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#23_Jan_2019
<scribe> scribenick: kaz
Lagally: had a call one hour ago
... workshop cfp draft reformatted
... applied an appropriate css
... also talked about picture at the top
... and diagram of wot including several industries
... draft picture provided by Victor
... primarily discussion
... should be modified a bit
... to add cloud
... good starting point
... maybe a picture from the arch draft as well
Lagally: in addition, Sebastian gave some high-level agenda
Lagally: 27 May openday
... 28-29 workshop
... different companies to have demos on openday
... also invited keynote speakers
... from Siemens
... would check within Oracle as well
McCool: would see keynote speakers
Lagally: need to get official approval from W3M
Kaz: working on that
McCool: discussion during f2f?
Lagally: yes
McCool: any more quick updates?
Lagally: none
McCool: goes through the wiki
... who to speak what?
... still reasonable to have only 30m for architecture?
Lagally: a bit short in the end
McCool: makes it 60m
... sebastian, what about TD?
Sebastian: identify issues, etc.
... what to solve, etc.
... need consensus
McCool: in that case, 120m
minimum
... and
... TestFest stuff
... I can lead that
... relatively short
... 30m
... what would be features at risk?
... Elena for security testing results; 30m
... rechartering discussion
... 6month extension for WG and IG
... will lead this
Kaz: talking with W3M about IG extension
Matthias: please have the session on rechartering at some time I can easily join
McCool: ok
Lagally: note on sat
... some of the attendees might be going to leave earlier
McCool: maybe all the items for sat can be by noon
Lagally: would be good
... maybe we can start earlier?
Koster: have hard stop at 3pm
McCool: will add people's constraints
here (on the agenda wiki)
... Elena, Zoltan, Daniel and Matthias
... CET; can attend up to 3pm
... want to finish by noon on sat
... Thursday
... rec track: arch (60m), td (120m), scripting (60m)
... notes: binding (60m), security/privacy (30m), security test
(30m), security bp (20m)
Sebastian: we should spend some time for binding as well - td for 240m
McCool: add "organization" at the beginning of thu
Lagally: arch for 120m
McCool: openday
... speakers from NIST and OGC
Sebastian: we'll have testfest in the
morning
... how long would it take
... also lunch time
McCool: starting at 1:30pm then?
Sebastian: would be careful about changing the time now
McCool: goes through the registration results
Kaz: George Percivall from OGC as
an invited speaker
... and 2 guys from Toshiba are observers
McCool: ok
... and approved
Lagally: had a call today
... a couple of proposals for the doc
... created a word doc based on the changes for review
... one from Toumura-san
... Kawaguchi-san
... and Matsukura-san
... editorial changes from Ari
... also security proposal from Elena
... extended deadline by Friday
... any proposals welcome for the f2f discussion
<mlagally_> https://github.com/mlagally/wot-architecture/blob/master/proposals/diff%20with%20all-PRs.docx
Lagally: feel free to take a look at
the above integrated change doc
... will work on the branch to merge the changes
... also will merge Oracle proposal
McCool: ok
Lagally: and we want to use the first 30m from the TD call for the final review before f2f
McCool: discussion about browser or not
zoltan's question (member-only)
Zoltan: node-only description is not
good for browser implementation
... would like input from people
... first from the group
... expectation from the scripting spec
... the way forward would be making it a group Note
... can be an NPM document maybe
... however, we could make changes to make the spec draft
better fit browsers
... generated some presentation slides (URL within the above message)
... is there an opensource implementation?
... we have a number of participants in the group
... would ask for opinions
McCool: how to proceed?
... can generate some formal questionnaire?
... main question and subsidiary question
... today or tomorrow
Zoltan: people are implementing
WoT
... would like to know what kind of scripting mechanism people
are using
Kaz: I can create a WBS questionnaire if the questions are clear
Zoltan: can send questions and options
Kaz: also we can talk with W3C Management guys like Philippe
Sebastian: did some changes for TD
model
... default value, etc.
... major changes from last week
... how to set up tests?
... Ege may have insight
... set up some configuration for next week
McCool: testing details for the next
hour
... bunch of issues on duplicated IDs
Ege: people can check things
manually
... and automatic tool also can be updated
McCool: talk about the details during
the test call later
... data schema for payload, etc., to be reviewed
... one question, extended assertion section for the TD
draft
... discussion at f2f
... did data schema assertions as well
... Koster might want to look into protocol topics
... anything else?
(none)
McCool: got a liaison letter
... need to look at that
... people are also welcome to review it
... review during f2f as well
McCool: any update?
Koster: no
McCool: some discussion on one data model on Sat
Koster: that's fine
McCool: not much report
... other than test plan by Elena
... first look during the f2f next week
... testing plan deliverable as a separate note
... document testing procedure and appropriate tools
... we need actual implementation
McCool: anything?
(none)
[adjourned; convene in 10mins]