The purpose of the Authentic Chained Data Container (ACDC) Task Force is to help draft and incubate a family of IETF-focused specifications that defines the standard requirements for the semantics of Authentic Chained Data Containers. 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) 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 supporting syntax of an ACDC.
The table below lists all deliverables of the ACDC Task Force:
|Acronym||Full Name of Deliverable||Deliverable Type||Link to |
|ACDC||Authentic Chained Data Container||Specification||Active Draft|
|SAID||Self-Addressing Identifiers||Specification||IETF Spec Repo||Samuel Smith||Active Draft|
|CESR||Composable Event Streaming Representation||Specification||IETF Spec Repo||Samuel Smith||Active Draft|
|CESR Proof||CESR Proof Signatures||Specification||IETF Spec Repo||Active Draft|
|PTEL||Public Transaction Event Log||Specification||IETF Spec Repo|
|IPEX||Issuance and Presentation Exchange protocol||Specification||IETF Spec Repo|
|OOBI||Out-Of-Band-Introduction protocol||Specification||IETF Spec Repo||Active Draft|
|DID KERI||KERI DID Method||Specification||IETF Spec Repo||Phil Feairheller|
|KERI||Key Event Receipt Infrastructure||Specification||IETF Spec Repo||Samuel Smith|
|VC-ACDC||Securing Verifiable Credentials using Authentic Chained Data Containers.||Specification||Unofficial draft||Active Draft|
Please add your name to this list if you wish to be a chair:
- Samuel Smith, ProSapien Samuel Smith
- Philip Feairheller, GLEIF Phil Feairheller
- Kevin Griffin, GLEIF Kevin Griffin
Please add your name to this list in any desired role:
- Primary Editors
- Primary Reviewers
The ACDC TF currently holds a meeting every two weeks 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.
See 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 Force (TF) of the Technology Stack WG (TSWG), the ACDC TF inherits the IPR terms from the TSWG JDF Charter. These include:
- Copyright mode: Apache2 and IETF Copyright
- Patent mode: Apache2
- Source code: Apache 2.0, available at http://www.apache.org/licenses/LICENSE-2.0.html.
- The ACDC TF is not expected to produce source code.
Mailing List and Communications
This task force uses the following for communications
- 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.
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
This table lists the starting set of use cases motivating the ACDC work.
|GLEIF use case||https://hackmd.io/dlnfd8xOSqmD90v4Y6mzFQ|
|Supply Chain use case||Supply chain refers to overall concept behind the flow of any type of goods and services.||https://hackmd.io/vYztT346RC-m34aVmFB7vg|
|Delegation use case (analog to ZCap usage)||A car rental company delegates driving privileges for car X to Alice. Alice delegates to the attendant at valet parking.||https://hackmd.io/jDSauX_4RWmTzn8rPijxng|
|Data graph with verification||Boarding a plane for international travel||https://hackmd.io/QYlbK-mmTSGKHkpyP_-VSg|
|Pure data provenance||Citing sources||https://hackmd.io/QiOf8YjnT261g8MMAh2yJA|
Don't see a link for the github or mailing list. Have these things been set up?