Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The GSWG meets bi-weekly on Thursdays at 11:00-12:00 PT / 18:00-19:00 UTC. Check the ToIP Calendar for meeting dates.

Zoom Meeting Link and Recording

...

Link: https://zoom.us/j/98299579894?pwd=c3UyQm1wR1RaaWV6S0NsMjJ1OFRtQT09

Recording: https://zoom.us/rec/share/amFcTud8YaHZQU2orCGHZGfPFR7WAKj6WDRELxfND6_yw5nXYolY8xQ-tPlJVA0.Z0DvCV2WPeWaDPiF TBD

Attendees

Main Goal of this Meeting

...

TimeAgenda ItemLeadNotes
5 min
  • Start recording
  • Welcome & antitrust notice
  • Introduction of new members
  • Agenda review
Chairs
  • Antitrust Policy Notice: Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role.New Members: none
  • Sherwood Moore: Been involved in climate accounting.
5 minReview of action items from previous meetingChairs

ACTION: Drummond Reed to line up Technology Architecture Task Force members to attend the following GSWG special topic meeting on Oct 20th for a discussion of: a) how the ToIP Technology Architecture Specification requirements affect the GSWG and our Governance Architecture specs, and b) what architectural components would be a good fit for the initial focus of our Governance Architecture Task Force.

5 minsAnnouncementsAll

News or events of interest to Governance Stack WG members:

5 minutes

Technology Architecture Task Force (TATF)

Drummond explained how the progress of the TATF on the ToIP Technology Architecture Specification (TAS) V1 is likely to affect the GSWG. This link is to the Google doc version of Working Draft 03 — it is being superseded by the GitHub version.

  • First, he pointed out that it brought clarity to the progression of four workstreams that will eventually produce the full ToIP stack. See screenshot #1 below, which appears in section 4 of the TAS.
  • He explained the structure of the TAS and how all normative requirements were consolidated in Appendix A.
  • He agreed with Scott that a GSWG review of these requirements would be a logical next step in two directions:
    1. To review what changes may be necessary to our Governance Architecture specifications.
    2. To suggest the set of components to be the focus of the Governance Architecture TF work.

Rebooting the Web of Trust

Identity Week - Washington DC

FIDO Alliance - Seattle

ISO working Group ISO 27560


5 minsGovernance Architecture Task Force

A summary of ongoing task force meetings


Working through a use case Museum Group pass and the governance that would be needed.

20 minutesIEEE Whitepaper on Blockchain Governance

Savita and Fredericde Vaulx will present the current IEEE Standard on Blockchain governance

Focus is on decentralized governance in four parts (People, Process, Practice, Policy and Incentives)

The model focuses on governance targets (Technology, Ecosystem, Lifecycle)

There are variety of governance subtargets where policies and rules should be applied.

First step in Governance is to build a governance design plan.

Standard going through IEEE QA process.

15 mins15 minsReorg of the Inputs and Semantics Working Group

Steven explained the reorganization of the Inputs and Semantics WG into the Data Modeling and Representation WG.

Scott explained that he invited the leads of the two ISWG task forces to present at this meeting but they did not have enough notice to be able to attend today. They included:
Notice and Consent Task Force

The Notice and

Risk Task Force (Jan Lindquist)

Consent Task Force has moved under the GSWG.  Sal and Mark will discuss the task force, their work and future objectives.

Wiki data can be found under Inputs and Semantic folder

Receipts have a long history that are a key component within governance.

Been working to create a controller credential to govern verifiable credentials.

Need governance to manage control of your private data.  Identifying who controls your data is key.

Transparency cannot happen before processing; after processing users do not have a choice on the transparency over the use of data.

The payload for consent receipt is now finalizing the initial standard issuance process.

ISO/IEC 27560 Consent Record Sharing was approved as a Ballot for a technical specification.

5 mins
  • Review decisions/action items
  • Planning for next meeting 
Chairs


...