Meeting minutes
Agenda
<kaz> agenda for today
<Ege> +1 to luca
Luca: For today I would not make any resolution since we aren't enough, so I would discuss Logistics, Update Plan and consider having the Minutes review offline as done in other TFs, the other items in the Agenda should be pushed to the next meeting assuming we'll have enough people by the time to have a resolution but can be presented anyway.
Kaz: I agree, we can at least confirm the status of the Basic Template
Kaz: Mizushima-san, you may send an email to the group to finalize the template offline
Mizushima: After the meeting or now?
Kaz: Both way works, we can gather consensus via email
Logistics
Cancellations
Mizushima: I would cancel April 10 and April 17 due overlaps
… Also be careful of the daylight time saving transitions in Europe
Mizushima: Is it ok?
<all> ok
Updated plan
Use Case template
<Tomo> Mar-27: Fix basic Use Cases template based on the previous discussion; start discussion on Requirements
<Tomo> Apr-3 and Apr-24: Fix basic Functional Requirements template based on a concrete eample
<Tomo> May-8 and May-15: Fix basic Technical Requirements based on a concrete example
Mizushima: We should consider how this plan relates with the other other TF schedules and our publication schedule
Minutes and discussion points
<kaz> Mar-13
Mizushima: <presents the summary> Any objections to the summary?
<no objections, minutes approved>
Preliminary resolution for the Use Case Template
Kaz: We now have 6 participants, but Michael McCool is absent, we can have a preliminary resolution
Mizushima: I update the template according to the feedback received
<Tomo> https://
<Tomo> https://
<Tomo> https://
<Tomo> https://
Mizushima: Can we preliminary approve the template?
Ege: I like it but we make sure to have a template and an example, this is a good example. Once we agree on the structure we should make a template (with empty sections)
Ege: Regarding the gaps, I would focus on which are the gaps in the standards. in the example I'd focus on what is infeasible with the current WoT standards.
Ege: Furthermore the template should be an empty structure but with links to the example document
Mizushima: Regarding example and template, I agree. I put already in the example the links to the guidelines. Regarding the Gaps description we will need more discussion on what fits.
Cristiano: Regarding the template structure, it looks good. My feel is that it might hard to iterate on the usecase. Do we have a mechanism to extend a Use Case as more requirements appear?
Luca: A process to update an already existing Use Case?
Cristiano: Yes, a newcomer might have a user story that applies to an existing Use Case, but with small additional details
Mizushima: We are concentrating now on new Use Case, we'll cover the updating phase later
luca: agree that what we have in the current example
… good example, and we should generate actual template based on this
… what's written here should put into the UCR Note itself too
… can volunteer to help that work
Kaz: I'm ok with Miz propose direction and I understand what had been propose to the other.
Kaz: Regarding updates, we can fit the topic later in the schedule
Kaz: if everybody is ok we can make a preliminary resolution based on the current example
Ege: Regarding the discussion on the Gaps, shall we do that now or later?
Kaz: We have the problem with submitters that are unaware of the WoT specification
Kaz: We can split the story into two pieces, (1) the structure of the template and (2) content specifics regarding the gaps
Luca: I agree we can have now a resolution on the template structure now, we should have a Gaps document like the security document so the submitter can do the gaps analysis work before submitting
Kaz: We need to clarify how the gaps to be described
Kaz: Is this in line with your opinions ege, lu and chris?
Ege+Luca: yes
Mizushima: I'd like to summarize this discussion: The template is fine, but we should discuss more on how to describe Gaps
Mizushima: Can we preliminary approve the template?
Mizushima: I'll send an email to the members to notify
Kaz: Please make sure Michael McCool is aware, since we have already 6 members
Kaz: Also mention that the template (with empty section) is still to be made and the pending discussion regarding Gaps
<Tomo> Proposal: the basic use case template preliminarily approved though we still need to discuss how to describe the Gaps.
RESOLUTION: the basic use case template preliminarily approved though we still need to discuss how to describe the Gaps.
<resolution approved>
ACTION: Mizushima to send out a confirmation message to the whole WoT WG also
<kaz> [adjourned]