WoT Use Cases

Agenda

McCool: let's reverse the order
… because we could not talk about the policy last time

<kaz> Agenda for today

Minutes Review

<kaz> Jan-31

Lagally: we merged the ETRI use case about pest control

<kaz> Minutes approved

Pull Requests

Updating Requirements Template

<kaz> PR 209 - Update requirements-template.md

Lagally: should we go with this template?

McCool: how do we refer to UCs?
… do we have id?

Lagally: we have internal ids

Ege: I think we should use html ids otherwise the numbers will change

McCool: we can do an example and then do the other ones

Lagally: we can take a strawman proposal

McCool: geolocation would be nice but it is a big UC

Ege: how can one know other person's business case?
… I think this should be in the UC input

Lagally: it can be also in the use case, like in the pest control it is about saving money

Ege: I thought this means more the business importance

Kaz: saying "business justification" within this requirements description would be a bit too strong, also kind of delicate. So would suggest we simply say "Need and Motivation" instead.

McCool: we should focus on the policy, justification can come later

Lagally: Agree. Also we should make sure that we give less priority to hobby projects and look for business cases

McCool: we can list multiple justifications and assign them. then we can rank them

Luca: how about having an impact gauge, whether it is business or societal

Lagally: Let's merge and iterate on it

Ege: ok I will create a PR to remove

Ege: should we update the HTML too?

Lagally: good question

McCool: the final document would be html

Luca: I think we should to stick to md but say what dialect we use
… we can use to github flavor

Lagally: is this the one?

Luca: yes, we can also remove some complex cases

<mlagally> https://github.github.com/gfm/

McCool: I would say let's use github and not make it complicated

Lagally: we can remove the html version

McCool: I think we can start with the geolocation

McCool: it has variants but we can handle them internally

Lagally: can someone take over the screen

Kaz: note that "geolocation" is a kind of data which could be used by various use cases including smart home, smart building and smart city. So this description is also a kind of generic description for various use cases derived from this.

McCool: right. so would start with generic description for this

McCool: also we need to capture variants.

Luca: it might good to use HTML comments

McCool: but they should be visible

<kaz> [adjourned]