Note: this is a DRAFT Charter for a proposed This is an approved Task Force under 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 to 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 - login - whether web3 native or OIDC-based, what is the recommended pattern.Perhaps more broadly: DID- and VC-based Authentication and Authorization, whether web3 native or OIDC-based, what is the recommended pattern
• further - analog to FIDO2 ("passwordless login"), username+password, etc.
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.

...

• Darrell O'Donnell 
• Drummond Reed 
• Daniel Bachenheimer , Accenture
• Rodolfo Miranda 
• Sumabala Nair 
• Matteo Midena , Monokee
  
• Brian Richter , Aviary Tech

Meeting Schedule

The first launch meeting is scheduled.

...

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:

• Copyright mode:  Creative Commons Attribution 4.0.  OWFa 1.0 (available at https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owfa-1-0)
• Patent mode: W3C Mode (based on the W3C Patent Policy).OWFa 1.0 (available at https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owfa-1-0)
• Source code: Apache 2.0 , (available at at http://www.apache.org/licenses/LICENSE-2.0.html. The W3CDTF TF is not expected to itself produce source code.)

Mailing List and Slack

This task force uses the following for communications

...