– DRAFT –
WoT Use Cases

Agenda Review

Mizushima: we have 6 topics today
… any other topics?

Ege: looks good to me

Mizushima: also please make sure to use q+ and speaking slowly

Logistics

Mizushima: the meetings on august 21 and 28 will be cancelled

Ege: I cannot be there for september 4th as well

Meeting plan

Mizushima: would like to fix GH issue template for use case using YAML
… then internal trial
… then refactoring

Minutes

July-17

Mizushima: any objections?

(none)

approved

Fix the YAML-based Use Case template

PR 298

<kaz> PR 298 - Change the order of items of WoT-UseCases-Template.yml

Mizushima: this PR changes the order of items

Mizushima: Do you know Ted?

Kaz: He is active in DID/VC work and is a W3C member

Kaz: we should talk about his contributions in general in the main call

Mizushima: any comments or questions?

Mizushima: Is it ok to merge?

Kaz: the changes are fine
… but it would be nicer to explain the PR a bit more

<kaz> preview md

Ege: let's merge :)

<kaz> merged

Real names and E-mail addresses

Mizushima: we decided that ownership and being able to contact is important. If we cannot, we should be able to delete the use case
… anonymous submissions are not allowed

Ege: I agree with this. We can collect name and email address in another way if we need it

Mizushima: we should be able to contact submitters

Mizushima: I would like to use github account first

Kaz: Please clarify what you want to talk about first

Mizushima: Email and name should be decided

1. if we can't contact submitters in the future (somehow - may or may not be email)
   then we reserve the right to delete a use case.

2. We should have clear "authorship" for uses cases.

3. We should don't allow anonymous use cases.

Kaz: Could you remove the policy above mentioned within the agenda because it was not our confirmed policy?

Kaz: (explains the issue in the markdown)

https://github.com/egekorkan

Ege: Could you clarify what you mean by contacting someone through github?

Mizushima: we can contact through github. No need to collect email address

Ege: My question was not answered

Luca: we can open an issue or discussion and tag them
… That should be enough for our use case
… They relinquish the right once they submit. UCs are just an input for standardization work
… if a UC is not useful, we can delete and move on to the next one

Ege: my question is answered by Luca. We should note it down, e.g. tagging GitHub handle in an issue

Kaz: Partly answers Ege's question

Kaz: but that is rather "how to solve the problem"
… and we should start with "what kind of information we need when we collect use cases" first
… then can think about how to get that information next
… we should clarify our need first

Kaz: we need clear input for each item from the UC tempalte
… and if some of the items are unclear, we need further clarification
… and so we need some method to contact the submitter to get further clarification
… we should start with that kind of need, then we can talk about how to get the information as Luca proposed.

Mizushima: we should discuss account to discuss those issues

Mizushima: I think there is enough in the issue template

Luca: just by using the issue, we can ask all the information we need. Until we have it all, we can keep the issue open and not contribute to git

Kaz: we should create a draft policy page, and ask people to give ideas to that page

adjourned