Meeting minutes
Use Cases coverage
McCool: for requirements, propose we focus in the short term on discovery and profiles
… since we have to write explainers anyway
Lagally: I have written up a table (CSV) to get coverage of various requirements
McCool: so the columns here are deliverables, right?
McCool: so each element of this table is a set of requirements, sorted into buckets
Lagally: suggest we do a high-level interation first, then drill down into details later once we find gaps.
McCool: doing this by columns might be easier
<mlagally> https://
McCool: ok, I have added this as an agenda item for Discovery
Kaz: for editor's call, Seb did mention he was generating a coverage note in issue #1350
… My understanding was you wanted Sebastian to update the coverage.csv itself based on this kind of check results, though.
<kaz> Sebastian's basic check results
Lagally: ok, I see there is a list; but this information needs to be boiled down a bit
McCool: what we really want to identify are gaps
McCool: maybe we need categories like "ok, partial, and (null)" (e.g. empty means there is a gap)
Lagally: three-way makes sense, if use "gap" explicitly it is clear is has been filled in
Lagally: (goes over use cases in TD comment above)
Lagally: let's look at the retail use case since David Ezell is here
<kaz> latest WoT Use Cases and requirement
McCool: in retail demos we were talking about simple automations
David: not so much about configuring individual devices, but about connecting devices in a certain way
McCool: also think that "simplicity of use" is an overriding requirement
… but also reliability, and "just works"
… also, I think out-of-the-box interop and control are at opposite ends
… in some use cases, e.g. smart building setup, an engineer may *want* control over all the details
… in retail, though, I want defaults to take care of the annoying details
Lagally: for virtual thing, integration of multiple devices -> automation rules
Lagally: we have found some gaps, can also look at individual use cases that have called out specific gaps
McCool: I think time series also shows up
Lagally: yes, in agriculture
McCool: also battery level, units
Lagally: relative values
McCool: eg. depth, and calibration
Lagally: precision, etc. are also importanbt
Lagally: let's remind people in main call
McCool: sure
<kaz> main call agenda
<kaz> [adjourned]