<scribe> scribe: zkis
<kaz> [Cristiano's IE procedure is ongoing, so he is an invited guest for today again
<kaz> May-11
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> 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]
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
see 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?
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]