Meeting minutes
Minutes Review
<kaz> Sep-4
Cristiano: Minutes look fine to me, if there are no objections I would publish them
No objections, minutes are approved
Publication Check
Cristiano: I noticed a minor issue, there is a problem with the WebIDL verification
… you mentioned, kaz, that you will talk to the Webmaster, this is something we need to keep in mind
Kaz: This is an issue with the namespaces, right?
Cristiano: Related to partial namespaces, maybe you have already fixed that. Let us know if we can help us
… issue is an old one, did not make any changes yet
ISSUE: w3c/
Cristiano: from the issue, I understood that you would make manual changes to the document before publication
<cris_> First comment: w3c/
<cris_> Group's proposed solution: w3c/
TPAC
Cristiano: I wanted to talk about TPAC, sadly Daniel is not here
… what I can say is that we had a nice conversation with the Web Agents group
… and I think we can find some synergies
… even though they have their own APIs and technologies
… sadly I could not attend the device interaction meeting due to conflicts
… in general, we could not tackle any Scripting API topics in the other meetings
… meetings were more focussed on high-level discussions
… relevant for us might be the Architecture changes, assertions are moved elsewhere, Servient concept could be defined in our document
Kaz: Please give information regarding the Web Agents CG also during the main call
… as you mentioned, main topic was refactoring and use case discussions, that is what the working group should focus on, including Scripting API topics
Zoltan: This is a TPAC + previous discussions feedback: I think we had a discussion with someone from Google that also dealt with creating a more consolidated API in WebIDLrather than JavaScript
… there are best practices we should adopt
Scripting API report
Cristiano: We should prepare a recap and report to the others what has changed and what is new in the Scripting API
… I would say that this won't happen in the next main call
… as we haven't agreed on a slot this week, but maybe in the next week such a report could happen
… should we simply ask we for a slot next week, Kaz? Or should we send an email and do it this week?
Kaz: I think this week's main call should be used for general reports from TPAC
… probably, we should arrange the Scripting API update next week or later
Cristiano: Then I would say that we can ask for a ten minute slot for next week
<kaz> s/present- Zoltan kis/(Zoltan leaves)/
Kaz: You can also send an email to the team-wot mailinglist to ask for a slot
Cristiano: Will do that
Cristiano: Our next focus should be to identify use cases
… after reviewing the use cases, we can focus on bugs in the specification
Issues
Cristiano: We have 65 open issues
… one thing that is currently missing is discovery
… we have open issues and PRs, what is missing is implementations
Jan: Will try to pick up existing PRs in node-wot to continue discussion in the upcoming weeks
TPAC (continued)
Cristiano: Do you have anything report regarding Scripting API here, Daniel?
Daniel: Not really, but I joined the Web Agents joint meeting and some chinese vendor showed an interesting demo based on WebAssembly
… not sure if we could adapt their approach
… apparently they haven't open-sourced it yet
… was a chinese university together with Huawei, if I remember correctly
Cristiano: Wasm is an interesting approach
… as it is an compiled language, which would improve the loading time in the browser
… however, the API would stay the same, only the implementation would change
… good to know, though
Kaz: Liason should mainly discussed during the main call
… even though Wasm could be an interesting improvement for node-wot or other implementations, it would not impact the Scripting API itself
… so it should be discussed during the main call
Cristiano: I think there is not that much to discuss here, but the Web Agents group is interesting in any case
Kaz: Even cooperation with other working groups such as the Web Payments API should be discussed during the main call so that others have the opportunity to notice it
Daniel: It was relatively specific to the Scripting API, therefore I mentioned it here. Other WGs are more interesting for the whole group
Kaz: I would suggest discussing liason topics in general during the main call
… as the topics can be interesting for all task forces
… my suggestion would be to make this report during the main call
Cristiano: I think it could be interesting to make the connection to projects like Solid and then report that in the main call
Kaz: Such a preliminary discussion is fine. In that case, let's consider today's discussion during this Scripting API call a preliminary discussion to clarify what to be reported during the main call from the Scripting TF participants.
Daniel: There was a discussion with Tim Berners-Lee with the result that Solid should be integrated with WoT
Cristiano: We can close the meeting early today and will continue next week
[adjourned]