W3C

– DRAFT –
WoT Scripting API

11 December 2023

Attendees

Present
Cistiano_Aguzzi, Daniel_Peintner, Jan_Romann, Kaz_Ashimura, Tomoaki_Mizushima, Zoltan_Kis
Regrets
-
Chair
Cristiano
Scribe
zkis

Meeting minutes

previous minutes

<kaz> Dec-4

Minutes approved.

next calls

Cristiano: we have a break until January 8.

PRs

PR #524

<cris_> PR 524 - Update text and examples regarding the fetching of TDs

Zoltan: we can only make normative statements on the implementations, not consumers

Kaz: we need to clarify section 5.1 vs. Appendix A.2. Maybe we could change the title of A.2 to clarify our intention.

<kaz> 5.1 Requesting a Thing Description

<kaz> A.2 Requesting and validating a TD

Daniel: it is OK to have the same title in both.

Zoltan: agree to include reference to A.2 from section 5.

Kaz: merging this PR 524 itself, then adding further improvement is also fine.

issues

<kaz> Remaining issues to to be closed

Cristiano: many issues have been updated, starting with the ones marked

Issue 360

<cris_> Issue 360 - Consider moving terminology definition to WoT Architecture

<JKRhb> +1

Zoltan: we have done the consideration, now we can close the issue

Kaz: would suggest two things, (1) quickly check with Lagally (I believe he is OK) and (2) we propose to the whole WoT WG how to close this kind of inactive issues in general as part of the new WoT WG policy.

Daniel: chatted with M Lagally, we should not overcomplicate it.

Zoltan: Architecture can pull the term if they want.

issue #427

<kaz> Issue 427 - Consider aligning with IntersectionObserver

Zoltan: we can close it

issue #443

<cris_> Issue 443 - Editorial: use map/exists instead of "defined", "exists" etc.

Zoltan: there are 3-4 places where this still needs correction.

issue #444

<cris_> Issue 444 - Editorial: use map/get when referring to object's properties

<kaz> (closed)

issue #216

<cris_> Issue 216 - Provide a convenient way to fetch a TD in simple case

Zoltan: just needs a reference before closing

<kaz> PR 441 - Align the discovery API with the Discovery spec

<kaz> (Issue 216 closed, since already fixed by PR 441)

issue #364

<cris_> Issue 364 - Discovery API - Alternatives

Cristiano: closing it

issue #374

<kaz> Issue 374 - Types for unreachable definitions cause unwanted comments

Jan: already resolved, can be closed.

Cristiano: actually depends on another issue, should keep it open

<kaz> related Issue 428 on bcherny/json-schema-to-typescript repo - Disable This interface was referenced by ... comments with --unreachableDefinitions

issue #390

<kaz> Issue 390 - Passing Credentials to Discovery Methods

Jan: how to distribute keys - but figured out how to do it

Zoltan: we need to explain the runtime assumptions, e.g. containers, provisioning, deploymemt etc.

Cristiano: create an issue for this

issue #391

<kaz> Issue 391 - Identify Scripting use-cases

Cristiano: it is a duplicate

Cristiano: closing it

issue #479

<kaz> Issue 479 - Improve Full Web IDL Appendix

Zoltan: this is a generated section, no need for decorations

Daniel: agree - any tweaks might interfere with generation

Cristiano: closing it

issue #422

<kaz> Issue 422 - Next Charter - Ideas / Proposals

Cristiano: Daniel will look at this offline and eventually close it.

Adjourned

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