00:39:39 kaz has joined #wot 01:05:52 dsr has joined #wot 01:24:14 dsr has joined #wot 03:25:19 dsr has joined #wot 05:26:30 dsr has joined #wot 07:01:19 dsr has joined #wot 07:18:52 dsr has joined #wot 07:37:53 dsr has joined #wot 07:57:30 dsr has joined #wot 08:16:21 dsr has joined #wot 08:31:14 dsr has joined #wot 08:37:41 dsr has joined #wot 08:58:27 dsr has joined #wot 11:57:12 RRSAgent has joined #wot 11:57:12 logging to https://www.w3.org/2021/03/18-wot-irc 11:59:34 McCool has joined #wot 12:00:27 mlagally has joined #wot 12:01:07 sebastian has joined #wot 12:01:09 citrullin has joined #wot 12:01:12 scribenick: McCool 12:01:43 ktoumura has joined #wot 12:02:16 Meeting: WoT-IG/WG vF2F Meeting in March - Day 3 12:02:51 present+ Kaz_Ashimura, Sebastian_Kaebisch, Dave_Raggett, Ege_Korkan, Kunihiko_Toumura, Michael_Lagally, Michael_McCool, Philipp_Blum 12:03:21 Mizushima has joined #wot 12:03:36 present+ Daniel_Peintner 12:03:55 Agenda: https://www.w3.org/WoT/IG/wiki/F2F_meeting,_March_2021#Thursday_March_18 12:04:41 presentations will be uploaded after the session to https://github.com/w3c/wot/tree/main/PRESENTATIONS/2021-03-online-f2f 12:04:47 dape has joined #wot 12:05:24 use cases repo is here, issue numbers will be relative to this repo if not fully qualified: https://github.com/w3c/wot-usecases 12:05:42 topic: Opening 12:05:54 -> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2021-03-online-f2f/2021-03-18-WoT-F2F-Opening-McCool.pdf Opening slides 12:06:12 today will mainly discuss use cases; only a 2h session 12:06:23 i/Presentations/topic: Preliminary/ 12:06:26 cris has joined #wot 12:06:51 mjk has joined #wot 12:07:06 seb: mccool to take minutes the first hour, raggett the second hour 12:07:19 present+ Cristiano_Aguzzi, Ege_Korkan, Michael_Koster, Tetsushi_Matsuda, Tomoaki_Mizushima 12:07:25 seb: (presents opening slides, reviews agenda) 12:07:25 rrsagent, make log public 12:07:31 rrsagent, draft minutes 12:07:31 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 12:08:11 matsuda has joined #wot 12:08:19 mmccool: no guests today, all IG members 12:08:29 topic: Use Cases and Requirements 12:08:44 ml: start by reviewing process 12:09:11 i/start by/[slides tbd@@@]/ 12:09:13 ... then I will present and walk through the current Use Cases and Requirements document 12:09:36 ... which we plan to publish in two weeks 12:10:44 we also have an ITU-T topic, but have to shift to next Monday due to avaliability 12:10:59 s/we also/... we also/ 12:11:19 note that we plan to have a resolution to publish on April 7, this is a review of the candidate draft. Has been stable for a while, but seeking input before publication 12:11:20 Chair: Sebastian/McCool 12:11:28 s/note that/... note that/ 12:11:36 ryuichi has joined #wot 12:11:43 ... there has also been some cleanup, including commenting out sections that were incomplete 12:12:20 ml: objective of UC IG TF is to collect use cases and identify requirements, including collecting use cases from other SDOs 12:12:33 ... and also collaborate with other TFs on requirements 12:12:39 present+ Daniel_Peintner, Philip_Tran 12:12:53 rrsagent, draft minutes 12:12:53 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 12:12:59 ml: process is as followed 12:13:37 ... collect use cases proposals, have a shortlist to filter contributions (although most have been high quality and have been accepted), then identify gaps, etc. 12:13:42 i/presentations will be/topic: Preliminary/ 12:13:45 rrsagent, draft minutes 12:13:45 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 12:13:59 ... eventually analysis of use cases should result in a set of requirements for other TFs 12:14:04 q? 12:14:08 Ege has joined #wot 12:14:37 ml: we don't have a strong formalism on use case description; have focused on getting input rather than being formal 12:14:43 ... so want to keep the barrier low 12:14:47 present+ Ryuichi_Matsukura 12:15:03 ... have a simple MD template, although eventually need HTML; Kaz created a convertor 12:15:18 ... github repo is here: https://github.com/w3c/wot-usecases 12:15:34 dezell has joined #wot 12:15:44 present+ David_Ezell 12:15:46 ... under USE-CASES, usecases that have been incorporated into the document are under "processed" 12:16:06 rrsagent, draft minutes 12:16:06 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 12:16:07 ... we also have some guidance as to appropriate terms to use, for instance, to refer to stakeholders 12:16:15 ... these are given in the template 12:16:52 ml: (walks through template) 12:17:09 ... there is both a requirements and a use cases template 12:17:35 ... we also need eventually to distinguish between "horizontal" and "vertical" use cases 12:18:13 ml: note introduced i8n requirements late, still not much content there 12:18:33 ml: driven by contributions 12:19:08 q+ 12:19:49 q+ 12:20:27 mm: suggest that we see if we can get wide review... i8n and privacy, although we have talked to accessibility 12:20:41 ack k 12:21:08 kaz: wide review is for normative docs 12:21:17 mm: understood, but at least we can ask 12:21:42 seb: nice if we can have a todo-list, especially for topics that are not covered yet 12:22:03 s/docs/docs, though it would be useful to get early feedback from them if possible/ 12:22:05 ... e.g. opc-ua, automotive, etc... so we know what's expected 12:22:17 ml: we collect these in issues, I have attached labels 12:22:38 ... did try to make a guess at which ones we may be able to finalize 12:22:48 ... but we are also dependent on contributions 12:23:01 ml: although I just noticed there is no issue 12:23:06 seb: there is a PR though 12:23:42 ml: while we are talking PRs, there are a couple that should go into the current document 12:24:20 ml: can create OPC-UA issue, can you be owner? 12:24:37 seb: yes, but we may also have other contributors to Shaeffler 12:24:46 ... no specific name however 12:25:47 ml: note that requirements was moved from architecture to usecases, so if you see an old link to architecture note that they have been moved to use cases 12:25:54 ... and will be in that document 12:26:46 mm: reiterate that the doc is "Use Cases and Requirements" and will be informative 12:27:17 ml: let me review the structure of the actual document 12:27:43 ... first talk about application domains and the purpose of collecting use cases from various domains 12:28:28 ... by the way, looking at the doc in PR https://github.com/w3c/wot-usecases/pull/114 12:28:59 ... this PR removes empty sections left over from template but not filled in; just commented out, however 12:30:05 ... some things have been labelled differently or renamed 12:30:21 q+ 12:30:48 ... also removed affiliation of people with companies, W3C policy clarification need 12:31:20 kaz: did talk to legal team about affiliations, esp for non-members 12:31:51 q+ 12:32:24 ack s 12:32:43 mm: I think we should raise this with W3M directly and ask to put affilliations in, since the purpose of UCs is to collect external input 12:33:44 ... and what if this was considered a CG document? 12:35:25 ack k 12:35:31 kaz: ok to put all the affiliations down in the acknowledgements, however 12:36:36 de: there is a strong connection to market, and while sensitive to issues of company promotion, but in this case the company affiliations are in fact very important for marketing reasons; "in good company" 12:37:07 ml: my personal take is that no-one reads appendices 12:37:19 mm: ok, let's do another round with Wendy S. 12:37:57 ml: going back to the doc, did not delete anything except a total duplicate section 12:38:26 ... also took out some editorial notes about "add something here", instead we have issues for this now 12:39:08 ... some of these todo are still in comments, however 12:39:28 s/esp for non-members/esp for non-members. first, we can include use case contributions from non-Members into the use cases doc. second, we should not mention the non-Member companies' name within the use case description because authorship of the W3C TR is entitled for the W3C Members. third, however, we still can acknowledge their work mentioning their name and affiliation within the Acknowledge section./ 12:42:40 mm: just wanted to clarify that main use case should be simple and concrete and raise a requirement; please put variations under "variants" rather than complicating the main use caes 12:42:48 s/caes/case/ 12:43:08 ml: should also mention in many cases we just have placeholders for references but the details need to be filled in 12:43:13 ... but this is just homework 12:44:00 rrsagent, draft minutes 12:44:00 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 12:44:30 ml: let's now look at the document; note that terminology is pulled entirely from Architecture 12:45:21 i/start by reviewing process/subtopic: Process/ 12:46:24 mm: should stakeholders be terminlogy? 12:46:38 s/stakeholders/"stakeholders"/ 12:46:45 ml: hard to make consistent, and also openended, prefer to keep those terms informal 12:47:00 ml: then we have vertical, domain-specific use cases 12:47:47 .. then have "horizontal" use cases that span multiple industries 12:49:25 i|going back to the doc|-> https://pr-preview.s3.amazonaws.com/w3c/wot-usecases/pull/114.html#sec-vertical-ucs Preview of PR 114 - 4. Domain specific Use Cases| 12:52:12 mm: VR/AR maybe belongs under Smart City, and 5.6.2 maybe belongs under 4.10.2... smart home vertical 12:53:31 q+ 12:54:15 ack d 12:54:34 ml: please make a PR 12:54:36 mm: ok 12:54:54 ml: also "target users" -> "target stakeholders"... everywhere? 12:58:01 kaz: @@ 12:58:06 mm: propose that we do some cleanup on the VR/AR topic (possibly splitting it up into a vertical and a horizontal use case) AFTER the proposed publication 12:58:11 ack k 12:58:22 q+ 12:58:22 q+ mm 12:58:30 ack m 12:58:34 ack m 12:59:57 s|@@|as one of the authors of the VR/AR use case, I believe this should be kept within the horizontal use cases, though we can add some more additional use cases or descriptions under the domain-specific use cases like smart city./ 13:01:07 i/let me review the structure/subtopic: Document status/ 13:01:14 rrsagent, draft minutes 13:01:14 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 13:01:53 i/as one of the/scribenick: kaz/ 13:02:05 i/propose that/scribenick: McCool/ 13:02:07 rrsagent, draft minutes 13:02:07 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 13:04:18 q+ 13:04:56 mm: maybe we could add horizontal/vertical tags? 13:05:11 ml: that's what we had before, would rather not revert at this point 13:06:27 q? 13:07:00 ack k 13:07:32 kaz: @@ 13:07:51 kaz: really just need a process where we collect use cases and then capture requirements; whether the use case is horizontal or vertical does not matter so much 13:08:06 s/kaz: @@// 13:09:29 ml: note that under REQUIREMENTS there are a set of additional contributions that have not yet been merged; and the current document is relatively light 13:10:05 i|note that|-> https://pr-preview.s3.amazonaws.com/w3c/wot-usecases/pull/114.html#requirements PR 114 Preview - 6. Requirements| 13:10:24 mm: should we be merging some of these? Discovery has been around for a while, for example 13:10:52 ml: don't think we can merge this now. 13:11:07 mm: agree, too much extra content to deal with now 13:11:08 i|note that|-> https://github.com/w3c/wot-usecases/tree/main/REQUIREMENTS REQUIREMENTS area on the wot-usecases repo| 13:11:56 ml: also, acknowledgements should not be 6.3 but a new section or appendix; editorial change 13:12:41 q? 13:13:33 proposal: merge PR114 https://pr-preview.s3.amazonaws.com/w3c/wot-usecases/pull/114.html for template cleanup 13:14:03 proposal: merge PR114 https://pr-preview.s3.amazonaws.com/w3c/wot-usecases/pull/114.html for "Remove template leftovers" 13:14:29 mlagally_ has joined #wot 13:14:29 s|proposal: merge PR114 https://pr-preview.s3.amazonaws.com/w3c/wot-usecases/pull/114.html for template cleanup|| 13:14:32 https://github.com/w3c/wot-usecases/pull/114 13:14:42 proposal: merge PR114 https://github.com/w3c/wot-usecases/pull/114 for "Remove template leftovers" 13:14:54 rrsagent, draft minutes 13:14:54 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 13:15:18 resolution: merge PR114 https://github.com/w3c/wot-usecases/pull/114 for "Remove template leftovers" 13:15:26 rrsagent, draft minutes 13:15:26 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 13:15:39 ml: there is another pull request that is on top of this one that adds a liaison chapter 13:16:11 ml: add a section on liaisons 13:16:33 i/there is another/subtopic: PR 117/ 13:16:36 q+ 13:17:09 q+ 13:17:12 ack m 13:17:59 mm: we should add at least Conexxus and IETF 13:18:06 kaz: and also OGC 13:18:13 ack k 13:18:42 Conexxus is working on a WoT POC demo for our Annual Conference the week of April 26. 13:19:04 i|there is another|-> https://github.com/w3c/wot-usecases/pull/117 PR 117 - Add liaisons| 13:19:07 q+ 13:19:12 ml: feel uncomfortable about joint activity in the document 13:20:56 seb: I think just mentioning that there is a liaison 13:21:27 ... am fine with the current text, but can also point to existing liaison 13:22:00 ... can add link 13:24:09 ml: David, can you provide a PR on Conexxus? 13:24:12 https://github.com/w3c/wot-usecases/pull/117 13:24:29 de: ok, can do 13:25:11 -> https://pr-preview.s3.amazonaws.com/w3c/wot-usecases/pull/117.html#liaisons Preview of 7. Liaisons 13:25:42 s/Preview of 7. Liaisons/Preview of proposed section "7. Liaisons"/ 13:26:40 q? 13:27:16 ml: let's then keep the PR open, work on it 13:27:42 mm: let's to an email call and point to this PR as well as the main 13:28:47 ... but email on the liaison PR can wait until a week before 13:29:18 kaz: have two questions 13:30:30 ... would like to understand main intention of this section; already contributed, or future? 13:30:40 ... IEC, ECHONET, ECLASS are in second category 13:31:37 https://www.w3.org/2001/11/StdLiaison 13:31:40 ... second, there is an official table, and we should link to other press releases too 13:31:55 s|https://www.w3.org/2001/11/StdLiaison|| 13:31:58 mm: is fairness a problem? If we link to one press release, should be link to them all? 13:32:07 -> https://www.w3.org/2001/11/StdLiaison W3C liaison table 13:32:23 ml: there is an issue for really old things? 13:33:01 s/official table/official table and we can mention that/ 13:33:11 s/and we/but we/ 13:33:18 mm: either we point to a table, or have a cutoff date 13:33:36 s/releases too/releases too if we include one for one SDO/ 13:33:38 ml: would rather have them in the doc then in a table somewhere else (so cutoff date approach ok) 13:33:49 q+ 13:33:54 ack k 13:34:13 ask s 13:34:38 seb: we need an overview of liaisons... is something that should be on the marketing TF task 13:34:46 ml: yes, let's discuss in the marketing call 13:34:55 ml: ok, let's look at the issues now 13:35:21 ml: automotive use case https://github.com/w3c/wot-usecases/issues/111 13:35:39 ... is there someone who can contribute on this? 13:35:58 q+ 13:35:59 seb: Daniel Wilms is our contact at BMW 13:36:06 ack s 13:36:42 kaz: BMW have also been participating in workshops, etc. 13:37:51 kaz: BK was also the original author of the VSSo 13:38:29 ml: closing issue about deleting sections no one uses 13:38:41 ack k 13:38:53 ml: next https://github.com/w3c/wot-usecases/issues/108 13:39:12 s/VSSo/VSSo. so I think Benjamin might be working with Daniel./ 13:39:16 mizushima: this is an old issue and should have been closed 13:39:23 rrsagent, draft minutes 13:39:23 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 13:40:16 i/ok, let's look at the issues/topic: Issue 111/ 13:40:20 s|ask s| 13:40:48 q+ 13:41:14 i|ok, let's look|-> https://github.com/w3c/wot-usecases/issues/111 Issue 111 - Automotive Use Case based on VSSo| 13:41:45 rrsagent, draft minutes 13:41:45 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 13:41:58 ml: for now... will label it wontfix, will remove it in a month 13:42:29 seb: agree in general that in manufacturing we should list standards 13:43:18 i|next https|topic: Issue 108| 13:43:44 ... but other use cases don't 13:43:47 i|next https|-> https://github.com/w3c/wot-usecases/issues/108 Issue 108 - Finalize the section 4.6.3 of Manufacturing| 13:43:57 rrsagent, draft minutes 13:43:57 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 13:44:37 mm: I would ask sebastian to provide a list for manufacturing... 13:44:52 ml: ok, will remove wontfix, will assign sebastian 13:45:18 topic: Issue 107 13:45:48 ml: propose closing, have fixed in PR we just 13:45:55 s/just/just merged/ 13:45:59 ml: (closes issue) 13:46:31 i|propose|-> https://github.com/w3c/wot-usecases/issues/107 Issue 107 - Finalize the section 4.6.2 of Manufacturing| 13:46:37 topic: Issue 107 13:46:56 s/Issue 107/Issue 105/ 13:47:29 s/Issue 105/Issue 106/ 13:47:53 ml: Mizushima, can you take this issue? 13:47:53 -> https://github.com/w3c/wot-usecases/issues/106 Issue 106 - Finalize the section 4.6.1 of Manufacturing| 13:48:14 mizushima: yes, I can look at it, but it seems the section was moved 13:48:28 topic: Issue 105 13:49:04 ml: number has changed to 4.6.1.2 13:50:42 -> https://w3c.github.io/wot-usecases/index.html#MedicalDevices 4.6.1.2 Interconnected medical devices in a hospital ICU 13:51:11 i|number|-> https://github.com/w3c/wot-usecases/issues/105 Issue 105 - Finalize the section 4.5.1.2 of Health use case| 13:51:12 mm: (proposed some text, added into the issue) 13:51:46 mizushima: proposed by taki, should it be checked by matsukura-san 13:51:50 q+ 13:52:45 ml: will assign it to both of you, please handle offline 13:53:10 https://w3c.github.io/wot-usecases/index.html#MedicalDevices 13:55:09 mm: note we might have missing sections in some use cases if they are old and those sections where added to the template later 13:55:11 q? 13:55:48 ml: will send an email then to all use case contributors 13:55:50 q+ 13:55:56 ack k 13:55:59 ack s 13:56:20 ack m 13:56:37 https://github.com/w3c/wot-usecases/issues?q=is%3Aissue+is%3Aopen+label%3A%22needs+owner%22 13:57:00 i/note we/kaz: think Mizushima-san meant there were several subsections within several use cases (when he generated his issues)/ 13:57:10 ml: since we are almost out of time, I would just add at this point for people to look at the issues and call for contributors 13:57:49 ml: probably still have significant editorial work 13:58:01 i/https/topic: Wrap-up/ 13:58:07 rrsagent, draft minutes 13:58:07 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 13:58:25 topic: wrapup 13:58:53 s/Wrap-up/Call for review again/ 13:58:53 rrsagent, draft minutes 13:58:53 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 13:58:55 seb: monday will be arch and profiles 14:00:46 s/profiles/profiles, plus ITU-T use case discussion at the beginning/ 14:03:19 seb: please upload your slides beforehand to: https://github.com/w3c/wot/tree/main/PRESENTATIONS/2021-03-online-f2f 14:03:35 seb: thanks a lot, and talk to you again on Monday! 14:03:38 [adjourned] 14:03:41 rrsagent, draft minutes 14:03:41 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 14:05:00 s/topic: Use Cases and Requirements/topic: Use Cases and Requirements IG Note/ 14:05:50 i/think Mizushima-san meant/scribenick: kaz/ 14:05:58 i/note we might have/scribenick: McCool/ 14:06:14 i/please upload your/scribenick: kaz/ 14:06:17 rrsagent, draft minutes 14:06:17 I have made the request to generate https://www.w3.org/2021/03/18-wot-minutes.html kaz 15:21:35 dsr has joined #wot 15:40:09 dsr has joined #wot 15:44:52 dsr has joined #wot 15:57:42 Zakim has left #wot 17:14:01 dsr has joined #wot 17:32:36 dsr has joined #wot 17:50:50 dsr has joined #wot 18:21:25 dsr has joined #wot 18:53:53 dsr has joined #wot 19:25:36 dsr has joined #wot 19:26:49 kaz has joined #wot 19:57:20 dsr has joined #wot 20:28:13 dsr has joined #wot 20:45:37 kaz has joined #wot 20:58:48 dsr has joined #wot 21:10:00 kaz has joined #wot 21:13:32 dsr has joined #wot 22:00:43 dsr has joined #wot 22:16:51 dsr has joined #wot 22:33:44 dsr has joined #wot