This is an approved Task Force of the ToIP Technology Stack Working Group. Please comment/suggest improvements and add your name if you wish to participate in this TF. This Charter was presented at the TSWG meeting on 2022-07-11 (see these meeting notes) and approved at the TSWG meeting on 2022-08-08 (see these meeting notes).

Mission

The TSWG web3 Concept Development Task Force (wCD TF) is chartered to explore where ToIP concepts can be applied to specific use cases across a broad ecosystem of technologies associated with the concepts of web3. Members of the Task Force commit to exploring ways that the ToIP concepts can be applied broadly to solve problems with the goal of informing the TSWG about future specifications and standards that can be aimed at specific problems in decentralization. While code may be created (hosted outside of ToIP) that is vendor/technology specific, the standards and specification recommendations coming from the task force must be broad and open. 

Initial areas of examination may include:

  • DID-based Authentication - what is the recommended pattern no matter whether it is "native web3" or uses OIDC, FIDO2, or some other mechanism compatible with the ToIP stack
  • VC-based Authorization - what is the recommended pattern independent of any underlying IAM system
  • verifiable "things" (e.g. verifiable NFTs) - how developers can create a simple protocol/pattern for verifying digital assets like NFTs and how these fit into the ToIP 4-Layer model.
  • DIDs and DID Fragment usage - where/how do DID Documents and the generic DID protocol help create useful patterns (e.g. resource storage, validation) that go beyond current thinking.
  • DIDs and Trust Registries - what are the patterns of interaction.
  • Compliance Suites - what patterns of compliance/accreditation would help drive adoption for ToIP 4-layer models. HL-Aries Interop test suite may be a starting point.

The mission of this task force is to explore each use case. That exploration may involve creation of working code that helps to identify the patterns that exist and determine what standards and specification may be needed to create broad industry adoption. The outputs may result in new new task forces created elsewhere in ToIP or other places.

Phases

  • The first phase is exploratory: to conduct survey studies to come to a common understanding of how the technologies of AI/Metaverse and Trust intersect & impact ToIP's current mission. The output can be one or more discussions or white papers.
  • The second phase is to synthesize an actionable recommendations and/or white papers as ToIP deliverables.

Deliverables

The deliverable of this Task Force are:

  • Regular reports to TSWG on each use case that is being actively explored.
  • One or more ToIP Recommendations or White Papers.

Leads

Please add your name to this list if you wish to be a lead:

Membership and Joining

Prior to participating in the meetings please ensure that you are a member of the Trust Over IP Foundation. Contributor level membership is available to anyone at no cost. Details can be found at this link.

To join this TF, add your name to this list: (Note from Darrell O'Donnell: I've pre-populated some of your names who expressed an interest previously. Please confirm by adding your affiliation or add/remove/edit as needed)

Meeting Schedule

The first launch meeting is scheduled.

  • First meeting: TBD

  • Zoom: TBD

We will discuss in the first meeting, among other topics:

  • A good time for regular zoom meetings and other ways to stay connected
  • An asynchronous method where we can most efficiently get things done.

Milestones

Key milestones will include, but are not limited to:

  1. Phase 1: Survey and White Paper
  2. Phase 2: Recommendation and/or White Paper

Intellectual Property Rights (Copyright, Patent, Source Code)

As a Task Force (TF) of the Technology Stack WG (TSWG), the web3 Concept Development TF (W3CDTF) inherits the IPR terms from the TSWG JDF Charter. These include:

Mailing List and Slack

This task force uses the following for communications

  • Mailing List: This TF will most likely not need its own mailing list.
  • Slack: This TF will have its own dedicated Slack channel #<TODO>