Purpose

The purpose of the Authentic Chained Data Container (ACDC) Task Force  is is to help draft a TSS (ToIP Standard Specification) that defines and incubate a family of IETF-focused specifications that define the standard requirements for the semantics of Authentic Provenance Chaining of Authentic Chained Data Containers. This The semantics of ACDCs 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 with 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. These are all encapsulated into the semantics with the supporting syntax of an ACDC.

Deliverables

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

1. ACDC TSS—a specification of Authentic Chained Data Containers. The original Pre-Draft Deliverable is here (PDF). This will be superseded by a wiki page draft. 

Chairs

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

• Samuel Smith, ProSapien
• Carsten Stoecker, Spherity
•  Samuel Smith
• Philip Feairheller, GLEIF Phil Feairheller 

2022 - Members

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

• Primary Editors
  • Samuel Smith
  • Phil Feairheller 
  • Kevin Griffin 

• Secondary Editors

  • Daniel Hardman 
  • Robert Mitwicki 
  • Carsten Stöcker
• Primary Reviewers

  • Drummond Reed

  • rieks joosten

• Secondary Reviewers

  • Kevin Dean

  • Scott Whitmire 
• Observers
  
  • Christoph Fabianek
  • Kent Bull 
  • Henk van Cann 
  • Nuttawut Kongsuwan 
  • Trent Larson 

Meeting Schedule

This TF schedules meetings as needed. Each meeting will be announced on the T mailing list and the TSWG  Slack channel.

Milestones

Key milestones will include, but are not limited to:

Task List

This table is the ongoing task list maintained by the TF members.

The ACDC TF currently holds a meeting weekly on Tuesdays:

• NA/EU: 10:00-11:00 EST / 14:00-15:00 UTC 

For all authoritative meeting logistics and Zoom links, please see the ToIP Calendar.

tps://zoom.us/j/92692239100?pwd=UmtSQzd6bXg1RHRQYnk4UUEyZkFVUT09

See the latest documentation in the GitHub Repo here:  https://github.com/trustoverip/tswg-acdc-specification

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 a Task Force (TF) of the Technology the Technology Stack WG (TSWG), the ACDC TF inherits inherits the IPR terms from the 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 )

• The ACDC TF is not expected to produce source code.

Mailing List and Communications

This task force uses the following for communications

• Mailing ListSlack: 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: #gswg-gov-architecture-tfhas 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

Specifications use the IETF draft format but may use the following:

• 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.