W3C

- DRAFT -

WoT-Scripting

02 Mar 2020

Attendees

Present
Kaz_Ashimura, Zoltan_Kis, Tomoaki_Mizushima, Daniel_Peintner
Regrets
Ege_Korkan
Chair
Zoltan
Scribe
kaz, zkis

Contents


<inserted> scribenick: kaz

Previous minutes

<kaz> Feb-24 minutes

Zoltan: any problems with the above minutes?
... I got an action to generate a PR and have crated one

(no objections)

Zoltan: the minutes have been accepted

<inserted> scribenick: zkis

PR

Zoltan: I had an action last meeting, here is the PR for that:

https://github.com/w3c/wot-scripting-api/pull/205

https://github.com/w3c/wot-scripting-api/pull/205/files

Zoltan: It's just a note in the spec and explainer

Issues

Issue 200: https://github.com/w3c/wot-scripting-api/issues/200

Zoltan: I will make a PR for making error usage more consistent and also to factor out error reporting from bindings

Issue 205: https://github.com/w3c/wot-scripting-api/issues/206

<kaz> (Issue on Discvoery API)

<kaz> (Zoltan asks people to join the Discovery TF call as well)

Issue 204: https://github.com/w3c/wot-scripting-api/issues/204

<kaz> (Issue on semantic APIs created by Daniel)

Zoltan: The semantic API suggested by Michael Koster is like the DOM API with semantic annotations
... It's similar to our former approach to the API

Daniel: this would be easy to adapt to node-wot
... we should keep the core API as it is now and extend it

Issue 201: https://github.com/w3c/wot-scripting-api/issues/201

<kaz> (interaction algorithms for Forms, contentType, DataSchema)

Zoltan: This is a bit tricky since we need to define a lot of things that are defined in the TD.
... We can make a note instead of embedding in the algorithms.

Daniel: yes, we should stick with a note.

adjourned

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2020/03/02 12:47:48 $