Meeting minutes
Agenda
<kaz> Agenda for today
for the agenda, would like to discuss self-description fixes...
https://
… addressing https://
… and also https://
Minutes review
Lagally: will upload the summary document after the call
… no objections to publishing
… now taking a look at minutes from 24th
… no objections to publishing
<mlagally> https://
Requirements
Profile requirements: https://
Lagally: added identification of profiles
… continue review after identification of profiles
defining a finite set of features
Ben: things should be allowed to define beyond the finite set of protocols
McCool: basic functionality should be covered
Ben: there could be forms for both ws and http. A consumer that doesn't support one, can ignore it.
Lagally: recorded Ben's comment. Discussion may continue offline.
Lagally: https://
limit resource consumption
Sebastian: not sure why Siemens is mentioned here
Sebastian: The constraints are not needed
Ben: it's okay to have a profile to define resource constraints. But it shouldn't apply to all profiles.
security and privacy best practices
McCool: security guidelines not yet published. Currently not clear how to define security definitions that apply to all use cases.
developer mode
Ben: it implies that nosec is disallowed, but there are very valid use cases for it
McCool: it overlaps with best practices. nosec can be used if use case demands it.
Cristiano: how can we test this if nosec is conditional and sometimes valid?
Lagally: comments added and merged https://
… to have a conversation next week about objections to individual goals without conflicting with requirements of other organizations
Ben: we don't need to cover everything in this (version of) document
Modelling of multiple things as Thing Link
https://
McCool: there is PR on discovery side: https://
… Thing Link is a TD that only links to other TDs
Ben: this doesn't solve our self-discovery problem. What use case is this PR solving?
Ben: the alternative way of using directories to list TDs adds additional implementation complexity
McCool: it would be just about the listing, not the whole TDD API
Farshid: listing may also require pagination
<sebastian> we should move to the main call
Ben: I don't think the well-known URL is that useful because the information may already be known. It rathers adds limitations
<kaz> [adjourned]