W3C

– DRAFT –
WoT Architecture

03 March 2022

Attendees

Present
Kaz_Ashimura, Kunihiko_Toumura, Michael_Lagally, Michael_McCool, Ryuichi_Matsukura, Tomoaki_Mizushima
Regrets
-
Chair
Lagally
Scribe
kaz

Meeting minutes

Minutes

Feb-17

approved

Agenda

agenda for today

PRs

PR 707

PR 707 - Draft Implementation Report

McCool: suggest we merge this PR, and I and Fady will work on further updates
… my tool collaborating with his one
… have to fix some strange issues with the CSV files, though
… will check the categories, etc.

Lagally:: perhaps you could delete wrong parts?

McCool: caused by the tools

Lagally:: when would we be ready?
… CSV results, testimonials, ...

McCool: will clean it up

Lagally:: ok
… we still need another round
… let's visit this next week then

McCool: ok

PR 711

PR 711 - Definitions for Device, Service, etc.

McCool: definition for device, etc.

diff - 3. Terminology

McCool: regarding "Digital Twin", one actual physical device and virtual thing

Lagally:: (shows "Virtual Thing")

McCool: a service representing the functionality of a Thing

Lagally:: a bit overlap with shadow

Kaz: good starting point
… but a bit complicated, e.g., about "Virtual Thing"

McCool: yeah
… but not ambiguous

Lagally:: ok
… let's merge this
… and we can add further improvement if needed
… (then shows the Editor's note for "Partial TD")

McCool: producing method for more details
… we should check if the definition is true

Scripting API Note - 5.2 The produce() method

McCool: there are mandatory things which are not specified by the spec

Lagally:: will create an Issue and assign it to Daniel as the Scripting API Editor
… (creates a new issue)

<mlagally_> Issue 714 - Outdated note on partial TD ?

Lagally:: (going back to the Terminology)
… TD Fragment
… (another Editor's note there)

In JSON representation it must be a valid JSON document, however could
be just an inner structure omitting outer elements, curly braces etc.
present in a full TD. As a use case the TD Fragment is useful for
Discovery results returned by a JSON-Path query. See the WoT Discovery
specification [ WOT-DISCOVERY ] for more details.

McCool: my preference leave it out

Lagally:: (creates another new issue)

<mlagally_> Issue 715 - Verify note on TD Fragment

Lagally:: let's merge PR 711 itself now

(merged)

PR 712

PR 712 - Terminology diagram as worked out on the Architecture call on Feb 17th

McCool: let's merge this

Lagally:: if somebody has time, would be good to update it

McCool: is that an SVG file?

Lagally:: yes, SVG

(merged)

PR 704

PR 704 - restructuring lifecycle section

Lagally:: not really readable yet...

diff - 7.4 Lifecycle

Lagally:: let's look at the rendered version

preview - 7.4 Lifecycle

Lagally:: (goes through it)

McCool: typo with "becomer"
… reviewing the lifecycle diagram is on the tray of the Security TF as well
… I'm OK but the TF should review it again
… none of the diagrams are inconsistent with the previous discussions
… one thing not mentioned is security
… Security TF to review the section and think about additional description
… not wrong but stuff it out

Lagally:: absolutely
… section structure to be fixed, though
… (for "Thing Lifecycle", etc.)
… will fix it

PR 703

PR 703 - removing obsolete ednotes

Lagally:: (shows the "Files changed")

Files changed

(merged)

PR 700

PR 700 - Update Abstract

Lagally:: let's merge it

McCool: ok

(merged)

PR 713

PR 713 - Align the scripting interfaces in Architecture with the conformance classes in Scripting

Lagally:: (shoes the "Files changed")

Files changed

Lagally:: would merge this

(merged)

PR 695

PR 695 - fixes #688: Improving language, adding rfc2119 assertion

Lagally:: (shows "Files changed")

Files changed

Lagally:: adding Thing Model

McCool: fine
… definition for "Thing Directory"?
… also "Thing Description Directory"

Lagally:: let's see what we have for the Terminology

(missing)

Lagally:: let's create an issue for that

Issue 716 - change "Thing directory" to "Thing description directory"

Lagally:: any volunteers?
… (assigns it to McCool)
… some others could help

Lagally:: (goes back to PR 695 itself)
… would suggest we merge this

McCool: can you go back this again?

(look at the changes)

McCool: ok with merging this

(merged)

Issues

Issue 709

Issue 709 - Definitions for Virtual Thing, Shadow, and Digital Twins

(closed)

Issue 708

Issue 708 - Definitions for Entities that are Things

(closed)

Issue 698

Issue 698 - Revise Abstract

(closed)

Issue 708 (revisited)

Toumura: for issue 708, generated a diagram
… how to deal with that?

Lagally:: let's revisit it then

Toumura-san's comment including the diagram

Toumura: how to install it?
… should create a separate file?

Lagally:: yes, please

Lagally:: would be helpful to understand the concept

Toumura: should update this based on the recent discussion, though

Lagally:: you could create a PR for this

Kaz: +1

Toumura: ok

Issue 682

Issue 682 - clarify virtual thing

Lagally:: still need some more improvement?

McCool: it's confusing
… for me, "virtual" is somewhat software
… maybe we need another term for "Physical Thing"
… I've not commented about that

Lagally:: the question is that comes back to the TD discussion
… wondering how many people would know about RDF, etc.

McCool: let's see how people handle it, e.g., for building management
… Takena, Siemens, etc.

related PR 696 - New section on "virtual things", clarifying terminology

Lagally:: trying to think about use cases
… location of Things and geofencing
… but this PR 696 itself is a separate one

McCool: can merge it?

Lagally:: let's keep it now

AOB

Lagally:: we still have a couple of tasks for spec alignment

<mlagally_> https://github.com/w3c/wot-architecture/issues?q=is%3Aissue+is%3Aopen+label%3A%22spec+alignment%22

Lagally:: also we got a couple of new issues
… please raise your hands for the issues lacking assignees

[adjourned]

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