<kaz> kaz: has changed the setting of "wot" repo to use "master" branch for github.io rendering. if any problem, can revert the change
<kaz> scribenick: taki
McCool: Lagally and Sebastian are working on this
Sebastian: Siemens is happy to
host as previously reported
... end of May / start of June is good.
... keynote speakers are being decided
... then concrete dates will be decided
McCool: call for papers deadline?
Sebastian: not yet. will meet
with Lagally with that.
... will make announcement this year.
... we should avoid conflicts with other conferences such as
OPC-UA
McCool: let's create a wikipage to collect potential conflicts
Kaz: Github or W3C wiki?
McCool: GitHub for now is ok.
Kaz: do I create?
Sebastian: that will be great.
<kaz> ACTION: kaz to create an initial template for the 2nd WoT workshop
<trackbot> Created ACTION-149 - Create an initial template for the 2nd wot workshop [on Kazuyuki Ashimura - due 2018-12-05].
<Zakim> kaz, you wanted to mention we can create a dedicated mailing list like team-wotws, etc.
Kaz: I can create a mailing list as well for the workshop.
McCool: please submit if there
are issues. we want to publish it as final.
... are there any objections?
... motion to formally approve.
silence.......
McCool: I take it as approval.
RESOLUTION: TPAC minutes approved
Kaz: regarding the action items from TPAC minutes, I talked with Wendy Seltzer again. Got approval for making Notes for existing protocols.
McCool: MQTT and CoAP?
Kaz: Right
McCool: OGC sensorthingsAPI
... It is a good idea to test with it in next round.
... if not now.
... I might personally attend their meeting in Siggapore in
December.
McCool: Elena created a draft.
<kaz> PR 155
<dape> Rendered HTML of the updated Scripting API draft
McCool: Not enough turn around in
scripting call this week unfortunately.
... security and privacy consideration section was added.
(section 9)
... set of risks are described.
... not a normative statements.
... and mitigations.
... points out what the risks and requirements are.
... watch out for input validity, heavy processing, hygiene for
services, etc.
... subscribe for notification for TD.
... ID change in TD.
... therefore a need for subscription for TD change
... runtime security issues.
... security credentials should be separately placed.
... script should not have direct access to native
interfaces.
... any questions and comments?
Zoltan: scripting API is
normative even though it's optional.
... We should not talk about scripting runtime.
McCool: WoT architecture is also
normative.
... If we put it into Architecture, it will be normative.
Zoltan: Scripting API document will not describe scripting runtime.
McCool: I can add Editors note.
Zoltan: A lot of them are policies.
McCool: WoT architecture document should have security risks section, correct?
Zoltan: We can create a runtime Note linked from Architecture.
McCool: let's discuss further in
security call.
... The first part belongs to the scripting api doc, we can
agree today.
Zoltan: Runtime part will go into another document.
McCool: Architecture doc
ok?
... Matsukura-san, Matthias?
Matthias: It may blow up the content.
Zoltan: runtime concepts need to be introduced.
McCool: Let's discuss in security call.
(sebastian leaves)
<kaz> Proposed updated IG Charter
<kaz> Pullrequest 598 to add ECHONET to the External Organization section
McCool: There is a PR.
... PR about adding Echonet
... from Toru-san
... We have a rendered version.
... with diff marker.
Kaz: diff is with Matthias's original version.
McCool: chairs name need to be
filled in.
... People should take a look.
... Echonet was added as one of external organizations.
Matthias: list of deliverables is missing.
Kaz: section 3.
... we can change or even stay as it is.
Matthias: we can add things that were raised in Bundang meeting, for example.
<kaz> Current IG Charter
<mkovatsc> Matthias's slides at the F2F in Bundang
McCool is opening the PPT...
"Next Steps" slides from Bundang...
McCool: additional protocol
bindings, subprotocols.
... Directory service.
Matthias: WG slides talk about it.
McCool: we can make a maximal list, and discuss about what we do not want to include next week.
Matthias: Lifecycle, and servient management.
McCool: Based on Bundang slides,
we can make a list.
... any objections?
Kaz: Who will do it?
McCool: I can cut and paste into GitHub issue.
McCool creating a GitHub issue...
issue "New IG Charter Deliverable Topics"...
GitHub issue "New IG Charter Deliverable Topics"...
#599 in WoT...
<kaz> Issue 599 on proposed deliverables for the new IG Charter
McCool: collaboration with smart
cities business group, which does not exist yet.
... any other input on this?
... We need to finalize this very very soon.
... charter ends at the end of December.
... Should renew at the end of this year.
... If we can send it next week, we can make it this
year.
... we should get to agreement and finalize next week.
... By Monday, please send in comments.
<kaz> Pullrequest 294 on WoT Thing Description Test Planning document
McCool: I want to merge this in
TD repo.
... template class to give names to all tables.
... Let's discuss further in testing call.
McCool: We will have
proposals.
... Regular time slots can be used.
... December 10 week, monday and Wednesday.
... TD call should be left alone.
... question is is that good thing to do?
... any opinions?
... all meetings are evenings in Japan.
... have to have devices running in evening time in
Japan.
... is it a problem?
... not hearing any objections.
... I am going to assume that will be the plan.
... Let's discuss in testing call for logistics.
Kaz: Script/Security on Monday and Editors/Main/Testing slots on Wednesday and then wrapping up during the TD call on Friday. correct?
McCool: yes. we will discuss more
in testing call.
... small group of us will discuss the details including
Ege.
... All implementations will need to be up and ready to
go.
... TestFest at least need to every implementators and TD
editors at the minimum.
... we want to streamline testing process, and generate a
report this time.
McCool: Sebastian is
gone...
... any updates Matthias?
Matthias: Monday-Thursday.
... OpenDay may be good in East Coast.
... Doodle poll will be done.
McCool: Which days?
Matthias: will check emails.
(checking his emails)
Matthias: 28 Jan-2 Feb / 4 Feb-9 Feb
<McCool> 28 jan - feb 2
<McCool> 4 feb - 9 feb
<McCool> those are the options
<McCool> .. kaz, please set up a doodle
(some more chats)
<kaz> Kaz: just to make sure: (1) Jan 28-Feb 2 vs (2) Feb 4-Feb 9
<kaz> McCool: right
McCool: two options
... additional items?
... testing call after this call.
... Please call in after 10 minutes.
... will discuss logistics etc.
... Implementors please call in.
... Thank you.
<kaz> [adjourned]