W3C

– DRAFT –
WoT Use Cases

07 December 2021

Attendees

Present
David_Ezell, Kaz_Ashimura, Sebastian_Kaebisch, Tomoaki_Mizushima
Regrets
-
Chair
-
Scribe
kaz

Meeting minutes

Minutes

Nov-30

approved

Retail use cases (Conexxus)

Lagally: integration of the top 7 use cases

David: was looking at the table
… primary/secondary may be removed

Lagally: ok

David: happy to update the table

Lagally: maybe we can prioritize those 7 devices

David: top 7 is fine

Lagally: ok

Mizushima: I've converted all the retail MD files to HTML
… but am wondering about the usage

Lagally: tx for working on that
… we can discuss the detail later
… do we have a PR?

Mizushima: PR 156

PR 156 - Insert digital-twin-use-case.md and use-case-opc-ua-binding.md and retail for conexxus into index.html

Lagally: David, have you yourself created a PR for your pseudo Thing use case?

David: we usually use GitLab and have some trouble
… (shared his screen)
… working on the description for "Pseudo Thing"
… "Virtual Thing" is an alternative

Lagally: let's go for "Virtual Thing"

David: OK
… (goes through the description)
… Category: Retail
… Class: Indoor facilities and Power equipment
… Target Users: device owners, device manufactures, gateway manufactures, network operators
… you can send comments by email
… one of the powerful points of WoT is using TD to describe Thing's capability
… in an abstract level
… Things like door sensors and multi-core processors
… also 5G network provides computational power
… same TD works for both the physical device and the virtual device
… input processed by AI
… huge problem with IoT about interoperability
… third-party facilitator provides devices
… and there is no standardization
… would cost accessibility
… new devices may work differently
… software for devices costs much
… expensive proposition due to certification, etc.

Lagally: that's quite clear

David: and more complicated case
… door sensor works with video camera
… you can change the video camera at any point based on WoT
… the stream could also use multiple virtual devices
… put some description here
… maintain existing functionality
… regarding privacy consideration
… even voice interaction to be considered
… security concern about sharing video streams as well
… should have security/privacy risk about door's opening and closing
… consideration about accessibility areas
… and i18n

Lagally: tx
… clear and concise description

kaz: thanks!
… would be great if we could have concrete description about the application
… with some of your diagrams from the slides
… maybe some description already included in the "Motivation" section, though

David: can move the description from "Motivation" to "Description"

Lagally: would be nice to have a diagram too

David: ok
… Kaz, let's have some chat about how to upload the results
… using screen share, etc.

kaz: ok

David: next week, I'll be not available but Jack can

Lagally: ok. thanks!
… btw, I've just created a PR to upload your slides, David

PR 160 - Retail User Stories - Priorities (Conexxus)

David: some updates to be added

Lagally: can wait

PR 157

PR 157 - editorial fixes

Lagally: editorial fixes
… merged

PR 158

PR 158 - EdgeX Liaison Section

Lagally: EdgeX liaison
… please take a look

PR 156

PR 156 - Insert digital-twin-use-case.md and use-case-opc-ua-binding.md and retail for conexxus into index.html

Lagally: please take a look

OPC-UA use case

Lagally: shall we talk about the OPC-UA use case today?

sk: would have McCool as well
… so let's postpone

Lagally: ok
… aob for today?

(none)

[adjourned]

rragent, make log public

Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).