W3C

– DRAFT –
WoT Scripting API

24 April 2023

Attendees

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

Meeting minutes

Previous minutes

-> April 17

Cristiano: Minutes look good -> approved

Quick updates

Cristiano: General Issue: we should clean-up issues on Agenda

Publication Schedule/Decision April 2023

Cristiano: Got resolution in main call to publish after PR is merged

Daniel: Correct

Cristiano: Good

Kaz: We should be clear what should be integrated in this PR

Daniel: Correct, should remain editorial

Next charter review

Cristiano: remove the agenda item ?
… task is completed

Kaz: Proposed draft charter has been agreed
… topic can be removed

Daniel: Back to normative note?

Kaz: PLH and I have been proposing to use non-normative note
… WG approved draft and it was send to review

Cristiano: remove normative statements ?

Kaz: Yes

Cristiano: Kind of a surprise for me and Daniel

Zoltan: Do we have a formal resolution on publishing normative note?

Cristiano: Yes, I think we have one...

Kaz: we can still raise question/issue
… from my view-point normative note is problematic
… rather make normative REC document

Zoltan: W3C should make that clear in guidelines

Kaz: several view-points
… publishing normative note would be problematic
… can still do that if we have a resolution of the group

Kaz: dangerous .. not covered by the W3C Patent Policy

Cristiano: I will start some investigation and make sure that everybody is aware of it

Zoltan: I don't see a change to go on REC track
… what we wanted to have is the normative language
… I think we can keep the normative statements
… the other alternative would be to move work to CG

Cristiano: Still not covered by patent policy

PR

Align spec with INFRA

PR 469 - Align spec with INFRA

Cristiano: marked as editorial
… no major change in algoritmn
… spotted minor issue
… does not change text at all.. just about respec linking

Zoltan: Already corrected it
… we can have a last review if you want

Cristiano: I am okay with a final review
… let's give it this afternoon
… and than start publishing process

Zoltan: +1

Daniel: +1

Kaz: Should NOT integrate other stuff in this PR
… IF we do other editorial stuff we should send email

Cristiano: Okay I got your point

Update README.md with versioning information

PR 462 - Update README.md with versioning information

Cristiano: Explain versioning
… not about document itself
… I think we can merge PR as is and create yet another issue about the version number

Daniel: Not sure if we need to merge now.. could add it to this PR

Issues

Check if record is better than map Editorial

Issue 465 - Check if record is better than map

Zoltan: I think we are done with it with the pending PR

Cristiano: Will link PR

Update the "expand an ExposedThingInit" steps wrt security definitions

Issue 471 - Update the "expand an ExposedThingInit" steps wrt security definitions

Zoltan: I think text is improved in the meanwhile about security definitions
… we need to do a better prose
… more exact

Cristiano: in node-wot we also not fully follow the algorithm
… but that is a different aspect

Update listener internal slots to map<name, structure>

Issue 470 - Update listener internal slots to map<name, structure>

Zoltan: we should leave this after publication
… should check this by reading through
… i reformulated the prose a bit

Cristiano: Did you introduce DataHandler construct?

Zoltan: No

Cristiano: Okay, let add "enhancement" label

Check pair vs tuple usages Editorial

Issue 466 - Check pair vs tuple usages

Cristiano: pending PR will solve this?

Zoltan: Yes, I think this should be covered by PR 469

<kaz> PR 469 - Align spec with INFRA

Consider aligning with IntersectionObserver

Issue 427 - Consider aligning with IntersectionObserver

Cristiano: We can "copy" the design.. after publication
… even though we have different use-case
… not sure if it is great in Web of Things
… shall we keep it open?

Zoltan: Yes, prefer to keep it open
… should check what other specs do

Explain the new tagging mechanism for experimental features

Issue 458 - Explain the new tagging mechanism for experimental features

Cristiano: TODO left and missed explanation
… I think we can close issue after PR 462

<kaz> PR 462 - Update README.md with versioning information

Stale issues

Cristiano: I think we went over the issues I wanted to discuss
… let's adjourn

Minutes manually created (not a transcript), formatted by scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC).