<scribe> scribe: dape
<kaz> Nov-23
All: no objections -> approved
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
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> Kaz's message sent to the Members list
<kaz> final message
Kaz: I will take care, might be safer
Daniel: Thanks, Kaz, see https://github.com/w3c/wot-scripting-api/issues/284
Daniel: reference WoT documents, 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, 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?
Daniel: skip 21, 28 December and 4 January
https://w3c.github.io/wot-marketing/activities/tf-scripting/
Zoltan: use abstract from document
<kaz> [adjourned]