- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Mon, 14 Dec 2020 20:49:46 +0900
- To: public-wot-wg@w3.org
available at: https://www.w3.org/2020/11/30-wot-script-minutes.html also as text below. Thanks a lot for taking the minutes, Daniel! Kazuyuki --- [1]W3C [1] http://www.w3.org/ WoT Scripting API 30 Nov 2020 Attendees Present Kaz_Ashimura, Cristiano_Aguzzi, Daniel_Peintner, Tomoaki_Mizushima, Zoltan_Kis Regrets Chair Daniel Scribe dape Contents * [2]Topics 1. [3]Last minutes approval 2. [4]Minutes takers 3. [5]Publication 4. [6]Next Steps / open issues 5. [7]Next Calls 6. [8]marketing text * [9]Summary of Action Items * [10]Summary of Resolutions __________________________________________________________ Last minutes approval <scribe> scribe: dape <kaz> [11]Nov-23 [11] https://www.w3.org/2020/11/23-wot-script-minutes.html All: no objections -> approved Minutes takers Daniel: propose some kind of scribe role? Cristiano: scribe rotation Daniel: +1 Kaz: name of scribe to agenda, like in main call Daniel: task on my side , put agenda up before the call Cristiano: +1 Publication [12]https://www.w3.org/TR/wot-scripting-api/ [12] https://www.w3.org/TR/wot-scripting-api/ Daniel: Thank you kaz for the work and fixes Kaz: updated references Dp: I believe there were more links Kaz: Editors could help updating the links also ... several broken links Daniel: brink back the links Kaz fixed ... i will try to do provide PR <kaz> [13]Kaz's message sent to the Members list [13] https://lists.w3.org/Archives/Member/member-wot-wg/2020Nov/0019.html <kaz> [14]final message [14] https://lists.w3.org/Archives/Member/member-wot-wg/2020Nov/0022.html Kaz: I will take care, might be safer Daniel: Thanks, Kaz, see [15]https://github.com/w3c/wot-scripting-api/issues/284 [15] https://github.com/w3c/wot-scripting-api/issues/284 Next Steps / open issues Daniel: reference WoT documents, [16]https://github.com/w3c/wot-scripting-api/issues/278 [16] https://github.com/w3c/wot-scripting-api/issues/278 Kaz: Not sure what we should do best ... as long as we publish on the same day it is not a problem Daniel: let's update the links and do like we did in the past Kaz: depends on the document we refer to ... using dated-uri is the right way Daniel: I see kaz: my PR will include these updates Daniel: thanks! ... Issues 233, [17]https://github.com/w3c/wot-scripting-api/issues/227 [17] https://github.com/w3c/wot-scripting-api/issues/227 Cristiano: Old issues from wot repo Daniel: Scripting API versioning #224 Cristiano: Yes, can think about possible solutions ... context file version Daniel: This would disallow moving faster Cristiano: Sync between TD and ScriptingAPI Zoltan: should link the version itself, to be sure which algorithms are in place Daniel: 2 versions? ... TD version implicit? Cristiano/Zoltan: Yes, implicit Cristiano: start with 1.1 Zoltan: 3 numbers? Daniel: node-wot version in sync? Zoltan: No need, node-wot can link "specversion" or "apiversion" Cristiano: +1 Daniel: 2 points: apiversion in document and webidl should have a way to report version Zoltan: 1. WoT namespace readonly version ... 2. text, algorithm, describing what does it return ... align names, avoid clashes ... "version" should be ok ... use case for having version in script? Cristiano: displaying version I am running Zoltan: documentation information enough? Cristiano: Portable script running in different runtimes Zoltan: feature detection does not go by version ? ... currently we have 3 conformance classes ... version does not help here Cristiano: node has different version ... does it support runtime discovery ? ... like web workers and processes... depending on version? Next Calls Daniel: skip 21, 28 December and 4 January marketing text [18]https://w3c.github.io/wot-marketing/activities/tf-scripting / [18] https://w3c.github.io/wot-marketing/activities/tf-scripting/ Zoltan: use abstract from document <kaz> [adjourned] Summary of Action Items Summary of Resolutions [End of minutes] __________________________________________________________ Minutes manually created (not a transcript), formatted by David Booth's [19]scribe.perl version ([20]CVS log) $Date: 2020/12/14 11:47:18 $ [19] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [20] http://dev.w3.org/cvsweb/2002/scribe/
Received on Monday, 14 December 2020 11:49:50 UTC