W3C

– DRAFT –
WoT-WG/IG

15 May 2024

Attendees

Present
Daniel_Peintner, David_Ezell, Ege_Korkan, Kaz_Ashimura, Kunihiko_Toumura, Luca_Barbato, Michael_Koster, Michael_McCool, Tetsushi_Matsuda, Tomoaki_Mizushima
Regrets
Sebastian
Chair
Koster, McCool
Scribe
mjk

Meeting minutes

Invited Expert application

Kaz: not ready yet but will contact them

Minutes from May 8

<kaz> May-8

McCool: any objections?
… no objections, minutes to be published

Quick Items

McCool: IG charter still in AC review, expect to be active later in May or Early June

Errata

McCool: defer until Ege joins

McCool: any notices?

Meetups

McCool: May 16 CG meeting with Solid CG

McCool: WoT JP CG undates:

Mizushima: no updates

Holidays ,availability, and cancellations

<Zakim> dape, you wanted to remove first 3 lines for cancellations

McCool: (review schedule items)

Kaz: Will have some unavailability in early June, will add a note with dates

Publications

McCool: there is a binding templates Note for publication

<mm> proposal: Confirm the TD TF resolution to publish an updated WG Note for Binding Templates base on the current ED version: https://www.w3.org/2024/05/02-wot-td-minutes.html#r01

Kaz: Ege sent out a 2 week notice

<kaz> Ege's all for Review

McCool: any objections to the resolution on the table?

McCool: no objections noted

RESOLUTION: Confirm the TD TF resolution to publish an updated WG Note for Binding Templates base on the current ED version: https://www.w3.org/2024/05/02-wot-td-minutes.html#r01

Kaz: there is still a 2 week notice based on the discussion last week period, but the resolution is ready to publish

McCool: resolution accepted

TF leads needed for Security and Discovery

JSON Schema

Ege: no update yet, waiting to hear from W3C

Ege: there are comments from WoT members and JSON Schema members

Kaz: Will talk with Philippe Le Hegaret and put on the agenda for the Strategy Team call

<Ege> https://landscape.json-schema.org/

Errata - revisited

McCool: we discussed the issue last week. We wanted to make it more deliberate, less automated

Ege: we should be careful when using labels that trigger automation

Ege: we need to change the procedure to use text [POSSIBLE ERRATA] in the issue name instead of a label
… Then a label will be added by the responsible Task Force
… and we will remove the script so the issue and label will be updated manually

Ege: each task force will need to copy the procedure
… once we agree, we will create a policy document

McCool: agree, we could use the script if it's manually triggered

Kaz: OK with this procedure but we should write the policy document
… and we should avoid misusage of "Errata" label and disable the automation

Ege: should the automation be disabled for all documents?

McCool: for all WoT deliverables

<mm> proposal: Disable the automatic errata mechanism for all WoT WG REC Deliverables while an errata policy is being decided.

Ege: that looks good

Kaz: make sure the current Errata is included in the new system

<mm> proposal: Disable the automatic errata mechanism for all WoT WG REC Deliverables while an errata policy is being decided. Ensure that current errata have not been deleted or modified by the automatic mechanism and rectify if necessary.

McCool: will create a separate resolution for the new policy when it is ready

RESOLUTION: Disable the automatic errata mechanism for all WoT WG REC Deliverables while an errata policy is being decided. Ensure that current errata have not been deleted or modified by the automatic mechanism and rectify if necessary.

McCool: any objections?
… approved

F2F planning

McCool: 2 meetings to plan, TPAC in Anaheim CA and our WoT F2F in Munich WoT@Industry

McCool: maybe more people would be interested interested in attending physically in the WoT F2F than TPAC

<kaz> F2F wiki

McCool: (review time slots for TPAC remote participation)

<Ege> Friday means saturday morning in japan btw

<kaz> https://www.w3.org/2002/09/wbs/1/GroupsTPAC2023/results

Kaz: this might be useful
… we created wiki entries for the participation

McCool: there is nothing there and it's due on May 20th

Kaz: Thursday looks possible

McCool: how many people should we estimate? 5 or 10?

Ege: From Siemens there will be at best one person

<kaz> [[ FYI, 14:00 Anaheim is 23:00 CEST, 6:00 JST ]]

McCool: myself, Kaz, and Sebastian probably

McCool: do we want to do joint calls, what are the conflicts

Ege: there will be a JSON Schema breakout
… probably won't need a call with JSON-LD

Kaz: Also RDF-star.

Kaz: RDF-Star will meet in person

McCool: RDF-Star is to support property graphs

McCool: would a joint meeting with Solid be useful?

Ege: depending on the result of the CG meeting on the 16th

<kaz> w3c/strategy#377

McCool: we could schedule a call at some other time, no need to load the TPAC schedule

<kaz> https://www.w3.org/WoT/IG/wiki/Wiki_for_F2F_2024_planning

David: Added to the wiki, was it in the right place?
… there were no other entries

Kaz: that is the correct URL

McCool: will publish something on Monday

subtolic: WoT@Inuustry

McCool: proposing Monday as open day to drive engagement
… looks like November 25th-29th

McCool: we could split the venue between Siemens and Microsoft
… please update the wiki and let us know your participation

David: the wiki still has some incorrect dates

McCool: will update and correct

McCool: we're planning a virtual F2F in June, discuss next week

McCool: any other business?

Ege: TD sub-task force meetings invitation

McCool: adjourned

Summary of resolutions

  1. Confirm the TD TF resolution to publish an updated WG Note for Binding Templates base on the current ED version: https://www.w3.org/2024/05/02-wot-td-minutes.html#r01
  2. Disable the automatic errata mechanism for all WoT WG REC Deliverables while an errata policy is being decided. Ensure that current errata have not been deleted or modified by the automatic mechanism and rectify if necessary.
Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).