Meeting minutes
<sebastian> <MM setup today's agenda>
Minutes
<sebastian> https://
McCool: any changes, objections?
Mizushima: no problems
minutes are approved
Progress of Use Case Call
Sebastian: we decided in the main call to move the use case work to the relevant task force
McCool: What will we do with the existing content
Sebastian: a lot of the content is from the very early work on WoT
… we could retire a lot of the content
McCool: one of the pending PRs removes a lot of the old content
McCool: the new process will use the use case document as a central index to other documents that are generated in the task forces
… but we need to work on the requirements wit hthe task force providing the content
… there is still the issue with people to work on the central document
… there are 2 PRs to start the work
… let's review those PRs and see where we are
… still waiting for a policy document from Ben
Sebastian: there is also the Architecture document that has use case information
McCool: a lot of that can be deleted, but still need people to work on it
… the Architecture draft needs a more thoughtful approach
… we need volunteers to clean up the documents
Ege: we need to agree on the future of these documents, what is the ideal goal
… what is the role of the documents?
McCool: it's for us to have a clear vision of where we're going
… we need more explanation of the purpose in the process documentation
… and more definition
… we are calling user stories use cases to avoid confusion
… how do we create actionable data?
McCool: my vision for this document is that this document is a linking of user stories to features
… this document should focus on justification for features
… the PRs are also removing the bulk of requirements
… the user stories define requirements
<sebastian> <sorry, I need to step out>
McCool: one point is some features don't have detailed user stories
… also it's good to have things all in one place
Ege: another discussion is high level use cases for the deliverables themselves, for example we need a TD to do device onboarding
… this could drive hundreds of features
<EgeKorkan> w3c/
Koster: as an IoT industry, I need a standardized document format for onboarding IoT devices so that we can grow the industry and avoid duplicated effort across organizations
McCool: they can all be user stories
McCool: these is still a need for a separate document to pull things together
… maybe we should call them user scenarios to clarify things
… the central document is almost ready to go, let's review the status of the PRs
… there is a PR to delete the Functional Requirements
… there is another PR that removes discovery requirements and adds some user stories
… these PRs are about 3/4 done
… the central document could mainly categorize and index user stories
Ege: a lot of the use cases in section 2 and 3 are generic IoT use cases and don't help to focus the TD work
… we only need a small number of high level use cases like device onboarding
McCool: agree these are generic IoT use cases
McCool: we should rename use case to user scenario
… also some of the document describes technology in general
Ege: we should evaluate the impact of features
McCool: summarizes the discussion in a github issue
… please review and comment on the issue #362
… let's adjourn and update the agenda later