Main WoT WebConf/2022 Next Charter

Special Meetings to Discuss Next Charter

Calendar: https://www.w3.org/events/meetings/504ef715-9e3b-44a7-b8a5-34eab01da99a/20230116T080000
Dates: Jan 16-18
- Monday Jan 16: 8am-9am Eastern; logistics Link for Members, Link for IEs
- Tuesday Jan 17: 8am-9am Eastern; logistics Link for Members, Link for IEs
- Wednesday Jan 18: 8am-10am Eastern; logistics Link for Members, Link for IEs
- Thursday Jan 19: 8am-10am Eastern (tentative); logistics Link for Members, Link for IEs
Proposals should go here: https://github.com/w3c/wot/tree/main/proposals/deliverable-proposals
Charter template/starting point: https://github.com/w3c/wot/blob/main/charters/wot-wg-2022-draft.html
To do: check latest template at https://github.com/w3c/charter-drafts/blob/gh-pages/charter-template.html
Liaisons: https://github.com/w3c/wot/issues/978#issuecomment-1359830278

Preparation

Deliverable proposals have all been merged
Please make PRs against WG 2023 Draft Charter going forward for proposed deliverables
Draft completed, please review before April 5 and review minutes (linked in the README at https://github.com/w3c/wot-charter-drafts)

Session 1

Day 1 - Jan 16

Length: 1h

Chair: McCool

Scribe: Ege

Organization (15m)
- W3C Process Guide (2023 Draft)
- README - WoT Charter Process
Starting Point:
- Template (5m)
Use Cases and Requirements (30m)
- Process (15m)
  - (link to Process presentation)
  - Adoption policy - discussion issue
- Coverage (15m)
  - https://github.com/w3c/wot-usecases/blob/main/USE-CASES/coverage.csv
  - https://github.com/w3c/wot-usecases/blob/main/USE-CASES/coverage-gaps.md

Day 2 - Jan 17

Length: 1h

Chair: McCool

Scribe: Kaz

Organization (25m)
- Schedule for remainder of current charter
- Charter Extension - how long is really needed? (10m)
- Registries - what are they, do we want to use them? (25m)
Deliverables (5m)
- Short review of PRs

Carried forward:

Security
- Onboarding process
- Consolidation of security assertions
- Key distribution e.g. via DID
Discovery
- Geolocation (TD/data vocab + query filters)
- Normative query language (e.g. JSON Path)
- Registry for Introductions?
Architecture update
TD update
Profile update
Scripting

Day 3 - Jan 18

Length: 2h

Chair: Sebastian

Scribe: Michael McCool (first hour), Michael Koster (second hour)

Organization (10m)
Generic (5m)
- Simple fixes: https://github.com/w3c/wot/pull/1058
Policy and Workflow (40m)
- Extension (10m)
  - Extend current charter 4mo or 6mo?
  - Either way, we would plan to start new charter June 1 (or earlier), and proceed with planned high-priority items e.g. OPC UA liaison and TD 2.0.
  - Even if do 6mo extension, should stick to the proposed schedule, which is based on 4mo
- License (5m)
  - Propose using W3C Software and Document License, as in our current charter
  - PR: https://github.com/w3c/wot/pull/1062
- Clarify policies (15m)
  - prioritize WoT's actual industry applications working with existing IoT standards like OPC UA and ECHONET Lite Web API
    - Issue (Use cases - Adoption Policy): https://github.com/w3c/wot-usecases/issues/206
  - clarify the relationship between the WoT-WG and related groups/organizations, e.g., WoT IG, WoT CG, WoT-JP CG, DID WG, JSON-LD WG, OPC, ECHONET, ITU-T, Matter, ... (see below for other liaison discussions)
- Example deliverable template for liaisons:
  - What: Binding Templates, Vocabulary and Ontology, Conformance tests
  - How: A separate joint WG?, WoT WG as a joint WG?, a TF within the WoT WG?, just part of the TD/Binding discussion?
  - Who: Editors from W3C, OPC and/or ECHONET?
  - Resources: Technical Requirements for OPC UA liaison
  - PR: https://github.com/w3c/wot/pull/1059
- Decision Policy (10m)
  - See https://w3c.github.io/charter-drafts/charter-template.html#decisions
  - PR: https://github.com/w3c/wot/pull/1061
  - Related to Async process proposal
Deliverables - continued (50m)
- Security
  - Work items: https://github.com/w3c/wot/pull/1053
  - Deliverables: https://github.com/w3c/wot/pull/1057
  - Onboarding process
  - Consolidation of security assertions
  - Key distribution e.g. via DID
- Discovery
  - Work items: https://github.com/w3c/wot/pull/1052
  - Deliverables: https://github.com/w3c/wot/pull/1060
  - Geolocation (TD/data vocab + query filters)
  - Normative query language (e.g. JSON Path)
  - Filters (also used for geolocation)
  - Registry for Introductions?
- Architecture update
- TD update
- Profile update
  - PR: https://github.com/w3c/wot/pull/1056
- Scripting
- Bindings Templates update
  - Registry?

Day 4 - Jan 19

Length: 1h

Chair: McCool

Scribe: Kaz/?

Organization (10m)
- Agenda
Review Current Draft
Issues and PRs
Next Steps
AOB

Session 2

Day 2 - Feb 14

Length: 2h

Chair: McCool

Scribe: Kaz

Organization (5m)
Review of first draft
Capture of issues that need to be addressed in first draft:
- https://github.com/w3c/wot-charter-drafts/issues/20
Assignment of Owners

Day 2 - Feb 15

Length: 2h

Chair: McCool

Scribe: Sebastian/Daniel

Organization (5m)
- note: we need to add an issue to the strategy funnel repo for this rechartering procedure - Kaz will work on that.
Review Issues and PRs
- Things to Fix
Discuss remaining issues and assign Owners
Review and close old PRs and issues, e.g. in wot

Day 3 - Feb 16

Length: 2h

Chair: McCool

Scribe: Cristiano/Ege

Organization (5m)
Review Issues, PRs, and Status
- Things to Fix
- Remaining issues in WoT repo
Discuss remaining issues and assign Owners
- Additional work items for Digital Twins
- Document Organization
Next Step
- When are we done?
  - Any other W3C groups or external groups to mention?
  - Remaining work - how to review and finalize?
  - Schedule
- Strategy funnel issue

Session 3

Day 1 - Feb 21

Length: 1h

Chair: McCool

Scribe: Lagally

Organization (5m)
Review old wot Issues
- https://github.com/w3c/wot/labels/WG%20New%20Charter%20Plans%202023
- All closed, please review and open new issues in wot-charter-drafts
Review Issues, PRs, and Status
Document Organization
Next Steps
- Are we done?
- Strategy funnel issue

Day 2 - Feb 23

Length: 1h

Chair: McCool

Scribe: Luca

Organization (5m)
Review Issues, PRs, and Status
Document Organization
Next Steps
- Are we done?
- Strategy funnel issue

Session 4

Day 1 - Feb 27

Length: 1h

Chair: McCool

Scribe: Andrea

Organization (5m)
Review Issues, PRs, and Status
- Details - https://github.com/w3c/wot-charter-drafts/pull/64
- Mission Statement - https://github.com/w3c/wot-charter-drafts/pull/42
- Bindings - https://github.com/w3c/wot-charter-drafts/pull/40
- Profile
- Scope - merge items from https://github.com/w3c/wot-charter-drafts/pull/55
- CG Collab - https://github.com/w3c/wot-charter-drafts/pull/41
- Other
Next Steps
- Are we done?
- if so, create strategy funnel issue, resolution text

Day 2 - Feb 28

Length: 1h

Chair: McCool

Scribe: Kaz

Organization (5+5m)
Review Issues, PRs, and Status (45m)
Next Steps (5m)
- Are we done?
- if so, create strategy funnel issue, resolution text
- if not...

Day 3 - Mar 1

Length: 1h

Chair: McCool

Scribe: Cristiano

Organization (5+5m)
- Daylight Savings announcement
Review Issues, PRs, and Status (45m)
- Mission Statement
- Scope
- Architecture Status

Day 4 - Mar 2

Length: 1h

Chair: McCool

Scribe: Kaz

Organization (5+5m)
Review Issues, PRs, and Status (45m)
- Charter Items
- Liaisons (invite PLH)
- TD/TM
- Other issues
Next Steps (5m)
- Update extension schedule
- Are we done?
- if so, create strategy funnel issue, resolution text
- if not...

Session 5

Day 1 - Mar 8

Length: 45m

Chair: McCool

Scribe:

Organization (5m)
Review Issues, PRs, and Status (35m)
- Charter Items
Next Steps (5m)
- Update extension schedule
- Are we done?
- if so, create strategy funnel issue, resolution text
- if not... mtg Mar 9 during Arch slot?

Day 2 - Mar 9

Length: 1h (-5m)

Chair: McCool

Scribe:

Organization (5m)
Process
- What needs to be decided?
  - Making Architecture normative or informative
    - What are some smaller, more manageable questions that we can answer first?
  - If Architecture is not normative, what do we do instead?
    - Moving assertions to other deliverables is just one option
  - Where can existing *categories* of normative content be moved, in theory?
    - ... but probably not details of individual assertions
    - better to defer detailed discussion/refinement of individual assertions to new charter
- How can we make this decision?
  - Process, analysis, proposals, resolution, consensus or ... (gasp) vote?
- What is the deadline?
Related Issues
- Should Scripting API be normative?
  - Some assertions in Architecture, e.g. about the runtime, are there because the Scripting API is not normative.
- Should there be a normative Security and Privacy document?
  - Some assertions about secure transport (for example) do not really belong in existing deliverables.
  - Proposed new topics like onboarding also don't really fit into existing deliverables.
- What constitutes "evidence of implementability"?
  - In some cases, we have assertions at risk even though the assertion is clearly implementable, i.e. support for secure updates or use of DTLS 1.3.
Next Steps (5m)
- Update extension schedule
- Are we done?
- if so, create strategy funnel issue, resolution text
- if not... when do we meet again? See: Process, above

Session 6

Day 1 - Mar 13

Length: 1h (-5m)

Chair: McCool

Scribe: Luca

Organization (5m)
Review PRs and Issues
- https://github.com/w3c/wot-charter-drafts/labels/WG%20New%20Charter%20Plans%202023
Architecture
- https://github.com/w3c/wot-charter-drafts/issues/16
Related:
- Should Scripting API be normative?
  - https://github.com/w3c/wot-charter-drafts/issues/84
- Should there be a normative Security and Privacy document?
- Should Profiles be managed as a registry (in the TD spec)?
https://github.com/w3c/wot-charter-drafts/issues/80
Next Steps (5m)

Day 2 - Mar 15

Length: 30m (part of main call)

Chair: McCool

Scribe: Sebastian/Kaz

Resources
- Draft Charter
- Strategy pipe issue 375 - WIP: Web of Things Working Group rechartering
Organization (5m)
- need a resolution to send for AC review
  - When can we make a resolution to send the draft WG Charter to the W3M/Wide review/AC review?
Identifying what to be resolved before the AC Review
- Mission, Motivation, Scope
  - WoT deployment for actual IoT industries based on stronger liaisons with related SDOs
- Normative delivarables
  - abstract description of each expected deliverable (including why it's necessary)
    - Architecture? - https://github.com/w3c/wot-charter-drafts/issues/16
    - Scripting API? - https://github.com/w3c/wot-charter-drafts/issues/84
    - Security and Privacy document?
    - Should Profiles be managed as a registry (in the TD spec)? - https://github.com/w3c/wot-charter-drafts/issues/80
  - relationship among deliverables
- Coordination
  - policy on how to deal with contributions and liaisons, etc.
  - Relationship among WoT Groups
  - Relationship with related groups and SDOs
How to deal with the details?
- We should update the details document, if we link it from the charter; don't necessarily have to finish policy docs if not linked.
Remaining PRs and Issues - https://github.com/w3c/wot-charter-drafts/labels/WG%20New%20Charter%20Plans%202023
Next Steps (5m)

Day 3 - Mar 16

Length: 1h - 5m Chair: McCool

Scribe: Kaz

Session 7

Day 1 - Mar 22

Length: 30m (part of main call)

Chair: McCool

Scribe: Sebastian/Kaz

Organization (5m)
- Draft Charter
- need a resolution to send for AC review
  - When can we make a resolution to send the draft WG Charter to the W3M/Wide review/AC review?
Identifying what to be resolved before the AC Review
- Mission, Motivation, Scope
  - WoT deployment for actual IoT industries based on stronger liaisons with related SDOs
- Normative delivarables - abstract description of each expected deliverable (including why it's necessary)
  - Architecture
  - Discovery
  - Thing Description (including Binding)
  - Profile
- Informative Deliverables
  - Use Cases and Requirements
  - Security and Privacy GUidelines
  - Test suite / Implementationr reports
  - Best Practices
  - Scripting API
  - Binding sub-documents
- relationship among deliverables should be clarified (separately from the Charter discussion itself)
- Timeline
  - What to be done by when?
- Coordination
  - policy on how to deal with contributions and liaisons, etc.
  - Relationship (1) among WoT Groups and (2) between WoT and other SDOs should be clarified (separately from the Charter discussion itself)
How to deal with the details?
- We should update the details document, if we link it from the charter; don't necessarily have to finish policy docs if not linked.
Remaining PRs and Issues - https://github.com/w3c/wot-charter-drafts/labels/WG%20New%20Charter%20Plans%202023
Contributions - which PRs and Issues are related to which topics above?
- PRs
- Issues
Next Steps - timeline for the rechartering procedure

Day 2 - Mar 23

Length: 30m (part of main call)

Chair: McCool

Scribe: Sebastian/Kaz

Organization (5m)
- Draft Charter
- need a resolution to send for AC review
  - When can we make a resolution to send the draft WG Charter to the W3M/Wide review/AC review?
Identifying what to be resolved before the AC Review
- Mission, Motivation, Scope
  - WoT deployment for actual IoT industries based on stronger liaisons with related SDOs
- Normative delivarables - abstract description of each expected deliverable (including why it's necessary)
  - Architecture
  - Discovery
  - Thing Description (including Binding)
  - Profile
- Informative Deliverables
  - Use Cases and Requirements
  - Security and Privacy GUidelines
  - Test suite / Implementationr reports
  - Best Practices
  - Scripting API
  - Binding sub-documents
- relationship among deliverables should be clarified (separately from the Charter discussion itself)
- Timeline
  - What to be done by when?
- Coordination
  - policy on how to deal with contributions and liaisons, etc.
  - Relationship (1) among WoT Groups and (2) between WoT and other SDOs should be clarified (separately from the Charter discussion itself)
How to deal with the details?
- We should update the details document, if we link it from the charter; don't necessarily have to finish policy docs if not linked.
Remaining PRs and Issues - https://github.com/w3c/wot-charter-drafts/labels/WG%20New%20Charter%20Plans%202023
Contributions - which PRs and Issues are related to which topics above?
- PRs
- Issues
Next Steps - timeline for the rechartering procedure

Session 8

Day 1 - Mar 27

Length: 2h (replacing Scripting and Security)

Chair: McCool

Scribe: Luca

Organization (5m)
- Draft Charter
Review PRs
- https://github.com/w3c/wot-charter-drafts/pulls?q=is%3Aopen+label%3A%22WG+New+Charter+Plans+2023%22+type%3Apr
Review Issues
- https://github.com/w3c/wot-charter-drafts/issues?q=is%3Aopen+label%3A%22WG+New+Charter+Plans+2023%22+type%3Aissue
Resolution to send for AC review
- Actual resolution will be in main call
- This will just confirm that the draft is complete

Day 2 - Mar 29

Length: 30m (part of main call)

Chair: McCool

Scribe:

Organization (5m)
- Draft Charter
Review PRs
- https://github.com/w3c/wot-charter-drafts/pulls?q=is%3Aopen+label%3A%22WG+New+Charter+Plans+2023%22+type%3Apr
Review Issues
- https://github.com/w3c/wot-charter-drafts/issues?q=is%3Aopen+label%3A%22WG+New+Charter+Plans+2023%22+type%3Aissue
Final Review
- Mission Statement
- Background and Motivation
- Scope
- Deliverables
- Timeline
- Decision Process
Resolution to send for review
- CALL FOR RESOLUTION to send charter draft for W3M/wide review in main call on April 5
- Resolution to send for AC review will happen after the W3M/wide review is complete, probably on May 17 - technically can be finalized by June 14 (4 weeks minimum review time).
- Allows group time to react to review comments before July 1. However, if this involves resolutions we will have to allow 1 week for final review.
- Note that technically our current charter goes to the end of July, so if necessary (e.g. if there is a major objection we have to deal with) we can use this time for further charter revisions.