Meeting minutes
previous minutes
<dape> https://
Daniel: there were two minor typos
Kaz: fixed
zkis: this time slot is a little bit difficult to me
Daniel: we could change it
zkis: we could move the call between sec and discovery
cris: it is ok for me
Kaz: I have another meeting at that slot
Daniel: ok then
Daniel: let's discuss this offline first
Issues
issue 219
<dape> Issue 219 - Discussion about read- write-/multipleproperties
Daniel: we discussed about the convience of having readMultipleProperties operations in scripting
Zoltan: we should support protocol features and not simulate them when we can
Daniel: I had an use case for retrieving only a small set of properties
… not sure if there are other use cases
Jan: yeah retrieve multiple sensor data might be another
… the problem is that there's already an example about how to indicate which properties you are looking form
Daniel: the td spec might be a little bit not clear
cris: it might be a non-issue right now
Daniel: there is no issue on the TD
cris: why do we have the issue open?
Daniel: we drop the operation a while ago
… we are missing something
… what is happing when we don't pass any property name?
Jan: in the scripting API are we interating through the properties?
Daniel: no we retrive all with one request
Zoltan: we want to give devs the opportunity to optimize network interaction
Daniel: what I think is missing is also a writeAll reference in WriteMultiple
Zoltan: having writeAll in scripting API might be difficult cause we might need to check if the input contains really all the properties
… we should pick a clear semantic in the TD spec
issue 354
<kaz> Issue 354 - Conformance section necessity
Daniel: any news about the conformance section?
Kaz: I'm waiting
issue 360
<kaz> Issue 360 - Consider moving terminology definition to WoT Architecture
Zoltan: Michael wants to move Interaction to the Architecture document
… we use it as a colloquial term to refer to Interaction Affordance
Zoltan: probably we need more discussion with him
issue 355
<dape> Rename Use Cases section,
Daniel: long discussion, maybe we talked about renaming the Use Case section
… Michael's opinion is that this section is conflicting with the Use Case document
… we look at different options
… but now I'm a little bit lost
Jan: it doesn't seem to really conflict
Zoltan: they are from different contexts
… IMO is not a problem
… if it might confuse people we can use Scripting Use Cases
Daniel: we resolved to put a text and link to the main document
Kaz: I'm asking Phiippe about these issues, I'll ping him again
… let's wait
issue 361
<dape> Should we publish TS types also for ThingModel?,
Daniel: we are publishing types for scripting api and td types
… it is not real work from our side is just pushing the types to npm
… at the moment we are ignoring TM completely in the APIs
… any feedback
cris: I would appreciate to have the types
Daniel: I'm ok of having this
Zoltan: we might need an explainer to clarify why we have this folder
… it can be a md file
… it should contain a developer friendly explanation about it
Daniel: please head over issue 352 if you have any idea about next charter topics
… should I put TMs there?
<kaz> [adjourned]