Meeting minutes
approving previous minutes
<dape> https://
no objections
<dape> https://
Daniel: note that we discussed what to do in the next charter, to be tracked in an issue
ACTION: DP creates issue for tracking charter changes
no objections
Daniel: last week we had joint call with Security TF
<kaz> Nov-8 Security call minutes
https://
Zoltan: we discussed onboarding, provisioning, discovery, management APIs, etc. See issues in the minutes.
Daniel: will list these for the new charter
node-wot release
Daniel: we are publishing a Note and then update node-wot
… but at the moment no need for an updated Note
PR 350
<dape> https://
Daniel: related to the link checker
Daniel: the PR fixes the broken links and typos
<dape> Broken fragments: https://
Daniel: some of the errors were false
Kaz: we should generate a static html first, only then apply the validator
… There might be some option for that purpose, but, need to consult the validator checker doc
Daniel: suggest merging this PR and then do the rest separately
Zoltan: fine with that
Daniel: merged
ISSUES
Clarify multiple requests for subscription/observation
<dape> https://
Cristiano: when we subscribe, should also record how to unsubscribe
Daniel: this as also discussed in the TD TF,
Cristiano: but it's not yet in the spec, may come only in the next charter
Cristiano: it's about choosing a Form for unsubscribe
Cristiano: implemented a scorer algorithm for determining how to unsubscribe
… but we should change the TD spec to link the unsubscribe Form
Daniel: can we subscribe via HTTP and unsubscribe via CoAP?
… how should it work?
Cristiano: we don't have practical use cases for that, but I think we should have the same binding
Zoltan: I agree, also for security reasons
Daniel: there is no statement to prohibit this use case
Cristiano: it's a validation problem
Cristiano: the TD should be invalid if it didn't have unsubscribe Form
Daniel: right now the matching algorithm could possibly use the Form from any binding
Zoltan: IMHO we should create an issue to track this, and update the algorithms in Scripting, to be precise
<dape> https://
Daniel: this depends on the TD TF to solve.
https://
subscribeEvent and observerProperty misaligned signature
<dape> https://
Cristiano: we can track this problem in a dedicated issue
<dape> https://
Daniel: then we also have an issue about the multiple subscriptions
<dape> https://
Cristiano: currently if subscribed, the next call will fail
Zoltan: that is good enough for now
Daniel: time is up, continue next time
<kaz> [adjourned]