W3C

– DRAFT –
WoT-WG - TD-TF - Slot 2

18 January 2024

Attendees

Present
Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan, Jan_Romann, Kaz_Ashimura, Kunihiko_Toumura, Mahda_Noura, Tomoaki_Mizushima
Regrets
Koster
Chair
Ege
Scribe
dape

Meeting minutes

Minutes of last week

Jan-11

Ege: Any concern?
… -> none -> minutes are approved

Binding Templates

PR 346

PR 346 - [Modbus] type fixes

Ege: Decided to merge asynchronously

Registry Analysis

Cristiano: PR 1161 not done yet

wot PR 1161 - docs: IANA procedures for registries summary

Cristiano: Proceeded further with different mechanism
… added description for "first come first serve"
… added also "Expert Review"
… do next: report rules for URI Schemes

Ege: Extend the generic policy?

Cristiano: Yes, but not much..
… e.g., lower-case / upper case sensitiveness
… usually additional constraints

Ege: Expert Review is going to be important for us

Cristiano: There is a dedicated section how to choose the "expert"
… a lot of information to digest.. takes a bit of time

Ege: Let's look at it next time again
… another aspect is whether we should start writing our requirements
… I think we can start
… and extend later what we learn

Cristiano: I think it is good to start
… like a TOC
… I have some ideas

Jan: Should we define use-cases as well where we can get requirements

Ege: Need a solution for a use-case/requirement
… maybe that is a good idea

Ege: We can add story-line about registry (in registry-analysis/Readme.md)
… a la "WoT to support multiple protocols" ...made interoperable with a descriptive approach

Kaz: Updated text might be also useful
… however, can use text from charter as well

Ege: Good point. I might have written some text for that

<kaz> WoT WG Charter

Ege: Maybe parts from Section 2 in charter document
… will do some homework later
… started PR 1169

<kaz> wot PR 1169 - Use Case and Story for Registries

Ege: please comment

Reviews of the individual bindings

Ege: related to DataMapping from yesterdays TD call

Ege: Interesting part: Missing protocol mechanisms
… e.g., we cannot describe a given mechanism in a TD
… people can also ask for help how to solve that in TD

Cristiano: e.g., MQTT pattern
… pretending we can describe it in a TD but we do not describe it

Ege: Is lack of documentation, not a new use case

Cristiano: Like the idea to ask experts for ideas

Ege: for example HiveMQ feedback
… with CoAP Klaus Hartke and Jan

Jan: I would know some more people

Ege: w.r.t. HTTP, people of WG are quite knowledgeable
… WebSocket needs people
… SSE needs people
… w.r.t. Modbus we got a lot of input already
… BACnet, quite recent, needs more time

Management

Project Management Proposal:

<kaz> project-management.md

wot-thing-description PR 1954 - Extending the project management proposal

Ege: Last week we extended it in coordination call
… issue coming from use case pipeline
… TF working on planning the work
… separation of concerns

Ege: Any points or objections to merge this PR?

Kaz: Any update like this is fine.
… we should think about which part is managed by use-case and Mizushima-San

Ege: Good point. Should be in line
… we might want to align the "naming"
… "gap analysis" is missing in my document
… I will link Process.md from wot-usecases

Ege: Can I merge 1954 ?

<cris_> +1

Ege: no objections -> merging

TD

Data Mapping

wot PR 1165 - Initial expansion of the DataMapping work item

Ege: Luca extended the PR
… I added related issues and added them to the PR
… others can do the same.. also from other task forces

Formatting before starting work

wot-thing-description Issue 1926 - Aligning formatting across files

Ege: Consistent way of working
… looked how prettier and editorconfig work together
… unfortunately we need to use both
… should keep them consistent

Ege: I don't think we should format output files which are generated

Ege: picked option "space" and "2 spaces" for indentation

Ege: In the end I can format all files in one go
… leads to a HUGE diff
… e.g. removing trailing whitespaces
… any concern or preferences on settings used

Cristiano: Style is okay.. no strong preference
… don't get some changes.. like line breaks

Daniel: I think there is a 80 character limit

Ege: "printWidth" might be the option
… default like 80

Cristiano: Should go with 120

Ege: BTW I excluded "publication" folder

Ege: Any other business?

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).