...
The purpose of the Authentic Chained Data Container (ACDC) Task Force is is to help draft and incubate a family of ToIP Specifications that defines 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:
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/ | Samuel Smith | Active Draft |
ACDC | Authentic Chained Data Container | Specification |
Active Draft | |||||
CESR | Composable Event Streaming Representation | Specification | https://trustoverip.github.io/tswg-cesr-specification/ | Samuel 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 |
Chairs
Please add your name to this list if you wish to be a chair:
- Samuel Smith, ProSapien Samuel Smith
- Philip Feairheller, GLEIF Phil Feairheller
2022 - Members
Please add your name to this list in any desired role:
- Primary Editors
Secondary Editors
Secondary Editors- Primary Reviewers
Secondary Reviewers
- Observers
Meeting Schedule
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.
tpsThis 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/9136800395792692239100?pwd=dFI4RGNqMDFkVjliNzFMQXQwN1cxUT09UmtSQzd6bXg1RHRQYnk4UUEyZkFVUT09
See the latest documentation in the GitHub Repo here: https://github.com/trustoverip/tswg-acdc-specification
...
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: Apache2 and IETF Copyright 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)Patent mode: Apache2
- 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.
...
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.
Specification Generation
This task force uses the following for communicationsSpecifications 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
...
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 |
...