W3C

– DRAFT –
WoT-WG/IG

24 July 2024

Attendees

Present
David_Ezell, Ege_Korkan, Kaz_Ashimura, Kunihiko_Toumura, Luca_Barbato, Mahda_Noura, Michael_Koster, Sebastian_Kaebisch, Tetsushi_Matsuda, Tomoaki_Mizushima
Regrets
McCool
Chair
Koster, Sebastian
Scribe
mjk, kaz

Meeting minutes

invited expert

Kaz: will contact the IE candidate person, Charith, and ask him about his interest in making contribution for TFs

Minutes

July-17

Sebastian: (goes through the minutes)

(typo fixed)

approved

Quick items

Web-based Digital Twins for Smart Cities IG

Sebastian: one comment from a Member

Kaz: the deadline for the response is over
… so working with PLH and TiLT Team to wrap it up

WebTransport

Sebastian: we'd work with them more closely
… could provide a comment to the AC review

AC review form (Member-only)

Sebastian: Luca already gave a comment about our collaboration
… I also made a similar comment
… the deadline is Aug-23

Planning document under the main wot repo

Ege: we started initial planning under the wot repo

wot repo's planning area

Ege: but the content is getting more and more TF-specific these days
… now the question is if we should move this content to the TF side

Sebastian: good question
… on one side, good to have all the planning information at the central repo
… but having details on the TF side would also make sense

Kaz: depends on who to maintain the content
… if the TD.Next documents would be mainly maintained by the TD TF, those documents should be managed under wot-thing-description repo

Sebastian: would have planning documents for the other TFs also

Luca: no strong opinion
… but would like to make sure we have enough consensus about what to be put where
… e.g., Profile TF have enough information to be put here

Sebastian: yeah
… please note that the question is not only about Profile, but our policy in general
… should all the planning docs be maintained under the wot repo (as currently we do)
… or should some of the TF-specific contents to be maintained under the TF repos

Luca: don't see any problems with either option

Sebastian: ok
… maybe we can tidy up the current resources under the wot repo first

Ege: will do

Meetups

WoT CG

Ege: would like to have a few meetings at TPAC 2024

WoT JP CG

Sebastian: event this week?

Mizushima: the JP CG would use the official Use Case template for the event
… discussed that idea during the UC call 2 weeks ago

UC call on July-10

1. The WoT-JP CG would like to copy the WoT Use Case template to their repository.
2. Then they would like to describe their use cases in Japanese using the template.
3. And bring the use cases back to the WoT Use Cases TF after translating the use cases in Engish.
4. The original Japanese use cases should be archived so they are available for future reference.

Sebastian: should not be a problem

Mizushima: thought the JP CG got basic approval during the UC TF call
… but still need to get an IG-wide approval

Kaz: Re-using the UC template itself should be fine, but the template is not fixed yet. Also we as the WoT IG need to check the feasibility of the template ourselves beforehand. So we need to see when to let the JP CG use the template.

Sebastian: but they're planning to use the template on July-26?

Kaz: already suggested to them they not use the template for the event on July 26
… but start with initial discussion about possible use cases
… they can still look into the template and examples, though

Sebastian: ok
… I'm still wondering about the procedure
… planning to bring the JP CG's use cases back to the IG officially?
… maybe don't know yet?

Mizushima: yeah

Sebastian: so you'd like to present JP CG's use cases back to the whole WoT IG. right?

Mizushima: right

Kaz: great
… and we need to ask them to clarify the plan :)

proposal: WoT-IG is OK with WoT-JP CG's reusing the UC template, but when/how to let them use it should be discussed by the UC TF a bit more

RESOLUTION: WoT-IG is OK with WoT-JP CG's reusing the UC template, but when/how to let them use it should be discussed by the UC TF a bit more

Liaisons

OPC Foundation

Sebastian: kick off meeting on OPC UA binding WG on July 30
… also the W3C Liaison table has been updated with Kaz as the WoT contact

W3C Liaison table for OPC Foundation

ETSI ISG CIM for NGSI-LD

Sebastian: similar situation with ETSI

W3C Liaison table for ETSI

Sebastian: a lot of contacts there but Kaz has been added as WoT contact there as well

Schedule

Holidays and Events

Sebastian: upcoming holidays in Canada, Germany and Japan
… then TPAC 2024 will be held in September
… also note summer vacations planned in general late August
… anything else?

(none)

F2F

TPAC 2024

TPAC 2024 WoT wiki

Sebastian: no big change so far
… breakouts are listed on the GitHub repo

GitHub issues for TPAC 2024 breakouts

Sebastian: current expectation is:
… 1. AI Model Management (McCool, Zoltan)
… 2. Web-based Digital Tns for Smart Cities (Kaz, Koster)
… 3. Cloud-edge-client computing (McCool, Zoltan)

WoT Week

WoT Week wiki

Sebastian: Plugfest, OpenDay and F2F
… we'll discuss the Plugfest topics after the main call topics today
… please put your name if you'd attend the event

Policies

Sebastian: anything for today?

Policy area on wot repo

PR 1181

wot PR 1181 - Assertion id policy proposal

Ege: initial proposal for assertion ID management
… (goes through the proposal)

preview

[[ SPECACRO-SCOPE-CUSTOM ]]

Sebastian: seems good

Kaz: ok as an initial proposal
… so OK with merging this

Sebastian: any objections?

(none)

merged

Sebastian: in two weeks, we can revisit this and see if we can move this to an official policy

PR 1201

wot PR 1201 - Initial Connection Figures

Ege: still need discussion, and will be discussed during the TD call today

Marketing

List of adopters

Ege: had discussion with Coralie
… not good to put the adopter information including non-Members on the official WoT-IG/WG page

Kaz: there are two separate points here, and we should think about those points carefully
… the Marketing TF should discuss which information to be managed by whom during the next Marketing call
… and get back to the whole IG/WG based on the TF conclusion

Sebastian: ok

<Ege> https://landscape.json-schema.org/ is done for JSON Schema. Such a page is easy to generate and can be maintained by the CG. Official page can refer to it

Profile

Luca: had discussion with Ben, etc.

July-17 Profile minutes

Luca: Ben has prepared some document on GitHub

<luca_barbato> wot-profile PR 417 - A start on use cases and requirements for Profiles 2.0

<luca_barbato> wot-profile Issue 416 - Discuss All the layers profiles can cover

Sebastian: would look into the PR and Issue
… and would suggest people also look into them
… good to have this discussion
… next steps for Profile to be discussed

Luca: there is no agreement yet
… would be great to have Ben and Koster at once for further discussion

Kaz: let's ask both of them to join the next Profile call on July 31 :)

Luca: will do
… (provides some more detail about the situation)

Sebastian: please take a look at the PR and the Issue
… and join the next call on July 31

Koster: will join it

(kaz whispers we're out of time for the main call topics :)

TF Reports

TD

Mahda: talked about tool chain

July-17 TD minutes

[adjourned; continue to use the same Zoom; but will use #wot-pf as IRC ]

Summary of resolutions

  1. WoT-IG is OK with WoT-JP CG's reusing the UC template, but when/how to let them use it should be discussed by the UC TF a bit more
Minutes manually created (not a transcript), formatted by scribe.perl version 227 (Fri Jul 19 09:58:06 2024 UTC).