Purpose
The purpose of the Authentic Chained Data Container (ACDC) Task Force is to help draft and incubate a family of IETF-focused specifications that define 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 the supporting syntax of an ACDC.
Deliverables
The table below lists all deliverables of the ACDC Task Force:
Acronym | Full Name of Deliverable | Deliverable Type | Link to Draft Deliverable | Lead Authors | Status/Notes |
---|---|---|---|---|---|
KERI | Key Event Receipt Infrastructure | Specification | https://trustoverip.github.io/tswg-keri-specification/ | Sam Smith | Active Draft |
ACDC | Authentic Chained Data Container | Specification | Active Draft | ||
CESR | Composable Event Streaming Representation | Specification | https://trustoverip.github.io/tswg-cesr-specification/ | Sam Smith | Active Draft |
SAID | Self-Addressing Identifiers | Specification | Merged to CESR | ||
CESR Proof | CESR Proof Signatures | Specification | Pending merge | Active Draft | |
PTEL | Public Transaction Event Log | Specification | Merged ACDC | ||
IPEX | Issuance and Presentation Exchange protocol | Specification | Merged ACDC | ||
OOBI | Out-Of-Band-Introduction protocol | Specification | Merged to KERI | ||
VC-ACDC | Securing Verifiable Credentials using Authentic Chained Data Containers. | Specification | Unofficial draft | Active Draft |
Proposed Chairs
Please add your name to this list if you wish to be a chair:
- Kevin Griffin Kevin Griffin
- ...
- ...
Meeting Schedule
Asynchronous
Meeting Agendas and Notes
TBD
Intellectual Property Rights (Copyright, Patent, Source Code)
As a Task Force (TF) of the Technology Stack WG (TSWG), the STTF inherits the IPR terms from the TSWG JDF Charter.
- Copyright mode: OWFa 1.0 (available at https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owfa-1-0)
- Patent mode: 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 http://www.apache.org/licenses/LICENSE-2.0.html)
Mailing List and Communications
This task force uses the following for communications
- Slack: This TF has its own dedicated Slack channel: #tswg-sttf
- 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.
Task | Description | Link | Authors |
---|---|---|---|
GLEIF use case | https://hackmd.io/dlnfd8xOSqmD90v4Y6mzFQ | ||
Supply Chain use case | Supply chain refers to the 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 |