- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Thu, 28 May 2020 22:28:49 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2020/05/18-wot-minutes.html
also as text below.
Thanks a lot for taking the minutes, Zoltan!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT Scripting
18 May 2020
Attendees
Present
Cristiano_Aguzzi, Daniel_Peintner, Tomoaki_Mizushima,
Kaz_Ashimura, Zoltan_Kis
Regrets
Chair
Zoltan
Scribe
zkis
Contents
* [2]Topics
1. [3]approving previous minutes
2. [4]issue 201
3. [5]optionality of InteractionOptions properties
4. [6]AOB?
* [7]Summary of Action Items
* [8]Summary of Resolutions
__________________________________________________________
<scribe> scribe: zkis
<kaz> [Cristiano's IE procedure is ongoing, so he is an invited
guest for today again
approving previous minutes
<kaz> [9]May-11
[9] https://www.w3.org/2020/05/11-wot-minutes.html
Discussing about past minutes.
Zoltan: did Cristiano get enough input?
Cristiano: still waiting on input from Michael McCool
Zoltan: wondering if McCool delegated that to Oliver
Daniel: not sure if Oliver can provide the input
... not sure yet how to follow up with the flow
Cristiano: McCool asked to be tagged in the github issue and
will provide input
<cris> [10]https://github.com/w3c/wot-scripting-api/issues/214
[10] https://github.com/w3c/wot-scripting-api/issues/214
Zoltan: if 2 flows are working, let's merge and deal with the
rest later
Daniel: yes, after some more tests
... no more change in the core API, so should be fine
Zoltan: any issues with previous minutes?
Previous minutes approved.
<kaz> [fixed typo]
issue 201
[11]https://github.com/w3c/wot-scripting-api/issues/201
[11] https://github.com/w3c/wot-scripting-api/issues/201
Zoltan: explained why we considered using streams
Cristiano: explain any+algorithms
Zoltan: the algorithms are defined in the PR and describe what
exactly to return for "any"
Daniel: the more I look at this, the more I think to call
readProperty in simple way or low level way
Zoltan: instead of using 2 functions, let's use one function
returning a reader interface for the reply
Cristiano: I would also choose the second
Zoltan: what should we keep from the Body mixin?
Cristiano: we could go by use cases and see what we need in the
InteractionData interface
Zoltan: could you please help us with writing examples for each
type we are supporting?
Cristiano: yes, I've been doing that
Zoltan: let's work on that in a gist and then make a PR to
Scripting, we can make a chapter with Examples
Daniel: how do we handle writing and events?
Zoltan: we can handle write input as `any`, using
WritableStream
... do we need to pass contentType etc to writing?
Cristiano: we could just select the form
... but it's fine to pass also the contentType
Zoltan: then we'd need to define a data interface for writing
... implementations should write the Response object
... or other bindings
Cristiano: yes, we need to wotify the Fetch API
Zoltan: we are getting close to just relying on Fetch API
Cristiano: I think we need a more specific API
... since with Fetch we have some construct that just works for
HTTP
Zoltan: but that assumption comes with using only HTTP (and
CoAP)
Daniel: that assumes we limit ourselves to HTTP
Zoltan: OK, thanks, I will update the PR with these
optionality of InteractionOptions properties
see [12]https://github.com/w3c/wot-scripting-api/pull/209
[12] https://github.com/w3c/wot-scripting-api/pull/209
Daniel: The problem is that in TypeScript we need to represent
as interface.
Zoltan: let's translate Web IDL dictionaries to special
interface in TypeScript where all members are optional
Cristiano: agree
Zoltan: let's keep this open and check about index types etc
AOB?
AOB?
Cristiano: we'll need to discuss about TypeScript definitions
later
Zoltan: also, if you think we'd need to define a simple fetch
for TD's in the WoT namespace, please tell
Cristiano: yes, will think about that
[adjourned]
Summary of Action Items
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [13]scribe.perl version 1.154 ([14]CVS log)
$Date: 2020/05/22 05:58:29 $
[13] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[14] http://dev.w3.org/cvsweb/2002/scribe/
Received on Thursday, 28 May 2020 13:28:18 UTC