Meeting minutes
Minutes
Jan: I had a problem with Firefox for HTML diff last week
Kaz: fixed
minutes approved
Logistics
Cristiano: reminder that (1) Scripting API call is now bi-weekly and (2) US Daylight Saving has started
… we can cancel the call on Apr-1
… then April 8 also due to the AC meeting
Kaz: btw, we should be clear about the "bi-weekly policy" as the basis :)
… no call on Apr-1 or 8. right?
Cristiano: right
RESOLUTION: Scripting API TF will not have the TF call Apr 1 or 8
PRs
PR 545
<cris_> PR 545 - feat: expand exploreDirectory algorithm
Jan: no real update so far
… just want to push one commit
… started to define some kind of dictionary
… minor change so far
… should have some more discussion
Cristiano: tx
… think the direction is good, and would see the final resolution
… let's have more discussion
… any opinions from Zoltan?
Zoltan: not really
… still a bit vague
… general thought is already described but need to think about how to implement it
… should be aligned with the Discovery work
… would ask the Discovery TF for review also
… after Jan makes clarification
Kaz: this is related to the "inter-TF collaboration" discussion
… you can mention your need about the review during the main call also
Cristiano: any conclusion about the "inter-TF collaboration" discussion?
Kaz: still ongoing
… so you can mention your need during the main call
… maybe we might want to think about the mechanism for the Wide Review for sepcs on GitHub
Zoltan: right
Kaz: but let's have discussion during the main call first
Issues
Cristiano: no new issues this week
… but have many remaining issues
Cristiano: need to think about how to have discussion with related TFs
Kaz: this is also related to the "inter-TF collaboration" discussion
… but some of the issues are already identified as "bug"s
… so we can work on those issues first
Cristiano: that's true
… also maybe it might be a good timing to think about how to deal with use cases too
Kaz: we should join the UC discussion for that purpose
… they're working on the updated procedure and the improved template
… but at some point, Mizushima-san can make some debriefing at the main call also
Cristiano: good point
… we might want to start with error handling
Kaz: there are several issues about error handling. right?
Cristiano: yes
<Zakim> kaz, you wanted to react to kaz
Mizushima: it's important to clarify what Scripting spec describes
… use cases are useful to understand that too
… so would suggest we (=Scripting TF guys) join the UC discussion also
… note that not many people are really aware of the Scripting API discussion as a whole
… clarifying concrete use cases would be helpful for people to understand what is expected for Scripting APIs
Cristiano: agree
… Jan, can you join the UC call?
Jan: have some conflict at the moment
Cristiano: would try to join the calls more
Kaz: yeah, Scripting API itself is clear enough but how to improve/update it is a bit vague
… so providing concrete use cases about our expectation would be helpful for people (including myself) to understand the points
Cristiano: right
… regarding "error handling"
… let's describe possible errors first
Kaz: that can be a good starting point
… but at some point, we need to think about the interface between the "WoT World" and the "External IoT World" as well
… what would be the impact to TD and Scripting API caused by the errors from the outside of WoT
… and also what would cause potential errors of the external world based on the errors of TD and Scripting API
Cristiano: right
Versioning
Cristiano: we're still waiting for the conclusion from the main group
… based on the work on TD and Discovery
Kaz: the discussion by TD TF and Discovery TF is still ongoing
… but the TD TF should be able to bring their initial proposal back to the main group next week
AOB
Jan: there was an issue around Discovery
Issue 535 - Dedicated methods for DNS-SD, CoRE Link-Format discovery, and other approaches?
Cristiano: what about adding a label of "high-priority" to the issue?
Jan: maybe "middle-priority"?
Cristiano: let's discuss this issue next time anyway
[adjourned]