Meeting minutes
Previous minutes
<kaz> Nov-24
Sebastian walks over the minutes from last week
no objections -> minutes approved
Quick updates
Brief report from the panel at IoT Tech Expo Nov 30 at 11:10am CET - Security (McCool)
McCool: 40 minutes events
… 4 panels
… oneM2M was present
… London Transport panel
… should follow-up with them
… topics come up: e.g., management system
… talked about vulnerable systems
… fur the future: network configuration might be of interest
… Note: there is a recording... not sure if it is public
Editors' sync-up call on Tuesday
Sebastian: Not many participants -> short call
… discussions about status of the documents
… new WD for TD is planned
… should also concentrate on profile document
Updates on the possible new Architecture call slot?
Sebastian: Currently: Thursday, 05:00-07:00 EST / 10:00-12:00 UTC
… temporary slot
… need a long-term solution
Lagally: Let's use the slot tomorrow to find a consensus
WoT Japanese CG updates
Mizushima: We are organizing kick-off meeting
Mizushima: Also translated Arch document into Japanese
Sebastian: Thanks, Great!
<kaz> WoT Architecture Japanese translation as a TTC standard
Smart Cities updates
Kaz: no specific news
Rechartering and Charter Extensions
IG Charter Rechartering/Renewal
https://
Sebastian: W3C Management takes the next steps
Kaz: We put several changes
… updated version is under discussion by W3C management
WG Charter Extension
Sebastian: Also under W3C managements review
Draft WG Charter for the next period AFTER the 12mo extension
https://
Sebastian: New ideas MMC?
McCool: correct, see https://
Sebastian: Thanks, please use issue for new ideas/topics
Lagally: In use-cases call we discussed new use-cases
Lagally: it is important to have such use-cases
… everyone is encouraged to provide use-cases
… e.g., need for orchestration or "intelligent" device
… video stream requirements
McCool: should go through all use-cases for new charter
… for new feature we should require use-case
Discuss decision process
https://
Sebastian: we discussed the topic in the last TD call. Agreed on GitHub agreements
… with approval ... for example form issue raiser .. we should be able to merge
… this depends of course on the issue and the relations
… every task-force should decide on its own
Lagally: Question about list of "reviewers"
… in the Arch work I assign relevant people
… we should make sure to have a proper review process
… I agree that editorial changes should be merged as soon as possible
… anyhow, we should draw a line here and take care
Lagally: I am still unsure whether asynchronous process helps to speed up
Sebastian: Speaking for TD task force. Small issues waste a lot of time...
… fixes like editorial stuff
Lagally: Agree with editorial changes
Sebastian: TD is stable by now... no big discussion at the moment
… other task forces are still working on the feature set ... which makes it more complex
Lagally: Ultimately we should have a "common" process for all task forces
Sebastian: "text improvements" is also about improving examples .. make it better understandable
Lagally: In nontrivial cases we still need a "live" discussion
… we could use "editorial" label
Sebastian: How does the discovery task force work?
McCool: We do discuss each issue...
… we could improve going through PRs
… should assign reviewers
Ege: PR template could solve such cases
… label a PR as editorial ...
McCool: If we have a template it should be short and clear
Ege: agree
… having checkbox like "editorial"
McCool: Editors should check the label
… PR should be also done at least 1 day before the call
Lagally: +1
Sebastian: Every task-force should talk about this process
Kaz: If we want to improve the process we should think about several steps
… discussion first et cetera
… complicated topics take time
… hence we should be careful
… e.g,. "small" PRs are better than BIG ones
Sebastian: Agree
Marketing
Sebastian: Wiki pages were redesigned
… need short description what task force is about
McCool: provided prototype in security wiki
… link to website et cetera
<sebastian> https://
McCool: propose this as prototype
Sebastian: Makes sense, other task forces should do the same
Testing needed prior to CR transition
McCool: Fady/Ege are working on tooling
Liaisons
McCool: Should follow up on older minutes .. like action items
… we could have "Liaisons" as ongoing process .. instead of adding it to each Agenda
… or even own wiki page ... which gets reviewed from time to time
Lagally: Use-cases document describes Liaisons
<ML showing sections in use-cases document>
<kaz> Liaison section
OPCUA
Sebastian: Had meeting with Jeff yesterday
… we WoT WG can start on OPCUA binding
… OPC UA can work on a new companion standard
… however, we should clarify what kind of stronger commitment required if we want to think about official joint work
… shall we continue the discussion in use-case call ?
Lagally: Makes sense
WISHI call
Sebastian: took place 2 days ago
… there are minutes
… I presented ThingModel
… SDF to ThingModel was discussed also
ITU-T
McCool: have upcoming event Feb 3
… will try to get more details
ECHONET
Kaz: ECHONET is planning to make blog post
… about PlugFest participation, and would like us to have a summary description on the Plugfest site so that they can refer to that page.
McCool: Let's discuss this in PF call
Kaz: Alright
McCool: We should have results for each PF
Sebastian: Blog post in English?
Kaz: I think Japanese only
TF Reports
Discovery
McCool: we made the decision to remove XPath from normative part
… not ideal, ... since JSON path is not standardized
McCool: If you have a strong opinion on that, please speak up
Architecture
Lagally: discussions about names like "profile" and core requirements
Lagally: Thursday, 05:00-07:00 EST / 10:00-12:00 UTC
<kaz> [main call adjourned; Plugfest call starts in 5mins]