Meeting minutes
minutes review
<kaz> Apr-24
Ege: any remarks?
… minutes approved
PR #4, Terminology Improvements
<kaz> Binding Registry PR 4 - Terminology Improvements
Ege: updated from yesterday's discussion
… is it OK to merge?
Kaz: is this mostly editorial?
Ege: yes, it's editorial
… no objections, merged PR
New issue to create the editor draft with the changed name
Kaz: we should coordinate this with the main group
PR #2097 Analysis Document template
<kaz> TD PR 2097 - Analysis Document Template
Ege: for capturing user stories etc.
Ege: (shows example documents)
… any comments?
… no comments. merged
Next work items
Use Case process
Ege: the discussion overlaps with the use case discussion
… Is the difference between use cases and user stories clear to everyone?
Kaz: please remember that the main purpose is to provide the background for each feature, required by the W3C process
Ege: any other input?
Ege: for now we need a small set of use cases for the TD document
… what are some use cases?
Kaz: maybe we will review what is written so far
Ege: yes, but for now what is the high level use case for TD?
Kaz: can we start with TD use cases that are already documented on the wot-thing-description repository?
Ege: for example, the high level use for TD at Siemens is for onboarding devices automatically
Ege: for example, there is a feature requirement for Modbus to provide the polling interval
Koster: should clarify the terms, "Use Case" and "User Story", a bit more here
Ege: (adds "Definitions" to the TD agenda wiki)
Kaz: would suggest we create a quick Issue for the definition on the wot-thing-description repo as usual :)
Ege: (creates a GitHub Issue instead)
Koster: user stories could be defined for features without worrying too much about broad use case categories
<kaz> TD Issue 2098 - Use Case vs User Story Discussion
Ege: what are some high level use cases we can list now?
Cristiano: human readability, managing device inventory
Kaz: we should think about several levels of users, for example developers vs. end users
Ege: for example, some users need JSON documents
Ege: does anyone have a topic to discuss?
Data Mapping and Manageable Affordance
<kaz> Data Mapping Analysis
Ege: who would be motivated to work on these documents?
… Data Mapping and Manageable Affordances
… we need to start with user stories
Koster: we might need to get a larger audience to ask for volunteers
Cristiano: I can help in some way
Ege: are you interested more in one feature?
Cristiano: Manageable Affordances
<kaz> Manageable Affordances Analysis
Daniel: I would be more interested in the Data Mapping feature
<kaz> Data Mapping Analysis
Ege: a concrete task could be to review the issues and write up user stories
Ege: (updates issue #2094 Data Mapping analysis)
… (assign to dape) We can ask Luca to sign up also
<kaz> TD Issue 2094 - Collecting Analysis on Data Mapping
Ege: (creates issue for analysis of Manageable Affordance item)
… #2099, assign ege and cris
<kaz> TD Issue 2099 - Collecting Input for the Manageable Affordances Analysis
Ege: AOB?
… adjourned