<scribe> scribe: zkis
Zoltan: New member, Jack Dickinson from Connexus
Jack: introduction
Followed by short introduction round.
<kaz> Oct-12
Zoltan: we were dependent on JSON-LD WG for publication
Kaz: we can update the Notes after those are published
Daniel: maybe we should leave as it is, without versioning
Cristiano: we can point to the spec and the content file
Past minutes approved.
Zoltan: should we wait for the versioning issue to settle?
Daniel: we didn't have that before
and it was fine
... also, if we rush, it might change later
... so I'd go for publication
Cristiano: should we also change the name?
Zoltan: we are not tied to JSON-LD, so not
TPAC schedule: https://www.w3.org/2020/10/TPAC/group-schedule.html
Kaz: we should get the group approval on Wednesday 21 October and then publish it
Zoltan: so we should have a slot on that meeting
<kaz> current draft
Kaz: also, we need a resolution from the TF
RESOLUTION: the Scripting TF agreed publishing the updated Scripting API Note.
Daniel: do we have a WG call this week?
Kaz: no, but we can ask the
Chairs
... during the WoT vF2F meeting
Daniel: the slot is on Thursday
<inserted> Scripting API slot on Oct 22 during the vF2F
Zoltan: are we fine with "WoT interface"?
Cristiano: yes, but we need to update the spec
Zoltan: can we close this?
Daniel: there were something open
Zoltan: that was on the TD TF, not
related to Scripting
... to provide a mechanism to define specific Events for
protocol errors
... do we have the issue open in the TD spec?
... or it may be a TD _content_ issue, then it's not a TD spec
issue
Cristiano: there was a related
discussion in Discovery TF as well
... will add the link later and we can close this issue
Daniel: I could sweep over the issues and clean up.
Zoltan: you can close it after inspecting and making sure the issues have been tackled
Zoltan: we have already taken into account the Generic Sensor design from early days
Cristiano: Ege is referring to a previous issue that's been closed
Related issue: https://github.com/w3c/wot-scripting-api/pull/235
agreed to close the issue
https://w3c.github.io/wot-scripting-api/#dom-discoverymethod
Zoltan: we have "local", so we can close this
Cristiano: it is not implemented in node-wot
Daniel: the whole discovery part is not implemented
Zoltan: should we introduce a new "direct" keyword to DiscoveryMethod?
Cristiano: I like that
... however, url alone is not good enough
... there are many kinds of URLs
... we could describe the direct discovery to each binding
Zoltan: yes, it works that way: the API describes the use case, the impl/bindings figure out the way
Cristiano: we should add a section to the Binding Templates as well
Zoltan: right, it needs to be defined
in detail
... will track that use case in the Discovery TF
... meaning the URL patterns
Cristiano: URLs should be opaque in the Discovery TF but I see the point
adjourned