Meeting minutes
<kaz> Patent Policy
Opening Session
<kaz> McCool's slides
McCool: Welcome to 3rd session
… 2 regular sessions
… and open day
… today we will be discussing use-cases and Japanese WoT CG
… <mentioning W3C patent policy>
Use Cases
Lagally: Let's jump into the presentations
… have some intro slides to give outline
… after that we have presentations from Conexxus, NHK, MiniApps, Digital Microscopes, and Retail
Lagally: Objective of use case task force
… identify and describe relevant use cases
… collect uses cases from W3C and other stakeholders
<Adam_> !!! Hello. I am presenting today on digital microscopes. I need the Webex link?
Lagally: collaborate with WoT task forces
… and external groups
… we ensure quality with a proper process
… document structure
… horizontal use-cases... applicable to vertical use-cases
… document has requirements section and liaison section
… we use light-weight Markdown/HTML template for initial use-case
… publication schedule
… first publication in May 2021
… new publication in December 2021
Conexxus
<Adam_> Thank you.
David: Conexxus, we write standards
… 1991 at W3C
… we are consumers
… not really creators of standards
… retails store
… interest in WoT- how to to write standards in the space
Jack: convenience stores.. retailers
… interested in data or sensors
… organizations have separate groups
… focused on general operation but also security, management, ...
… planning teams
… General Business Issues & Benefits
… Equipment & Facilities
… Sales & Marketing
… Safety & Compliance
… Operations
… dynamic group of people
… problems & challenges
… data in silos
… data is often limited .. and access is limited
… not shared across devices
… Common Data Points
… online vs offline status of device
… software level of a device
… status of peripherals such as displays, printers, ...
David: We are in the process of attempting our use-cases to GH
… 27 use-cases
… divided in several groups
… e.g., indoor sales devices
… target users: owner, manufacturer, ...
… interested in expected data
… need to know the status of devices like printers are up
… dependencies with TD and Discovery
<Zakim> kaz, you wanted to mention it's available at: https://
David: sometimes we have read-only information from sensors
… e.g., indoor door sensor use-case
… process: we want to know time.. who is accessing
… or locked in cooler et cetera
… safety issues, security issues
… the use-case templates helped us to fit in our use-cases
… stakeholders... we call them target users
… is about "who" wants the information
… e.g. use case: stop button
<kaz> https://
David: big red button for emergency case
… inside the store we need a better UI
Jack: button hit accidentally or on purpose
David: expected data is very thin
… devices are not created by us
… we would like to say here is a TD .. helps us to understand the data
… manufacturer providing input
Brian: Who to contact?
David: manufacturer
… helpful for us
… industry contact...
Lagally: Out of the box TDs, right?
David: Yes, correct
… opportunity to help with TDs
Kaz: Provided use-cases are very useful
… many use-cases ... maybe prioritize ?
David: Yes, will try to come up with top 3 list
MK: use-cases are more about how devices provide TDs
… how to interop across industry ?
… ThingModels being more generic?
Lagally: Suggest to tackle this observation in next use-case call
MiniApps
Qing: from MiniApps groups
… Alibaba group
… miniApp CG and WG at W3C
… this year we started work on IoT
… MiniApp overview
… new format of mobile application
… running on top of native apps or os
… web-like, free installation
… What is MiniApp for IoT
… running on IoT devices
… similar architecture...
… run on top if IoT OS
… unique features: packaging, life-cycle
… Some use cases
… -> switch panel
<xfq> MiniApp for IoT
Qing: -> smart speaker
… -> checkout pad
Qing: -> video conference terminal
… -> face recognition terminal
… -> locator
… Hardware supporting MiniApp for IoT
… - LTE Cat 1 Module
… - Wi-Fi module
… - AliOS things
… Benefits of MiniApp for IoT
… traditionally developers write code -> obj -> binary
… with MiniApps, Coding based on libraries/API (JS+JSON)
… easy to integrate
… web developers can write apps for IoT
… Develop and Debug
… local write vs. online write
… How to develop miniApp for IoT
… use app.js + app.json -> single page miniApp application
… more files possible like XML and CSS
… packaging structure
… working experience similar to mobile
… we are working on spec called miniApp for IoT
… packaging / lifecycle / components
… we think there is joint work & discussions
McCool: Difference to WebApps?
Qing: broader aspect
… runtime is different
… not used in web only, native also
Ege: Use miniApp to attach HW
… can other packages be used?
Qing: other packages can be used for UI
… for HW limited to miniApp API
Kaz: Device capability description ? Is there a model?
Qing: we have data model ... called data profile
… similar to WoT
… service, actions, events
Kaz: We can discuss data-format in future
Lagally: Time is running
… suggest to move the question to next use-case call
Qing: I can attend the call
… questions beforehand would be even better
Lagally: Okay, please provide questions ahead of time
<Zakim> pchampin, you wanted to ask how WASM / WASI fit in that picture
<pchampin> my question was about WebAssembly and WASI. Whether the mini-app group had considered them in their architecture.
NHK
<kaz> NHK's slides
Endo: Hiroki Endo from NHK
… Objective
… future broadcaster will deliver content not only for TV sets but also for various IoT devices
… IoT-based media framework
… content according different devices
… and user
… 2 implementations
… 1. Physical laboratory
… space is modeled on the interior of a house
… <video>
… track people -> update interest if back to home
… e.g. soccer games ... TV informs other devices about goal
… in half time coffee machine starts
… or weather warnings will be shown on TV screen and other devices
… System configuration uses node-RED
… using WoT device emulator
… provided toe the PlugFest at TPAC 2021
… 2. Virtual Web app
… select device where you will go
… select what you will watch
… location can be changed
… typhon alert will be shown
… each device has TD
… node-wot library used to interact with devices
… Findings
… issues on discovery
… broadcaster cannot handle WoT devices in user environment
… typically houses to not have network manager
… we implemented DNS-SD for local networks
… Action affordance for media presentations
… need link information to WoT actions and content
… mediaType of content
… corresponding action type like "playAudio"
Lagally: w.r.t. action types, simple string?
Endo: not enough to determine media
… TD don't define schema
Lagally: Write-up of gaps helps us to understand the problem better
… use-case description with the gaps
Endo: Yes, will try to work on it
Kaz: Wanted to help Endo-san. MEIG also had discussion yesterday, and there was some discussion on having a virtual device for media distribution. For that purpose, various mediaTypes can be specified and also various actions can be specified to handle video distribution/playback/recording services. Further detail to be provided by NHK based on this use case and implementation.
Sebastian: I liked the showcase
… w.r.t. to the action gap
… maybe additional context may help
… special context for broadcasters
… w.r.t. mediaType, we can use IANA media-types
<pchampin> is "mediaType" in this slide really meant as in IANA's media-types?
<pchampin> looks like something different
<pchampin> considering an ontology that could be used here: https://
McCool: Orchestration ?
Endo: Our implementation is limited
<mlagally_> I think it is a description of a media stream, this could be complex, such as a MPEG DASH media descriptors, ...
Endo: SPARQL search
Kaz/ML: invite Endo-san to use-case call
Digital Microscopes
<McCool> (are there slides? Not seeing anything)
Adam: Digital Microscopes ... high quality
… share work
… no manual adjustment needed
… 4 concepts
… 1. digital microscopes
… 2. mixed reality collaborative spaces
… 3. Services
… - free vs paid et cetera
… 4. Multimodal user interfaces
… 2 Examples
… 1. A droplet water
… 2. A Living cell
… WoT topics
… Digital Microscopes are important class of devices
… streams could contain metadata
… using computer vision
… semantic labels
… requirements not addressed: interconnecting services
… Considerations
… - Security
… - Privacy
… - Accessibility
… - Internationalization
Lagally: Question: When you think about controlling microscopes ?
… who determines this living object
Adam: AI could do automatic focusing but also manual override
McCool: Video streaming and AI are important use-cases
Kaz: Microscope requires precise handling
… we can think about meta framework for handling precise movement and video streaming along with AI.
… recall Takenaka's building management system.
… would get actual use case description based on this idea.
Lagally: Adam has provided use-case already
… follow-up conversation during the Use Cases call.
… medical category or lab category
<kaz> Adam's use case
Retail use case with ECLASS semantics
<kaz> Retail use case with ECLASS semantics #140
Christian: Sebastian and I worked on use-case document
Christian: working on an rdf representation of the eclass standard
… with sebastian we have worked on a use case document, it is on github
Christian: (shows the uc document)
… motivation is to embed device information
… all data that is needed for purchasing, sales, product master data
Christian: internationalization is very important and we have different languages available
Christian: we need a way to include these models in TD, like templates
Christian: there are other related standards like gs1 and w3c data exchange group
Ege: can we link via link via the links container?
Christian: yes
Sebastian: live data annotations will be also possible
… that way we can annotate TDs in the interaction level
Christian: (shows CDP interface of eclass)
Christian: we have this list of devices in different application domains
Kaz: 2 comments. regarding the use case itself, it would be better to have concrete use case description rather than general concept on using ECLASS ontology with TD
Kaz: also we need to have further discussion on which part of the ECLASS ontology should be included in the TD via the "@context" field.
... We've been talking with both ECLASS and ISO TC184/SC4 about that, but it's still our big question.
Lagally: can you elaborate on the relation to the other standards
Sebastian: it was an input from your side but we can add more information
Christian: I can do it
McCool: let's have a 10 minute break
<kaz> [10-min break]
<kaz> milestones calc
WoT Japanese CG update
<kaz> Mizushima-san's slides
Mizushima: w3c standardization has started to tackle the interoperability problem
Mizushima: improve the future society via improving the e.g. infrastructure
Mizushima: main communication language is japanese
Mizushima: we have 4 task forces, use cases, outreach, deployment and translation
… translation tf is working on translating td and architecture recommendations
Mizushima: we have a tutorial page
Mizushima: and also this is the japanese version of wot architecture
Mizushima: we want to exchange with the WG and IG, like today's report
Lagally: the CG is bringing input to the IG right?
Mizushima: yes correct
Lagally: thank you for reaching out to japanese manufacturers
Kaz: will help Mizushima-san and Toumura-san. note Kasuya-san from Takenaka is also joining the CG
McCool: reaching out to the japanese community is very important, thank you
Kaz thank you all the task force leaders for their efforts
Charter Discussion
McCool: we need to discuss our deliverables and schedule
… schedule is July 26 for REC, June 21 for PR and CR is May 5. FPWD Jan 13
… mid april for PR and mid march for CR are more realistic deadline
<sebastian> sorry, I have to leave the meeting
<sebastian> +1 for the charter extension
Ege: (goes through the definitions of the CR, PR and REC)
McCool: testfest would be by mid february meaning that the specs should freeze by 31.12
Kaz: given the upcoming wide reviews and implementation experience, would agree we freeze the features by the end of this year. btw, is the "current" drafts stable enough? For example, would it possible for us to finalize the drafts right away?
McCool: 2.0 needs to be pushed to next charter
McCool: that's a good question. may need to rollback some things for KISS, compatibility
Ege: wondering about testing
McCool: we should limit the amount of rec track publications
McCool: we have 3 implementations for Discovery already
… what about Profile?
McCool: profile spec is not complete, so we should do that before talking about testing
Lagally: we need a stable TD spec first for the profile spec
McCool: we should freeze TD so that profile can base on that
McCool: we can mark more things at risk this time
McCool: since sebastian is not here, we should wait his opinion
Kaz: we can do a tentative resolution now, and check with Sebastian during the vF2F tomorrow.
<McCool> proposal: request a 6mo extension to the WG charter, based on the following plan: 1. roll back TD spec to 1.1 features by Nov 30; 2. feature freeze TD 1.1 spec by Dec 15; 3. feature freeze Discovery spec by Dec 15; 4. feature freeze Profile spec by Jan 31; 5. Testfest in mid-Feb; 6. CR transition in mid-March; PR transition in mid-April; REC transition before end of extended charter end of July
Resolution: (tentative) request a 6mo extension to the WG charter, based on the following plan: 1. roll back TD spec to 1.1 features by Nov 30; 2. feature freeze TD 1.1 spec by Dec 15; 3. feature freeze Discovery spec by Dec 15; 4. feature freeze Profile spec by Jan 31; 5. Testfest in mid-Feb; 6. CR transition in mid-March; PR transition in mid-April; REC transition before end of extended charter end of July
AOB?
IG charter updates addressing W3M comments #998
McCool: IG Charter updated
… comments welcome for the PR
Kaz: when to review it?
McCool: next main call at the latest
[adjourned]