Page tree
Skip to end of metadata
Go to start of metadata

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:

AcronymFull Name of DeliverableDeliverable TypeLink to
Draft Deliverable
Lead AuthorsStatus/Notes
ACDCAuthentic Chained Data ContainerSpecification

Pre-Draft Deliverable (PDF)

Slides from the original white paper
AIDAttributable IdentifiersSpecification
Samuel Smith
SAIDSelf-Addressing IdentifiersSpecification
Phil Feairheller
DID KERIKERI DID MethodSpecification
Phil Feairheller
SISSchema ImmutabilitySpecification
Robert Mitwicki
CESRComposable Event Streaming RepresentationSpecification
Samuel Smith
CESR ProofCESR Proof FormatSpecification

IXPIssuance Exchange ProtocolSpecification

PXPPresentation Exchange ProtocolSpecification

PTELPublic Transaction Event LogSpecification

JSON SerializationJSON Serialization RequirementsSpecification


JSON SchemaJSON Schema RequirementsSpecification



Chairs

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

Members

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

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:

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.

TaskDescriptionLinkAuthors
GLEIF use case
https://hackmd.io/dlnfd8xOSqmD90v4Y6mzFQSam and Drummond
Supply Chain use caseSupply 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 verificationBoarding a plane for international travelhttps://hackmd.io/QYlbK-mmTSGKHkpyP_-VSg
Pure data provenanceCiting sourceshttps://hackmd.io/QiOf8YjnT261g8MMAh2yJA




  • No labels

1 Comment

  1. Don't see a link for the github or mailing list.  Have these things been set up?