Meeting minutes
Minutes check
<kaz> Feb-3
Lagally: there is a typo in listener
Kaz has just fixed it.
Lagally: is the dataResponse PR already merged?
Sebastian: yes
any objections?
no
Testing
Lagally: McCool cannot share its testing tool due to companies regulation
McCool: No time to create a PR yet
… however already run the tool for the Arch Repo
… will share the csv file soon
<MM sharing its screen with the result>
<MM explains the content of the draft test report>
McCool: still to do some cleanups in the report
… e.g., there are topics that are related to discovery
Lagally: currently we have 30 assertions to test
Contributions
Lagally: we have a good numbers of PRs
https://
PR 686
<kaz> PR 686 - Update Security and Privacy Considerations (2)
McCool: still working on this
… so far I also introduced some text about trusted environment
Lagally: shall we introduce a terminology entry for trusted environment?
McCool: makes sense
<Ml shows the diff of this PR>
<kaz> 11 Security Considerations
<kaz> 12 Privacy Considerations
Lagally: what is new?
McCool: trusted envorenment and some sections have to be rewritten
Kaz: the descriptions are relatively stable. also the PR will change the section structure. so I'd suggest we once merge this PR and add further improvement after that.
Lagally: any objections? otherwise I will merge
no
McCool: is there already a TAG request?
Sebastian: no
ML is merging the PR
Improve chapter headings #694
<kaz> PR 694 - Improve chapter headings (5&6)
Lagally: I improved some chapter headings
Lagally: I will merge and update one header to "Common deployment pattern"
PR 695
<kaz> PR 695 - fixes #688: Improving language, adding rfc2119 assertion
<kaz> diff in "7.1.3 Links"
Lagally: update e.g. text about the Links
Ege: I would use other JSON-LD description for geofance and TD reference to it
Lagally: how many reference would I need then?
Ege: if everything is in the TD I would always need semantic processing
… you not solving the problem when you have everything in the TD
Ege: is there as example no_sec for security it does not mean there is no security at all
McCool: we don't have any requirements that everything needs to be a "Thing"
… Things may have network interface and additional metadata
Ege: promoting this approach might make things diverse
Kaz: think we should think about hardware layer and software layer separately when we think about use cases
Lagally: yes
<Mizushima> +1 kaz
Lagally: WebThing has a network interface
… we should split physical layer and abstract layer
… let me type in
<mlagally> proposal: split terminology "Thing" and "WebThing"
<mlagally> Thing being the general form which may only have metadata.
McCool: I'm working on a PR about terminology, btw
Lagally: tx
… talk to you soon!
[adjourned]