Note: this is a DRAFT Charter for the proposed Task ForceThis is an approved Task Force of the ToIP Technology Stack Working Group. Please comment/suggest improvements and add your names... This is a proposed ask Force under the Technology Stack Working Groupname if you wish to participate in this TF. This Charter will be was presented to the TSWG on 11JUL2022. @anwas 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  TSWG web3 Concept Development Task Force (wCD TF) has been created 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 .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 helps to identify the patterns that exist and determine what standards and specification may be needed to create broad industry adoption. The outputs may quickly create result in new new task forces created elsewhere in ToIP or other places.Phasing:

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 Discussion/White Papersdiscussions or white papers.
• The second phase is to synthesize an actionable Recommendation recommendations and/or White Papers for ToIP to consider acting uponwhite 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.
• A Recommendation One or more ToIP Recommendations or White PaperPapers.

Leads

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

...

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)

• Wenjing Chu , Futurewei
• Vikas Malhotra, WOPLLI Technologies
• Phil Wolff
• John Phillips
• Burak Serdar
• sankarshan Darrell O'Donnell 
• Drummond Reed 
• Zaïda Rivai, Danube Tech Gmbh
• Gwen Pfetsch, Microsoft
• Shannon Wells
• Daniel Bachenheimer , Accenture
• Rodolfo Miranda Nuttawut Kongsuwan, Finema
• Sumabala Nair
• Pratyaksh Gupta
• Vladimir Simjanoski, Blokverse 
• Mattia Zago – Monokee
• Callum Haslam, BC Gov
• Jacques Bikoundou 
• Darrell O'Donnell 
• Drummond Reed 
• Eric Drury 
• Vinod Panicker , Wipro
•  
• Matteo Midena , Monokee
  
• Brian Richter , Aviary Tech@JudithFleenor, TrustOver IP Foundation

Meeting Schedule

The first launch meeting is scheduled.

• First meeting: July 7, 2020 (Thursday), 9 AM, Pacific TimeTBD

• Zoom: https://zoom.us/j/97604264531?pwd=NXB3S2d6bldidVVjVFlYVmpwallBZz09TBD

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.

...

We have created a new channel #tswg-aim-tf. Please join us there:  https://trustoverip.slack.com/archives/C03G3S7BH8U

Milestones

Key milestones will include, but are not limited to:

...

Intellectual Property Rights (Copyright, Patent, Source Code)

As a Task a Task Force (TF) of the Governance the Technology Stack WG (GSWGTSWG), the GATF web3 Concept Development TF (W3CDTF) inherits the IPR terms from the GSWG 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 GSWG TA TF is not expected to produce source code.)

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 has will have its own dedicated Slack channel #tswg-aim-tf: https://trustoverip.slack.com/archives/C03G3S7BH8U#<TODO>