W3C

– DRAFT –
WoT Use Cases

18 September 2024

Attendees

Present
Ege_Korkan, Kaz_Ashimura, Luca_Barbato, Michael_McCool, Tomoaki_Mizushima
Regrets
-
Chair
McCool, Mizushima
Scribe
kaz

Meeting minutes

Logistics

Kaz: would suggest Mizushima-san and McCool have coordination discussion before the official Use Cases call

McCool: to be done in the future

Agenda review

agenda for today

Mizushima: (goes through the agenda)

Kaz: TPAC discussion to be done earlier given it would be held next week

Mizushima: if any specific topics

Kaz: need to finalize the agenda items about UC during TPAC

McCool: we can talk about requirements after TPAC

Minutes

Sep-11

Mizushima: (goes through the minutes)

approved

TPAC planning

TPAC WoT wiki

Mizushima: starts at 14:10?

McCool: yeah, 10-min opening first then Use Cases
… Use Cases to be discussed first
… then refactoring which would impact all the specs
… think that's a right order
… note that registry discussion to be handled during the TD session
… btw, "where do requirements go" to be discused during the UC/Req session
… my slides have 5 pages, 2 mins for each
… then discussion
… we should have some slides prepared
… I've prepared slides for my part on requirements process
… technical vs functional
… separation of what and why
… would invite comments for that discussion

Ege: may agree, but would see examples

McCool: will describe that using slides
… (describes some example about security)
… use cases will be motivation

Ege: agree

McCool: I'm ready, I think
… if you want, you can review my slides on GitHub
… btw, Mizushima-san, have you generated your slides yet?

Mizushima: not yet...
… some slides available, though

McCool: 3 slides on basics and demo would suffice

Mizushima: demo by Ege
… Ege, could you please generate some material for the demo?

Ege: ok

Kaz: ok for Ege to show the current work by the TD TF?

Mizushima: would like to Ege to present the current trial by the TD TF

McCool: let's allocate 5 mins for that purpose
… Ege can create one slide

Ege: ok

McCool: other than that, the current slides look fine
… please upload them on GitHub
… including screenshots would be nice

Kaz: Ege, you can generate one pager slide separately

McCool: anyway, please upload your slides, Mizushima-san

Schedule

schedule.md

McCool: if you go down...
… Sep 2024 was the original target for UCR Note publication
… but would not be feasible any more
… in September, we'll have TPAC and then vacation
… so should say October instead
… then
… another goal to update the requirements section of the UCR doc by April next year
… by the end of October, we should be able to finalize the process
… (start to share the screen to edit the schedule)
… (applying the proposed changes)
… would like to propose...
… October, 2024 for UCR process defined
… March, 2025 for updated UCR Note publication
… need to define requirements for our spec work

Kaz: need clarification for "process defined in Oct"
… within the UCR Note?

McCool: focus on capturing use cases
… if necessary, some use cases to describe that

Kaz: so concentrate on the description about the process
… and we don't need to capture actual use cases at the moment. right?

McCool: right

Kaz: ok

McCool: we have to wrap all the discussion quickly for that purpose
… then really focus on requirements next
… can/need to handle things in parallel
… any objections for those two changes?

(none)

McCool: PR has been created, and will be merged during the main call

Internal trial of new UC template

Ege: (shares his screen to describe that)

TD Issue 2039 - Using the New Use Case Template and Gathering Experience

Ege: there are several proposed UCs already
… put the UC template on the TD Issue 2039 as MD
… so that people can copy the template easily

Daniel's example

Ege: one from Daniel
… about property returning a set of values
… the description is very technical

McCool: this is a feature request describing why we need some specific feature

Ege: Daniel is assuming, e.g., Philips Hue

McCool: anyway, I need to give comments to this
… there are three examples on my slides too

Ege: if I do a demo based on this TD Issue, should it be done before your presentation?

McCool: before my requirements slides
… but we need to distinguish feature requests from requirements

<EgeKorkan> w3c/wot-usecases#296

Ege: have different example about history data also
… can talk about the details during the TD slot

McCool: can mention the three examples and mention the detailed to be handled during the TD slot
… let me quickly share my slide

Kaz: agree the details on Issue 2039 to be done during the TD slot and just mention there is some trial work by TD TF during the UC session

<McCool> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2024-09-tpac/2024-09-26-WoT-TPAC-Requirements-McCool.pdf slide 6

McCool: (shows his slides)
… three examples here
… consumer of TDs, system owner, and produce of TDs
… can add more clarification to them too

Kaz: regarding TD issue 2039
… agree the McCool that feature requests to be handled separately from requirements
… then would be better to create separate MDs one by one so that we can give comments to each proposed trial UC
… will propose that during the TD call again

McCool: ok
… anyway, let's go for the slides including the examples

Next meeting

McCool: in 3 weeks due to TPAC and recap

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 229 (Thu Jul 25 08:38:54 2024 UTC).