- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Wed, 03 Mar 2021 17:55:21 +0900
- To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at:
https://www.w3.org/2021/02/09-wot-uc-minutes.html
also as text below.
Thanks a lot for taking the minutes, Michael McCool!
Kazuyuki
---
[1]W3C
[1] https://www.w3.org/
WoT Use Cases
09 February 2021
[2]Agenda. [3]IRC log.
[2] https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf#Agenda_9.2.
[3] https://www.w3.org/2021/02/09-wot-uc-irc
Attendees
Present
David_Ezell, Jack_Dickinson, Michael_Koster,
Philip_Tran, Sebastian_Kaebisch
Regrets
-
Chair
Lagally
Scribe
kaz, McCool
Contents
1. [4]Agenda bashing
2. [5]minutes review
3. [6]PR 89
4. [7]PR 86
5. [8]PR 94
6. [9]OPC-UA
7. [10]Issue 50
8. [11]Issue 75
9. [12]Summary of action items
Meeting minutes
Agenda bashing
Lagally: reviews agenda
… notes UC TF description added to new web page draft
… and we should also do some wiki page cleanup
<kaz> [13]Use Cases TF description on the WoT Welcome site
[13] https://w3c.github.io/wot-marketing/activities/tf-usecases/
Lagally: also master->main change on github needed, but still
working through this change on wot-testing
minutes review
<kaz> [14]Jan-26
[14] https://www.w3.org/2021/01/26-wot-uc-minutes.html
Lagally: discussed ITU-T use case summary
… plan was to invite them to this call, but did not get
organized, so need to try again
… also talked about OPC-UA and liaison plans
… see PR90
<mlagally> [15]PR 90 - Joint activity for a standardized OPC UA
Binding
[15] https://github.com/w3c/wot-usecases/pull/90
Lagally: no objections, minutes approved
so, want to look at LBD, but no one in attendance to discuss,
so we'll look at other topics
PR 89
Lagally: let's review PRs
… PR89, HTML version of template
<kaz> [16]PR 89 - add HTML template for use cases
[16] https://github.com/w3c/wot-usecases/pull/89
McCool: suggest we also update the README to give appropriate
instructions, i.e. either MD or HTML template
Lagally: will take update the README offline
<kaz> i/let's view PRs/topic: PR 89/
PR 86
<kaz> [17]PR 86 - Update Smartcity Dashboard UC
[17] https://github.com/w3c/wot-usecases/pull/86
<kaz> [18]4.4.2 Smart City Dashboard
[18] https://pr-preview.s3.amazonaws.com/w3c/wot-usecases/86/20a5eb5...mmccool:89774c2.html#smartcity-dashboard
Lagally: let's keep the PR/MR open so Philip Tran can review,
then will discuss in two weeks
McCool: there are other pending activities around geolocation
more generally...
Lagally: but that can wait, let's do the dashboard UC first
PR 94
<kaz> [19]PR 94 - Focus AR/VR Guide use case on AR
[19] https://github.com/w3c/wot-usecases/pull/94
<kaz> [20]4.17.1 VR/AR Virtual Guide
[20] https://pr-preview.s3.amazonaws.com/w3c/wot-usecases/94/81bb852...mmccool:49f9368.html#ar-guide
Action: kaz to contact Rob Smith about PR 94
<mlagally> [21]https://github.com/w3c/wot-usecases/pull/94
[21] https://github.com/w3c/wot-usecases/pull/94
OPC-UA
<kaz> [22]PR 90 - Joint activity for a standardized OPC UA
Binding
[22] https://github.com/w3c/wot-usecases/pull/90/files
Sebastian: been working on joint charter
Kaz: not really a uc description but a liaison proposal
… should be put under related standards in another relevant use
case...
McCool: such as factory automation
Sebastian: see PR 90
Lagally: we should additionally clarify what an OPC-UA binding
provides as benefits to other use cases
McCool: so maybe this should be in a new section, i.e. "Related
Standards"
McCool: not sure whether the ITU-T stuff should go in as
well...
Lagally: don't think we should do that, but can look at
specific content
Lagally: anyway, proposal is to add a section for "Related
Standards" and subsections for OPC-UA and ITU-T
… and suggest that we do another iteration on the OPC-UA to
include additional
Kaz: technically, we could reuse "dependencies" section but
adding a new section for "related standards" would make sense
Lagally: (created an issue on that point)
[23]Issue 96 - New Annex to describe Liaisons
[23] https://github.com/w3c/wot-usecases/issues/96
(McCool leaves)
Issue 50
[24]Issue 50 - Complete privacy section for Medical use case
[24] https://github.com/w3c/wot-usecases/issues/50
Lagally: this is one example on privacy required use cases
(need McCool for this topic)
Issue 75
[25]Issue 75 - Requirements document for time stamps/ time
series
[25] https://github.com/w3c/wot-usecases/issues/75
Sebastian: we're not sure how to handle time stamps / time
series withing TD
… related to topic about runtime data
… detailed description of the runtime data is needed
Lagally: do we have any ontology to handle time stamps / time
series?
Sebastian: think it's a question of the data model
… JSON Schema already provide some
… but you can provide something additional
… but we don't have any concrete recommendation
Kaz: 2 comments here
… first, do we really have clear enough descriptions within our
use cases about how to deal with time series of data?
… probably we should add some more clarifications based on some
of the related use cases like media use cases and geolocation
use cases
… second, as I suggested during the main call the other day, we
should talk with related SDOs which handle ontologies, e.g.,
IEC
Koster: agree with Kaz
… joint discussion with OneDM on time information handling
could be helpful
… examples include time series of temperature
David: time is on the same level of location
… need to identify when/where and what
Koster: right
… relevant to TD processing
Lagally: should have some use case on the combination of time
and geolocation
… let's continue the discussion
… aob?
Mizushima: there is still a use case proposal on edge computing
… but that is written in MD
… we should convert it into HTML, shouldn't we?
Lagally: yes, please do so
[adjourned]
Summary of action items
1. [26]kaz to contact Rob Smith about PR 94
Minutes manually created (not a transcript), formatted by
[27]scribe.perl version 127 (Wed Dec 30 17:39:58 2020 UTC).
[27] https://w3c.github.io/scribe2/scribedoc.html
Received on Wednesday, 3 March 2021 08:55:29 UTC