Meeting minutes
Invited Experts
Philip Blum has been approved Michael Koster's application is still pending
Approval of minutes
<kaz> Feb-3
Michael reviews the minutes of last week's call
Any objections to publishing the minutes [no]
Approved.
WoT Japanese CG
Kaz talks about the new Japanese WoT Japanese CG. they're planning to hold an online event later February. Mizushima-san could give some more details.
Mizushima-san gives more details
McCool asks if we can update our new Web pages to link to the new CG
<dape> CG area within the new WoT Welcom page
Daniel provides some details
McCool: we should link to the WoT JP CG from our marketing pages
<Mizushima> wot-jp cg homepage
Renaming the "master" branches to "main"
McCool: we were asked to rename our Master path on GitHub to Main. I've tested this in my own fork.
People need to update their local copies on their own computers.
McCool: I have a few more things to do and will then draft some detailed instructions. Any PR's against the Master path need to be applied before we do the updates
Michael shows us some of the details
Lagally: what's the purpose, what will happen to the original?
McCool: I think but haven't tested that pending PR's will be automatically rolled over
Github has been a little unstable recently ...
So taking things cautiously
Goals and Objectives
Our CEO, Jeff Jaffe is asking for the objectives we are setting ourselves for this year. This can include our publication roadmap, any workshops we plan to do, measurable progress with our liaisons, and best of all metrics for adoption by industry and targets for member recruitment.
Any idea of how we can answer Jeff?
Some of this is around marketing, and industry outreach
We want to set some achievable objectives according to what we want
McCool: what do we do in respect to contacting industry prospects
Sebastian: we're starting a joint activity with OPC and this should be one of the objectives as an important step for a WoT binding to OPC
McCool: how should we organise this? I could create a markdown file in GitHub?
kaz: please note that the W3C Objective is related to the Industry Team, and the Industry Champions including Dave for WoT and myself for Smart Cities are in charge of generating the Objectives documents.
what I as the WoT Team Contact would like to ask the group to think about is rather clarifying the existing targets and expectations. for example, what I suggested during the marketing call and the use cases call yesterday. extending the timetable for spec generation might be a good starting point.
McCool: we need a clear place for where we keep those objectives
He creates an issue to kick this off
… along with a markdown file "goals.md"
The issue is #956 "Capture objectives and goals"
<McCool> https://
Lagally: what is the lowest entry level for compliance with WoT
I believe that we need to have the entry barrier very low
We also need to encourage convergence by the Mozilla web things
McCool: a tutorial would list what components you need to build a WoT compliant solution
McCool: we need to raise our visibility and encourage adoption
We're working on our marketing plan with a March 1st milestone
Ege talks about microcontrollers
McCool: for a product the cheapest device, along with a hub device ...
Lagally: we should talk about this in the architecture call
Sebastian: the Mozilla web thing community meet regularly, and have plans for W3C WoT compliance for 2.0 version
kaz: is Ben Francis still leading the Web Things community?
McCool: I think so
<kaz> kaz: in that case, we can chat with Ben directly too :)
Plans for joint calls
Michael reviews the pending plans for joint calls with external groups, WebThings (Mozilla), Microsoft DTDL, IEC CDD, ...
plugfest and Virtual F2F planning
David: I wanted to ask about thingweb.io, which talks about Raspberry Pi a lot
McCool: we want to provide instructions for running node-wot
… it would be my preference for a reference platform
<Zakim> dezell, you wanted to ask about thingweb.io
<Ege> https://
Michael Koster talks about some development hardware options
NodeMCU is based on ESP8266 chip plus WiFi
We should talk about a tutorial for a minimally conformant systems
<Ege> https://
Further discussion in the plugfest call ...
Sebastian has implemented support in the Lua stack
Michael wonders if node-wot can be made to run on small devices
Sebastian: TUM have some baseline implementations
<Zakim> kaz, you wanted to suggest we talk about the detail on implementations during the plugfest call again :)
<Ege> https://
F2F planning
McCool: We've arranged webex for the face to face, but need to prepare the agenda
<mjk> We should eventually have a common reference stack for embedded platforms (C/C++)
Kaz: one hour for a joint discussion with IEC
McCool: let's try to arrange the calls with other external groups on the same day
Each task force needs to add their own agenda topics
McCool asks Michael Koster about joint call on oneDM and ASDF, should this be done in the IETF?
Koster: I don't think there will be time during the IETF meeting
<McCool> https://
Sebastian is proposing a cooperation document and sub group for WoT/OPC
McCool: I think this is essentially about protocol binding, but these are not part of our charter in respect to normative specs
Kaz: informative would be fine for now given the Charter says Protocol Binding is informative. also we can have further discussion during the TD call later today.
<kaz> Charter
McCool: I have a draft proposal for gelocation and am working with Christne Perey on this
TF reports
Sebastian provides a quick status report from Marketing TF, good progress on web pages
<dape> see https://
Launch date for new pages is March 1st
<dape> wot-marketing issue 118
Please review by end of Feb
McCool: we should think about a clean experience for developers new to WoT
<Zakim> aks, you wanted to discuss general marketing feedback w.r.t. "is everyone" ok with the current approach
Lagally: when will we do a resolution on the new pages?
McCool: not today, but definitely to mark that we're comfortable with the launch
Feel free to propose PR's if you have some ideas for improvements
… end of meeting
<kaz> [main call adjourned; PF call starts in 5 mins]