13:00:49 RRSAgent has joined #wot-uc 13:00:49 logging to https://www.w3.org/2022/01/11-wot-uc-irc 13:01:01 meeting: WoT Use Cases 13:01:55 present+ Kaz_Ashimura, Michael_Lagally, Michael_McCool 13:02:36 present+ Jack_Dickinson 13:04:47 Mizushima_ has joined #wot-uc 13:05:18 present+ Tomoaki_Mizushima 13:06:01 agenda: https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf#11.1. 13:08:31 dezell has joined #wot-uc 13:09:20 present+ David_Ezell 13:16:10 mlagally___ has joined #wot-uc 13:16:53 recap 13:17:10 i/recap/scribenick: McCool/ 13:17:20 s/recap/topic: recap/ 13:17:23 ml: before winter break, reviewed doc and now have a version we are seeking approval for publication 13:17:32 ... gave people time over the break to review 13:17:55 ... there were a few questions outstanding, e.g. how to integrate retail 13:18:23 ... but I think we are in a good position to do editorial fixes but not major content changes at this point 13:18:34 topic: minutes 13:18:58 ml: went over PRs for new use cases 13:19:10 ... looked at EdgeX and Connexxus use cases 13:19:26 ... integrated some additional use cases, including digital microscopes 13:19:30 i|went over|-> https://www.w3.org/2021/12/14-wot-uc-minutes.html Dec-14 13:19:42 ... had a proposal for a table 13:20:16 mm: thought we agreed to take the table out for now... let's discuss today 13:20:27 ml: any objections to publish? 13:20:33 ... none, publish 13:20:36 topic: logistics 13:20:48 ml: back to biweekly schedule? 13:21:12 ... we did a big push to update the doc, but I think it is appropriate to relax a little bit and focus on other specs 13:22:12 proposal: go back to a bi-weekly schedule, skip next weeks cxall and have the next UC call in 2 weeks from now. 13:22:24 proposal: go back to a bi-weekly schedule, skip next weeks call and have the next UC call in 2 weeks from now. 13:23:04 resolution: go back to a bi-weekly schedule, skip next weeks call and have the next UC call in 2 weeks from now. 13:23:19 topic: pull requests 13:23:49 ml: two presentations from jack and dave, uploading 13:25:03 mm: appropriate to include in W3C repos? 13:25:45 kaz: can archive slides, does not require transfer of copyright 13:26:58 de: as mentioned in email, was not sure where the document we talked about was 13:28:27 https://github.com/w3c/wot-usecases/pull/160/files 13:28:39 https://github.com/w3c/wot-usecases/pull/159/files 13:28:58 ml: just put the content into the repo, under CONTRIBUTIONS 13:29:59 ... not new content, just helping you out with the upload 13:30:23 de: we use gitlab, would like to spend time with someone figuring out how to do PRs 13:30:33 ml: let's take ten minute after the call 13:30:46 ... in the meantime, are we comfortable with merging these? 13:30:50 de: sure 13:30:55 jd: sure 13:31:25 de: actually, can you not merge the second one, we can use it as a test case in our session? 13:31:34 ml: ok, sure, will keep it open 13:31:45 de: but we do approve merging the content 13:32:12 topic: document review 13:32:27 ml: to recap, reorganized retail into a common section 13:32:50 ... the orginal single use case is now set up as an intro 13:34:01 i|to recap|-> https://w3c.github.io/wot-usecases/#retail WoT Use Cases - 2.5 Retail 13:34:02 mm: but it probably needs a little tweaking so the opening use case reads like an introduction 13:34:34 ... and I recall we agreed to comment out the table for now (but it's still in the doc) 13:34:54 ml: we thought the table was useful, however 13:35:09 ... see slide 3 in pres 13:35:15 q+ 13:35:27 ... but maybe it goes at the beginning of 2.5 before any use case 13:36:05 de: regarding the table, is it a problem if this only exists for retail 13:36:15 ... also first two columns don't really fit 13:36:31 ... and needs to be updated to list all of them 13:36:48 ml: in that case, let's stick with what we have 13:37:23 present+ Sebastian_Kaebisch 13:37:37 mm: david, please do think about the name for the first retail use case 13:37:50 ... we called it "retail operations" but that may not be ideal 13:37:54 topic: publication 13:38:01 ... need to clean up issues, etc. 13:38:46 ... in particular, need to close issues that have been resolved 13:38:53 ... e.g. digital microscopes 13:40:38 ml: closing issue #172, for retail use cases 13:41:02 ml: issue #135, use specref database references when possible 13:41:32 s/... need/mm: need/ 13:41:57 ... note this is specific, there are a set of references that needed to be fixed 13:42:26 i|closing issue #172|subtopic: Issue 172| 13:42:35 ... issue is still outstanding 13:42:40 i|closing issue #172|-> https://github.com/w3c/wot-usecases/issues/172 Issue 172 - Revise introductory Retail use case - table, etc.| 13:42:43 subtopic: Issue #121 13:42:56 ml: this is for Brick schema 13:42:57 i|issue #135|subtopic: Issue #135| 13:43:17 s/subtopic: Issue 172/subtopic: Issue #172/ 13:43:47 i|issue #135|-> https://github.com/w3c/wot-usecases/issues/135 Issue 135 - Improve references: Use Specref Database references where available for release 2.0| 13:44:08 ... also need to convert the 13:44:16 ... URL to an actual reference 13:44:29 ml: ok, editorial, mm can you fix? 13:44:30 i|this is for B|-> https://github.com/w3c/wot-usecases/issues/121 Issue 121 - Add citation to Brick Schema| 13:44:31 mm: yes 13:45:11 subtopic: Subtopic Issue #88 13:45:17 ml: accessibility revierw 13:46:56 mm: as part of the revirew, they could provide input on issue #64 13:48:58 ... e.g. whether we need to add specific considerations to each use case 13:49:12 mm: ok, assign this to me, I will send the email requesting revierw 13:49:20 s/revierw/review/ 13:49:21 s/Subtopic Issue/Issue/ 13:51:29 mm: not clear if the cifferent lifecycles are really different use cases or just different ecosystem conventions 13:51:37 ... will have to discuss in security 13:52:43 s/cifferent/different/ 13:53:17 mm: rather than specific considerations 13:54:41 mm: (proposed text in issue) 13:54:48 subtopic: issue #48 13:55:03 i|accessibility review|-> https://github.com/w3c/wot-usecases/issues/88 Issue 88 - Accessibility review of FPWD draft of "WoT Use Cases and Requirements" document| 13:55:17 i|not clear|subtopic: Issue #50| 13:55:51 mm: do we have any vertical use cases that mention time series? 13:56:01 ... smart home, digital twin, etc. 13:56:14 kaz: smart building, media, etc. 13:56:33 i|not clear|-> https://github.com/w3c/wot-usecases/issues/50 Issue 50 - Complete privacy section for Medical use case| 13:56:59 s/issue #48/Issue #48/ 13:57:01 subtopic: issue #49 13:57:11 ml: OAuth 13:57:38 i|do we have any|-> https://github.com/w3c/wot-usecases/issues/48 Issue 48 - Horizontal use case for time series| 13:57:39 mm: think we can do the same thing here as medical, just add a sentence citing the appropriate spec, in this case the OAuth spec 13:58:13 i|OAuth|-> https://github.com/w3c/wot-usecases/issues/49 Issue 49 - Complete privacy section for Oauth use case| 13:58:20 s/issue #49/Issue #49/ 13:58:52 subtopic: issue #39-#44 13:59:04 ml: cross references, all deferred to pub 3.0 13:59:30 subtopic: issue #75 13:59:42 ml: requirements for timestamps; first need use cases 14:00:38 subtopic: issue #76 14:01:02 mm: accuracy; we agreed to use SSE terminology 14:01:31 ... agree not short-term, but can start by identifying use cases that mention accuracy, e.g. geolocation 14:01:43 topic: others 14:01:52 i|cross refere|-> https://github.com/w3c/wot-usecases/issues/39 Issue 39 - Cross reference from vertical use cases to horizontal use cases| 14:01:53 ml: will generally assume other issues are all deferred 14:02:09 I need to go 14:02:19 i|cross refere|-> https://github.com/w3c/wot-usecases/issues/40 Issue 40 - Cross reference from vertical use cases to Discovery use case| 14:02:50 i|cross refere|-> https://github.com/w3c/wot-usecases/issues/41 Issue 41 - Cross reference from vertical use cases to Oauth use case| 14:03:18 i|cross refere|-> https://github.com/w3c/wot-usecases/issues/42 Issue 42 - Cross reference from vertical use cases to Digital Twin use case| 14:03:41 i|cross refere|-> https://github.com/w3c/wot-usecases/issues/43 Issue 43 - Cross reference from vertical use cases to Geolocation use case| 14:04:02 i|cross refere|-> https://github.com/w3c/wot-usecases/issues/44 Issue 44 - Cross reference from vertical use cases to Edge Computing use case| 14:04:49 i|requirements for time|-> https://github.com/w3c/wot-usecases/issues/75 Issue 75 - Requirements document for time stamps/ time series| 14:05:08 kaz, the bridge was closed 14:06:47 zoom would be better 14:06:54 does that work for you? 14:07:06 or can we just join back for 10 mins? 14:08:12 thanks Kaz - let's do that 14:09:28 i|accuracy;|-> https://github.com/w3c/wot-usecases/issues/76 Issue 76 - Requirements document for accuracy| 14:10:22 i/I need to go/[adjourned]/ 14:10:32 rrsagent, make log public 14:10:37 rrsagent, draft minutes 14:10:37 I have made the request to generate https://www.w3.org/2022/01/11-wot-uc-minutes.html kaz 14:11:32 s/issue #/Issue #/ 14:11:33 s/issue #/Issue #/ 14:11:33 s/issue #/Issue #/ 14:11:35 rrsagent, draft minutes 14:11:35 I have made the request to generate https://www.w3.org/2022/01/11-wot-uc-minutes.html kaz 14:12:37 chair: Lagally 14:13:32 s/accessibility revierw/accessibility review/ 14:13:54 i|accessibility review|Issue 88 - Accessibility review of FPWD draft of "WoT Use Cases and Requirements" document| 14:13:57 rrsagent, draft minutes 14:13:57 I have made the request to generate https://www.w3.org/2022/01/11-wot-uc-minutes.html kaz 14:14:31 rrsagent, bye 14:14:31 I see no action items