Meeting minutes
Minutes Review
Ege: any remarks?
Ege: minutes approved
Use Cases
Ege: anything to talk about use case process
Kaz: mjk wants some clarifications
… you can find it in the minutes and we can talk next week
TD Spec Work - Analyses
Data Mapping
<kaz> analysis-data-mapping.md
<kaz> TD Issue 2094 - Collecting Analysis on Data Mapping
Ege: I will put the issue links
Ege: How to proceed the best way
Daniel: I want to work on as I am interested in XML
… but no progress so far
Luca: data mapping and initial connection are related
… do we have consensus on the problem
Luca: (describes the problem)
<kaz> WoT Thing Description ED - Example 32
Ege: (put comments about the points)
… Daniel will look into the XML
… Luca will look into the HTTP header/query params and CBOR maps
… what about you, Cristiano?
Cristiano: also interested
Ege: myself will look into Modbus and Profinent
Initial connection
Issue 2093 and 2102
initial-connection/tooling/tds.js
TD Issue 2093 - Initial Connection Container Parsing
TD Issue 2102 - Clarifications for Initial Connection
Ege: should we allow security to be expanded as well?
Daniel: same concern about scheme not being understandable with beginners
Luca: this is a complicated case I think. It is not easy to compose
Daniel: it will get more complicated when other terms in security gets expanded
Ege: (updates the issue comment)
PR 2103
<kaz> TD PR 2103 - Initial Connection Improvements
Ege: removing an empty code file as implementation should live elsewhere
Ege: we should be clear about defaults. Expanded TD has defaults filled in
Daniel: not sure if the defaults should be expanded.
<luca_barbato> +1
Kaz: regarding a possible "canonical version TD", I'm still wondering if we could think about an improved version of TM for that purpose
Ege: (creates a new Issue about that idea)
… (then goes back to the PR's changes)
… would ask people to review the points again
TD Issue 2104 - TMs with Initial Connection for expressing common deployments
[adjourned]