<inserted> Jan-27 minutes
McCool: any objections?
... only one typo on "clearer"
... accept them?
(no objections)
McCool: the minutes accepted
McCool: done for version 1.0
... (closed)
McCool: we did add references to ISO
specs, etc.
... may want to re-open a new issue for ver. 2.0
... (closed)
McCool: still open
... need to deal with it after defining suitable "streaming
data"
McCool: where is this issue
from?
... let's look into the fetch spec
McCool: (also looks into the WoT Security Guidelines)
WoT Security and Privacy Guidelines
McCool: don't think we've discussed
origin things
... still a "live" issue
... we don't actually reference CORS or Fetch in the Security
Guidelines document
... not clear where to put them
McCool: signed TDs
... we don't currently specify a signed packaging mechanism for
TDs
... relates to the issue of discovery
... leave this open, and assign to myself and Elena
... (adds the "Discovery" label to this issue 51)
... (also creates a new issue on "Scripting API for
Discovery")
<inserted> new issue 160
McCool: don't think this is a high
priority right now
... (closed)
McCool: feeding into the discovery design
McCool: related to issue 148
McCool: we need clearer definition of
"authentication", "Authorization", etc.
... would be good to have more specific issues
McCool: need to better document the
requirements for different security schemas
... schemas based on standards (OAuth) are pretty clear but the
more generic ones (PSK) need a little more explanation
... marking this as a TD issue as such explanations and
definitions should probably in the TD spec
McCool: relates to discovery
... also relates to the definition of "authentication",
etc.
(see also issue 148: https://github.com/w3c/wot-security/issues/148)
McCool: let me assign this to
myself
... for next meeting, we'll concentrate on the rest of page 1
issues
[adjourned]