- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Tue, 19 Jan 2021 18:34:16 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2020/12/14-wot-script-minutes.html
also as text below.
Thanks a lot for taking the minutes, Cristiano!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
WoT Scripting API
14 Dec 2020
[2]Agenda
[2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#14_December_2020
Attendees
Present
Kaz_Ashimura, Daniel_Peintner, Cristiano_Aguzzi,
Tomoaki_Mizushima, Zoltan_Kis
Regrets
Chair
Daniel
Scribe
cris
Contents
* [3]Topics
1. [4]Agenda
2. [5]Scripting TF lead
3. [6]Previous minutes
4. [7]Marketing text
5. [8]Scripting issues
6. [9]Architecture terminology
7. [10]Upcoming calls
* [11]Summary of Action Items
* [12]Summary of Resolutions
__________________________________________________________
Agenda
Daniel: goes through the agenda topics
... anything to add to the agenda?
Scripting TF lead
Kaz: last week Sebastian asked who should lead this scripting
API task force
... Can we discuss it today? I myself am OK if two of you would
co-moderate the TF.
Daniel: sure, I think we should talk about it in the marketing
agenda item
... is it ok?
Kaz: ok
Previous minutes
<dape> last minutes
[13]https://www.w3.org/2020/12/07-wot-script-minutes.html
[13] https://www.w3.org/2020/12/07-wot-script-minutes.html
Daniel: we had a discussion about updating links
... then we had a discussion about discovery
Zoltan: yes, we discussed the latest changing in the discovery
document and how that will effect the scripting api
Daniel: did you take any resolution?
Zoltan: not much, we just decided to monitor the discovery task
force
Daniel: should we publish the minutes?
... ok minutes accepted
Marketing text
Daniel: in the new website it will be a section about the
activities and one dedicated to our group
... mccool proposed a template
... I sketched a simple example to what we can put there
<dape> Proposal
[14]https://github.com/w3c/wot-marketing/pull/102
[14] https://github.com/w3c/wot-marketing/pull/102
Daniel: the template contains a place for the task leader, what
should we put there? my proposal is to have three of us as
leaders (Zoltan Daniel and Cristiano)
Kaz: Usually, having three task leaders is not really
recommended
... Zoltan could be listed as editor
Zoltan: it makes sense
Daniel: I feel that zoltan is still doing a lot, he deserves to
be there
Zoltan: I have another proposal, let's chose one person as task
force leader
... we can do a rotation
... now I like to have Daniel for his involvement in TD task
force
Kaz: if we do a rotation, we should clarify the process
... moderator is not just an active participant
Cristiano: I'm fine with the current state and having Daniel as
task leader
Kaz: my suggestion is simply asking Daniel to take the lead
... we should first polish the task force wiki and then just
transfer what we have in the new website
Daniel: I am working on it
Kaz: since the Wiki is still the first point of contact for the
newcomers it should be kept updated
... in parallel the marketing web site can be synchronized
Daniel: I agree, so my proposal is to take the text from the PR
and copy it to the Wikipage
... please review the text so that we can go ahead
Zoltan: we should keep in sync also github documents (e.g.,
readme)
Daniel: so the todos are: add link to wiki page from github
repo; add text to wiki what task force is doing; add wiki link
to github wiki
Kaz: I don't think we really need the github wiki
Daniel: on option is to remove the wiki
... but I can't do it in this repo
plus one from my side
Daniel: about PR marketing text, we had different template
propsal. Template modification can be discussed during the
marketing call
Kaz: we should also clarify what should be copied from the w3c
wiki pages
Daniel: yeah I think this is discussion to be shared with the
other task forces
... meanwhile please review the PR so that we can go ahead
... I think these new activity pages are better than before
because they contain more information about what we really do
Kaz: I am ok, if the whole wiki information is included
somewhere and nothing is lost
Daniel: can someone review the text?
Cristiano: I'll do it this afternoon
Daniel: it's a first step towards a better website
Scripting issues
scribenick: cris_
<kaz> [15]Issue 224
[15] https://github.com/w3c/wot-scripting-api/issues/224
Cristiano: I am proposing to put version under WoT namespace
Zoltan: I think it is not best practising to have version
variable avaible during runtime
... we should encourage programming by version and we should
keep a stability in the API
Cristiano: I agree, the problem is that we don't have really a
use case for having this variable avaible
Daniel: I agree, we have to find the use case
<kaz> [16]vF2F minutes
[16] https://www.w3.org/2020/10/05-22-wot-minutes.html#day5-resolution01
<kaz> [17]TD issue 932
[17] https://github.com/w3c/wot-thing-description/issues/932
<kaz> [18]JSON-LD 1.1 Processing Mode
[18] https://www.w3.org/TR/2020/REC-json-ld11-20200716/#dfn-processing-mode
Kaz: we discussed jsonl-ld version practice, they suggested we
talk with DID and VC guys
[we should continue the versioning discussion with the TD guys
too]
Architecture terminology
Daniel: moved to the next call
Upcoming calls
Daniel: Christmas break and then first call on the 11th of
January 2021
<kaz> [19]https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf
[19] https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf
Kaz: please update the cancellations section on the main web
conf page
<kaz>
[20]https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Cancellatio
ns
[20] https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Cancellations
Daniel: sure
[adjourned]
Summary of Action Items
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [21]scribe.perl version ([22]CVS log)
$Date: 2021/01/19 09:34:01 $
[21] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[22] http://dev.w3.org/cvsweb/2002/scribe/
Received on Tuesday, 19 January 2021 09:34:25 UTC