Meeting minutes
Agenda
<dape> https://
Previous minutes
<dape> -> September-26
No objections, minutes approved.
quick updates
Daniel: we discussed changing the document so that the Note could also include normative statements
Daniel: wondering if there are any pushback from W3C
Kaz: the process doc defines just Rec track. Note track doc may include normative statements.
… anyway, we needed to clarify the status of Scripting in the new WG charter
Kaz: not yet discussed with Philippe
… he will ask on the WoT WG decision, so we did need the group resolution on that
Daniel: yes, we have that
Kaz: we should prepare for comments from other W3C members
Kaz: I am not sure why we want a normative Note, since that would require AC review, comments, etc. Should we try to make the Scripting to make normative Rec track doc again?
Daniel: we need the normative statements, but we don't need to go to Rec
… we are still in the exploratory phase, the API is not stable
… maybe in the future, but not sure about that yet
Zoltan: does it mean we can only use MUST, SHALL, etc with AC reviews?
Kaz: no, I just meant a normative deliverable for Scripting
Zoltan: we can stick to the group decision already made
Daniel: so far it has been accepted that we use normative statements
Cristiano: I also think we should stick with the group decision
… if all goes well, we might end up in the Rec track, but for now we can stay in the current state
Wot Profile test fest
Daniel: if anyone was present, any takeaways for Scripting?
Cristiano: I joined nearly all calls
… the general feeling is that Profile is not mature enough yet
… but they will try to finish it in the next months
… there was some implementation attempt, not yet finished
… some tests as well
Cristiano: no dependencies for Scripting
… we might look into action operations which we don't support
… maybe we should look into that
Kaz: look into the minutes of the test fest
(link)
Kaz: some takeaways for TD, Michael McCool will summarize the findings in this week's calls (discovery, profile, architecture, ...)
Daniel: thank you for the summaries
Daniel: CA's point (query action) is something we should do in the next charter
… the TD needs to improve wrt the OP values and align with Profiles
… so cancel/query actions are underspecified
… after that is solved, we can update the Scripting API
… but it will likely go into the next charter period
… since it also needs a plugfest where we can test those ideas
pull requests
PR432
<dape> PR 432 - refactor: fix/remove emphasised empty #432
Daniel: fixes a typo
… we discussed to use "empty" without emphasis
<cris_> +1
Daniel: can we merge?
PR431
<dape> https://
Daniel: fixes a typo
Merged.
PR434
<dape> PR 434 - feat: adjust ThingFilter interface
Jan: last time we discussed to move out some changes to a new PR
Jan: this could clear the way for accepting the other PR
Daniel: are these dependent?
Jan: no, they are independent and should be discussed separately, hence the new PR
Jan: so PR 405 could be taken further
<kaz> PR 405 - feat!: add new Discovery Web IDL definitions|
Cristiano: there are some mistakes, like if the filters are now mandatory
Cristiano: I agree we move the async iterator forward and discuss the rest later
… maybe we should move that line out as well (which removes optional from the filter arg)
… apart from that we can merge the async iterator change
Jan: OK, the PR is updated
Daniel: nice - in rest, the PR has been reviewed, so we could merge that
PR 405 merged
Cristiano: we can handle the rest in the new PR
Issues
issue 433
<dape> Issue 433 - New publication within current charter?
Daniel: it's about what to publish in the current charter
Daniel: I think we should make a release
Zoltan: the async iterator is enough reason to publish
Daniel: yes, but we should not update the OP values
Cristiano: I agree with this. We should also finalize the Discovery chapter to align with the Discovery TF.
… also, update node-wot
… after that we can publish
Jan: regarding discovery implementation in node-wot is going well, should be able to finish in next months
… also experimented with bootstrapping, security
Cristiano: what about test results
Jan: there were some, but need to update them
Cristiano: MMc asked to finalize them
… security bootstrapping is not specified well
Daniel: thank you
issue 430
<dape> Issue 430 - Define exact steps/algorithms instead generic references to "Protocol Bindings" spec
Daniel: we need to rely on dependencies on Bindings spec
… which is not ready yet
Zoltan: we need to define those algorithms, eventually temporarily in Scripting, then move them to Bindings
Kaz: we should clarify which portions are to be included in the Bindings spec
… my suggestion is to discuss with TD spec guys
… at least in this chapter
Zoltan: in that case we can keep it in Scripting until the Bindings spec is ready to take them
Daniel: makes sense
Daniel: it's also fine to leave it open and wait until properly defined
Zoltan: should we cover it for HTTP, eventually CoAP?
Daniel: need to adjourn
call adjourned