W3C

- DRAFT -

WoT Scripting API

10 Aug 2020

Attendees

Present
Kaz_Ashimura, Cristiano_Aguzzi, Daniel_Peintner, Zoltan_Kis, Tomoaki_Mizushima
Regrets
Chair
Zoltan
Scribe
zkis

Contents


<scribe> scribe: zkis

Quick updates

Kaz: some info from the main call last week
... we had several events and some of them, e.g., MiniApps, would possibly be related to Scripting improvements

Zoltan: do we have issues for these?

Kaz: no GitHub issues have been created but we'll invite some of the contact persons to one of the WoT main calls and/or the TPAC joint meeting

<kaz> August-5 Main call minutes

<kaz> TPAC vF2F wiki

Kaz: I suggested to have a joint meeting on use cases first, before any API changes

Past minutes

<kaz> July-27 minutes

Approved

Issue 230

<kaz> Issue 230

Daniel: we should use the dated version of TR links

Kaz: W3C encourages using dated versions

Zoltan: I don't see the value of making a release just because some other documents changed

Cristiano: I would also prefer the dated URLs for reference purposes
... I can also see the point in using the latest TR version

Zoltan: the publication checker anyway needs the dated URL versions

RESOLUTION: we change all referred URLs to dated versions

https://en.wikipedia.org/wiki/Plugtest#:~:text=A%20plugtest%20or%20plugfest%20is,with%20those%20of%20other%20manufacturers.

Zoltan: we can use the word "plugfest" or "plugtest"

Ege's feedback in PDF for issue 230

<kaz> Ege's comments in PDF

Zoltan: would prefer comments in github as it's difficult to spot the issues

Daniel: maybe we should split and create PR's or issues

Cristiano: I can also help in this

Zoltan: OK, then we can split the work

Daniel: will include a comment in the issue on the split

Issue 228 - wot issue 235

Cristiano: these are coming from other TF discussions

<kaz> wot-scripting issue 228

<kaz> wot issue 235

Zoltan: we need to make the explanation explicit
... meaning to update the rationale.md
... we can also link the issue that have been discussing the topic

Issue 227 - wot issue 233

<kaz> wot-scripting issue 227

<kaz> wot issue #233

Zoltan: let's leave these issues (228 and 227) open, they have been discussed in the past as well

Issue 224

<kaz> Issue 224

Cristiano: we can add the version property of the WOT object
... also discussed in the TD TF, and they suggested looking at the JSON-LD group's handling of versioning

Daniel: we also tried to keep the version info in node-wot, and it should be the same

Daniel is adding a comment

Cristiano: also, how can we connect the spec version with the implementations and Web IDL

Zoltan: we should declare the version in the spec text, and include links in the spec to past versions

Daniel: we can also flag in the text (without changing the API)

Zoltan: I can create a PR on this

Next meeting

<dape> https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#Agenda

Zoltan: will publish the agenda

[adjourned]

Summary of Action Items

Summary of Resolutions

  1. we change all referred URLs to dated versions
[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/08/11 07:00:51 $