WoT Scripting API -- 14 Dec 2020

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 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 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> Issue 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> vF2F minutes

<kaz> TD issue 932

<kaz> JSON-LD 1.1 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]