Purpose

The purpose of the Authentic Chained Data Container (ACDC) Task Force  is to draft a family of ToIP Specifications that defines the standard requirements for the semantics of Authentic Provenance Chaining of Authentic Data Containers. This semantics include both source provenance and authorization provenance or delegation.  The hypothesis is that the W3C Verifiable Credential standard may be expanded to serve as an Authentic Data Container (ADC) and that the semantics of a VC may be expanded to support an authentic provenance chains (APC) as a super semantic. This may be further expanded to support both a source provenance sub-semantic and a delegated authorization sub-semantic.

Deliverables

The table below lists all deliverables of the ACDC Task Force:

Chairs

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

• Samuel Smith, ProSapien  Samuel Smith

Members

Please add your name to this list in any desired role:

• Primary Editors
  • Samuel Smith
  • Daniel Hardman
  • Robert Mitwicki

• Secondary Editors

  • Carsten Stöcker
• Primary Reviewers

  • Drummond Reed

  • rieks joosten

• Secondary Reviewers

  • 
    

• Observers
  
  • Christoph Fabianek

Meeting Schedule

This TF schedules meetings as needed. Each meeting will be announced on the T mailing list and the TSWG  Slack channel. Currently, we are meeting every other week on Mondays, at 9 am US Mountain time, 1700 Central European Time, at https://zoom.us/j/91368003957?pwd=dFI4RGNqMDFkVjliNzFMQXQwN1cxUT09

See latest documentation in the GitHub Repo here:  https://github.com/trustoverip/TSS0033-technology-stack-acdc

Meeting Agendas and Notes

All meeting agendas and notes are recorded on the ACDC Meeting Page.

Intellectual Property Rights (Copyright, Patent, Source Code)

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

• Copyright mode: Creative Commons Attribution 4.0. 
• Patent mode: W3C Mode (based on the W3C Patent Policy).
• Source code: Apache 2.0, available at http://www.apache.org/licenses/LICENSE-2.0.html. The GSWG TA TF is not expected to produce source code.

Mailing List and Communications

This task force uses the following for communications

• Mailing List: This TF is preparing to set up its own mailing list. Watch this page for details.
• Slack: This TF has its own dedicated Slack channel: #tswg-acdc-tf
• Github: This TF will use GitHub issues for substantive conversations on topics, not Slack. This way the conversation is source controlled.

Specification Generation

This task force uses the following for communications

• Markdown: Draft portions spec written in Markdown
• SpecUP: Final version of spec processed with SpecUp

Use Cases

This table lists the starting set of use cases motivating the ACDC work.