Meeting minutes
Logistics
Cancellations
Mizushima: I cannot prepare the call for april 10
… also march 20 and april 3
Ege: April 3 should be fine for those without kids. I can attend for example
Kaz: Let's ask about people's availabilities
McCool: Let's not cancel unless it is a holiday everywhere
Mizushima: Then let's not cancel april 3rd. Is it ok?
<kaz> (no objections)
<kaz> [ Use Cases call will be cancelled on Mar 20 and Apr 10 ]
Daylight Saving changes
Mizushima: daylight saving is starting next week. calls one hour earlier in eu and japan. No change for US and Canada
Kaz: It is just a reminder right?
Mizushima: yes
Plan
Mizushima: we talked about the templates for use cases, functional and technical requirements
… I have an updated version of the plan. Here it is (presents the plan in markdown)
Kaz: this seems more feasible to me. Could you put it in the agenda wiki as well?
Ege: is the proposal available?
Mizushima: yes it is below
… let's discuss that later
Minutes Review
<kaz> Feb-28
<kaz> (Mizushima goes through the minutes and mention main discussion points)
Mizushima: can we approve the minutes?
McCool: no objections
Mizushima: approved
<kaz> (both the minutes themselves and the extracted discussion points have been approved)
Use Case Template Discussion
Mizushima: let's look at the example in section 2.10.3 of the current use cases document
Motivation
Mizushima: I am not changing the motivation but adding Why WoT section
… it is detailing why wot is needed for cases with multiple vendors
Stakeholders and Environments
McCool: it would be good to have a fix list of stakeholders
Kaz: detailed questions can be done later
Ege: current template also has protocol, what about this one?
McCool: yes but only if it is relevant. we should mention whether we want to describe the protocol with wot
Ege: also, in this case the smartphone app developer is important. Is it device manufacturer, echonet consortium, 3rd part?
Kaz: I agree with both that protocol can be relevant
McCool: yes. We have to show what WoT TD is describing here
Kaz: protocol is important since it can be a potential binding based on the use case
Kaz: so let's add expected protocol to the template?
Mizushima: I agree
McCool: no objection
Mizushima: I will add it later
RESOLUTION: we'll add "Expected protocol" also under "Expectations for stakeholders and environments"
Gaps
Mizushima: Here are the gaps
Ege: there are some paragraphs and points that should not be in gaps
McCool: I agree
Ege: I can provide a PR
McCool: existing standards, similar use cases and dependencies should be above gaps
McCool: we do not have enough time. We should focus on the template
Mizushima: any suggestions? opinions?
McCool: yes please improve the example and template based on the discussion today
Mizushima: yes let's do that
Kaz: now we can accept proposals from other TF members
<kaz> Now the question is who to do that. I think
McCool: I think Mizushima-san should do the PR and me and Ege can comment/review
Ege: I agree. I am not sure about what to change in the current template, e.g. horizontal or vertical category
… I can happily provide comments and suggestions
Kaz: Yes, in that case, let's ask Mizushima-san to create a PR after skimming Ege's draft PR.
Kaz: so Mizushima-san has an action item to do a PR to update the template based on today's discussion
ACTION: Mizushima to create a PR to update the use case template based on today's discussion
Mizushima: let's discuss the PRs in the next meeting
adjourned