Things to Fix

[mmccool]

• Revise Mission statement
  • support industry adoption
  • integration with other ecosystems (e.g. other standards, communities)
  • Revise mission statement #23
  • Mission Statement Revise #42
  • Owner: Ege/Sebastian
• Remove "details" section
  • Remove Work Item Details #17
  • Clean up after separating details #22
  • Separate details #21
  • Clean up and consolidate work items #31 - removes hyperlinks to deleted "details" sections
  • Details cleanup #51 - cleanup separate details doc
  • Owner: McCool
• Consolidate work items
  • Discovery (5) -> one Discovery Improvements
  • All Protocol Bindings, Payload Bindings into one workitems; "Work on new protocol bindings as appropriate"
  • Consolidate and Refine Work Items and Describe Higher-Level Goals #24
  • Clean up and consolidate work items #31 - merges Discovery, Protocol Bindings, Payload Bindings
  • Owner: McCool Ege
• (OPTIONAL) Group work items into higher-level categories
  • E.g. Digital Twins, Discovery, Metadata, Protocol Binding
  • ... pending consolidation
• Add additional work items
  • Digital Twins:
    • Higher-Level Structures
    • Behavioral Descriptions
    • Edge Computing
    • recategorize existing work items, e.g. timeseries, geolocation
    • Owner: Lagally/Sebastian
    • Orga: Add Missing Work Items for Digital Twins #25
• Relate work items to appropriate deliverables AND external groups
  • ... pending reorganization
  • Revise Liaisons #37
  • update external orga list #43
  • Owner: Ege/Sebastian
• Add Normative Specifications
  • TD 2.0
    • TD and TM restructuring #33
    • Owner: Ege
  • TM 2.0
    • TD and TM restructuring #33
    • Owner: Sebastian
  • Architecture 2.0 (need to discuss further)
    • Owner: Lagally
  • Profiles
    • Owner: Lagally
  • Individual Protocol Bindings
    • Or do these as Notes?
    • Just defer discussion of structure
    • Organize Deliverables for Protocol Bindings #26
    • Simplify the binding mechanism #40
    • Owner: Ege
• Version numbers
  • Do we even want them? What do we do instead?
• Reorganize Informative Deliverables
  • Call out Notes in a separate category
  • Additional Notes for Protocol Bindings, "as discussed in Liaisons section"
    • Owner: Ege
    • Organize Deliverables for Protocol Bindings #26
• Timeline
  • ... defer pending reorg.
• W3C Groups
  • WoT JP CG
  • SDW WG
  • WN IG
  • consider as candidates all groups in prev charter
  • Add W3C Groups #27
  • Add W3C group coordination list #32
  • Add SDWWG to list of W3C Groups #44 - adds SDWWG
  • Do we keep Privacy and Accessibility Groups? #45
  • Expand CG collaboration #36 - expand WoT CG desc
  • Owner: McCool
• Decision Policy
  • should at least document what we are currently doing
  • Update Decision Policy #28
  • Owner: McCool
• Suppress charter history (for now; fresh start)
  • Suppress Charter History #29
  • Suppress Charter History #30
  • Owner: McCool

[mmccool]

Also:

• Charter Organizational Issues wot#1051
• Brainstorming: Topics for the next charter from Architecture TF discussion wot#1069
• Architecture Restructuring wot#1070
• Update WG 2023 Discovery items wot#1066

[mmccool]

Propose closing, we can just use issues directly, and this is out of date now.