Meeting minutes
Agenda
mm: we should talk on the resolutions of the chair changes
Minutes Review
<kaz> Oct-20
sk: any objections to publishing the minutes?
Minute Review of F2F
<kaz> Oct-27
<kaz> (Architecture part will be reviewed during the Architecture call tomorrow on Nov-4; Scripting part will be reviewed on next Monday)
<kaz> Oct-28
sk: when and where should some of these be reviewed
mm: I think only liaison minutes should be reviewed now
<kaz> (OPC-UA, etc., will be reviewed during the Use Cases call next Tuesday)
Moderator Change
<sebastia_> proposal: the group approves that Ege will be new moderator for the Marketing TF
Resolution: the group approves that Ege will be new moderator for the Marketing TF
<sebastia_> proposal: the group approves that Fady will be new moderator for the Testing TF
Resolution: the group approves that Fady will be new moderator for the Testing TF
Editor's Call Updates
sk: now being held on Tuesday
kaz: the main purpose is checking the consistency of all the WoT specs, and also see potential missing descriptions.
Events
sk: IoT Interoperability Workshop has deadline next week
<mlagally_> https://
<mlagally_> please review the MR for the precedence rule on terminology
mm: I am collaboration with Michael Lagally
ml: it is not a liaison paper
sk: any updates from WoT Japanese CG?
tm: we are discussing the activities of the task forces to brief the participants
… and also their policies
Schedule for deliverables
<kaz> Draft WG 2021 Extension Plan #1000
sk: here we have the plan. PR 1000 in the w3c/wot repository
sk: we have to sort of publish FPWD by January 13 in order to meet the deadlines
sk: freezing profile by Jan 31
sk: and testfest by mid february
ml: really good to have a concrete plans. There are some open questions
ml: what is the plan with the architecture spec
ml: architecture should also have a feature freeze by Jan 31
sk: since there is no need to test, we can have it later than december
ml: end of january would be ok
ek: we can do it much later, no need to do any tests
ml: how about the note documents from the task forces
sk: we can have them in end of april>
kaz: we do not have to put the notes in this schedule plan
kaz: don't we want to test the architecture specification this time?
ml: we want to have an implementation report
mm: mostly manual assertions and implementation descriptions
kaz: isn't there dependencies between profile and architecture?
ml: yes. Also between td and architecture
kaz: do you want to add further features to your specifications
sk: if we have restrictions or dependencies between architecture and other specifications, it is not good
ek: sadly, there is such dependencies between TD and Architecture. And mistakes that do not align with the TD
ml: we should not call these mistakes
<kaz> (we're getting out of time but Kaz suggests we continue this discussion)
ml: maybe some misalignments that need to be formulated
kaz; we have a time problem. If michael mccool and ege does not have any concrete topics, we can continue discussion now in this call
ege: I have some points but they can be short
mm: we should decide what should be in the 1.1 specifications
kaz: this should be step 0
sk: (adds step 0 to the extension plan)
kaz: do you plan to have new features/changes in the architecture specification
ml: the text is mostly informative
kaz: Informative changes are also possible
ml: the spec is stable since months
ml: the step 0 should be about the normative changes
kaz: we also have the Wide Reviews
sk: TAG review also happens right?
<kaz> (Wide Review includes TAG, Accessibility, Privacy, Security and Internationalization)
mm: I put the 2 months padding because of this
<kaz> Wide Review Guideline
ege: I would like to see implementations first before going with a feature freeze
ml: ben francis has said that he has implementations and that these are easy to implement
ege: I still think that we need some implementation experience
mm: we don't have to have automatic testing
ege: my concern is not about automatic testing but implementability of the specification
<kaz> kaz: we should discuss new features including Ben's proposals during the step 0 in the updated wg-2021-extension-plan.md
ml: about point 1. What do we rollback?
… is there a tag/label?
https://
<sebastia_> proposal: group approves about the WG Charter extension plans as described in the PR https://
ege: we need to define what it means to be backwards compatible
Resolution: group approves the WG Charter extension plans as described in the PR https://
IG Charter updates
<kaz> IG Charter updates based on W3M review #986
<sebastia_> I need to go
<kaz> mm: need some more clarification
<kaz> kaz: ok. will get back to the W3M based on the current status.
<kaz> [main call adjourned]