<scribe> scribenick: kaz
McCool: don't see any problems
... objections to accept the minutes?
(no objections)
McCool: accepted
McCool: Taki can't make Monday
... any preference on the slots on Monday?
Elena: no preference
McCool: prefer the later time
Kaz: me too
McCool: so let's go with 7am JST
<scribe> ACTION: kaz to allocate a new webex and distribute it for the next week
Kaz: will do
McCool: after talking with Taki, we might be going to change the slot again
(Zoltan joins)
McCool: Zoltan, we were talking about
the new slot for the Security call
... (explains the situation)
Elena: it's 1pm in Finland
Zoltan: ok
... fine by me though might be a bit late
<McCool> https://github.com/w3c/wot/blob/master/charters/wot-wg-charter-draft-2019.html
McCool: the initial PR (PR 856) has been merged
http://w3c.github.io/wot/charters/wot-wg-charter-draft-2019.html
McCool: rendered version above
... as far as security goes
... topics on security within "2. Scope"
... also Interoperability Profiles
... Discovery
... need to work with the Privacy group
... security aspects for Implementation View Spec as well
... 2.6 Discovery
... we have to define deliverables
... possibly break out into 2 pieces
... introduction and exploration
... peer-to-peer discovery could be supported as a special
case
... have to coordinate with IETF, etc.
... need more general context here
... 2.7 Identity Management
... Kaz mentioned there is a proposed WG named the
Decentralized ID WG
... should collaborate with them
... kind of like ID management lifecycle
... e.g., please notify me when the ID management changes
... device with right access to be handled
... we have a deliverable down here ("3. Deliverables")
... we need to create repos for those deliverables
... would like to start soon
... Michael Lagally is generating draft as well
... any comments?
Zoltan: discovery for WoT?
... do we want to define ourselves?
McCool: good point
... have predescribed script
... in fact we're doing how to distribute things
... because existing devices don't distribute TDs
Zoltan: distributing script as well?
McCool: may be
Zoltan: some kind of manifest of
something
... some kind of package
McCool: bunch of things that are
listed as "Notes"
... normative deliverables are extracted from the powerpoint we
discussed in Munich
Zoltan: was there any deliverable which can be included as Note?
McCool: hold on...
... (shares the powerpoint slide from Munich)
... other things used to on the REC track
... essentially deployment model and packaging
... WG Charter can be changed later
... what we should do is
... if you think deployment/packaging mechanism for Scripting
would be useful, you can create a PR for that proposal
... the current list is generated from the powerpoint in
Munich
Zoltan: ok
... some provisions to associate things
... should be contained to Scripting distribution mechanism
McCool: 2 kinds of dependency
... NPM kind of packaging
... and function
... query mechanism and installation mechanism
Zoltan: we don't have to re-invent generic distribution mechanism
McCool: packaging of script
... there is dependency
... 2 parts of manifest
... very interesting
Zoltan: let's say I discover things
and would know about the capability of scripts
... up to the clients
McCool: please review this draft
Charter
... and also proposals from Michael Lagally
(Elena leaves)
McCool: what is the right context to
handle the context?
... have been talking about the orchestrator
... e.g., Panasonic, etc., use node-red
... we could add another deliverable for management
script
... need context for interoperability
... just like profile, we need draft text which describes the
context and the basic architecture
... would be useful to do
... personally started to think Scripting API could be a Note
by the IG
... IG should be incubating the requirements
Zoltan: it's specific to node-wot and typescript
McCool: we could add management
API
... with packaging capability
Zoltan: JS is the language supported
by Web browsers
... that might be one way to go for something like Web
Assembly
McCool: what to be contained for
packaging?
... those things could be interesting
Zoltan: right now we have JS
runtime
... there are some issues to tackle
... it's something would make sense
... but not directly related to WoT
McCool: if we go for more general
mechanism for packaging
... need a draft text to be included in the draft Charter
... need same thing for packaging and/or management API
Kaz: it sounds like
object-oriented programming
... how to combine the TD model and Scripting API as a possible
method for the data model
McCool: would create an issue about this point
<McCool> https://github.com/w3c/wot/issues/861
McCool: WG Charter issue above
... also it would be nice to have a specific repo for the
wot-discovery discussion
... will generate a draft first
... and let's have discussion during the main call
Zoltan: regarding the above Issue
861
... we need use cases to motivate it
McCool: ok
... (adds comment on that point)
... why don't you add your comments to this thread?
Zoltan: ok
[adjourned]