W3C

– DRAFT –
WoT Scripting API

17 October 2022

Attendees

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

Meeting minutes

Previous minutes

-> October-10

all: Minutes look good -> minutes are approved

Quick updates

Daniel: Cancellation Call on October 31?
… I am not available that day

Jan: I would be available

Kaz: Japanese meeting in Tokyo -> not available
… suggest to cancel call

Daniel: will send out email and update the calendar

PRs

feat: adjust ThingFilter interface

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

Daniel: constructor requires input

Jan: inspired by my implementation
… always required URL
… move URL outside of ThingFilter
… other discovery methods might not require url... could make it optional

Cristiano: understand the rational
… agree about line 3772
… wondering whether more changes make sense
… function to have direct() and directory() ...
… same with auto()
… a general question.. not related to this PR only

<zkis> https://www.w3.org/TR/wot-scripting-api/#the-start-method

Cristiano: overall discussion, see https://github.com/w3c/wot-scripting-api/issues/222

Jan: separate functions make sens

Zoltan: separate argument for each function needed
… idea was to be compatible... if changes happen in discovery we should not break
… need to extract value for developers
… being flexible enough
… current way is most flexible
… PlugFest might show benefits

Cristiano: use-case to find things around me ...
… is a valid use-case
… the function API shape looks better to me
… current design prone to error
… suggest to merge this PR as is and continue discussing the function API for discovery

Zoltan: looking at the discovery spec
… I think we can expose discovery options
… any() function does not sound right to me
… we have homework to do

Daniel: charter time frame is not enough for changing the API

Cristiano: agree, might need more time

Daniel: Should check algorithms also..

Jan: need to check more closely

Zoltan: algorithms might need changes
… breaking changes
… I am against the "required" changes
… seems against the discovery api as well
… would try to start with discovery spec and check APIs and shapes
… will make these comments in PR

Zoltan: Suggest we experiment with the API

Cristiano: Will do

Jan: Can try to work on that as well..

Kaz: not merge PR now and continue discussion

Daniel: Correct

Kaz: Useful to add label

Daniel: Agree, on the other hand I do not see which label to use.. since the outcome is very unclear for now

Issues

Definition missing for "discovery results"

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

Daniel: PR 405 broke definition

Zoltan: question whether we need discovery results" at all

Jan: I think we can remove it.. but will check
… will work on PR

<kaz> [adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 192 (Tue Jun 28 16:55:30 2022 UTC).