W3C

– DRAFT –
WoT Scripting API

20 February 2023

Attendees

Present
Cristiano_Aguzzi, Daniel_Peintner, Kaz_Ashimura, Tomoaki_Mizushima, Zoltan_Kis
Regrets
-
Chair
-
Scribe
dape

Meeting minutes

Previous minutes

https://www.w3.org/2023/02/06-wot-script-minutes.html

Cristiano: 2 minor issues

Kaz: fixed

Cristiano: Minutes are accepted

Quick updates

Cristiano: checked list w.r.t. to spec improvements
… 1 month time-frame should be ok

Daniel: reasonable plan

Kaz: fine by me also
… could add it to schedule MD document

<kaz> https://github.com/w3c/wot/blob/main/charters/wg-2021-extension-plan.md

Cristiano: will create issue

Kaz: Or PR directly
… mention resolution in main call

Cristiano: Issue is # 453

<cris_> w3c/wot-scripting-api#453

PROPOSAL: Publish update to Scripting API document (18th of March)

PROPOSAL: Publish update to Scripting API document (18th of March). Task-forces finalizes review 2 weeks before the publication date.

PROPOSAL: Publish update to Scripting API document (27th of March). Task-force finalizes review 2 weeks before the publication date.

Zoltan: 2 weeks to handle the document
… I think this is not enough

Kaz: The plan is okay..
… 2 weeks for the whole group review, and we usually bring the draft for publication to the main call on Wednesday.

PROPOSAL: Publish update to Scripting API document (30th of March). Task-force finalizes review but please remember before the publication date (13th of March).

Cristiano: maybe shift by 1 or 2 weeks

PROPOSAL: Publish update to Scripting API document (14th of April). Task-force finalizes review 2 weeks before the publication date (27th of March).

Cristiano: Looks good to me

Daniel: +1

PROPOSAL: Publish update to Scripting API document (13th of April). Task-force finalizes review 2 weeks before the publication date (27th of March).

RESOLUTION: Publish update to Scripting API document (13th of April). Task-force finalizes review 2 weeks before the publication date (27th of March).

Next charter review

Current status

https://w3c.github.io/wot-charter-drafts/wot-wg-2023-draft.html

Cristiano: I think the description is fine

Kaz: mentioned during charter call. Charter draft still far from AC review
… need some more text to describe the WoT WG's intentions
… the Scripting API viewpoint s clear, though
… next point is Note or REC, and I talked with PLH about that again. with PLH
… we might want to have more discussions
… preliminary review is possible
… *nicer* to have Scripting API on REC track
… that's why we want to try normative Note track
… I personally still think it would be nicer to make it a REC, and PLH agrees. us to think about REC
… technically we can try normative note

Cristiano: I agree with stronger recommendation
… however, moving to REC might cause problems (2 major companies)
… how to convince them
… we can talk in main call

Daniel: I would still go with normative Note
… 2nd comment, I think security task-force want to move to the same note style

Summary of resolutions

  1. Publish update to Scripting API document (13th of April). Task-force finalizes review 2 weeks before the publication date (27th of March).
Minutes manually created (not a transcript), formatted by scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC).