Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The purpose of the Authentic Chained Data Container (ACDC) Task Force  is to draft a TSS (ToIP Standard Specification) 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:

...

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

...

 (PDF)

...

...

original white paper
AIDAttributable IdentifiersSpecification


SAIDSelf-Addressing IdentifiersSpecification


DID KERIKERI DID MethodSpecification


SISSchema ImmutabilitySpecification


CESRComposable Event Streaming RepresentationSpecification


IXPIssuance Exchange ProtocolSpecification


PXPPresentation Exchange ProtocolSpecification


PTELPublic Transaction Event LogSpecification



Chairs

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

...

Meeting Agendas and Notes


2021-08-

...

30

OCA as a SAID based Schema Immutability specification

More details on ToIP glossary wiki facility

Details of how GLEIF is using ACDC and associated specs. Placeholder spec repositories at https://github.com/WebOfTrust

Specs WoT

KeyStorage keeping.py module Manager and Keeper classes encrypted secrets

  • vLEI Credentials rely on the following specifications.
  1. JSON Required https://datatracker.ietf.org/doc/html/rfc7159
  2. JSON Schema Version 2020-12 https://json-schema.org/draft/2020-12/json-schema-core.html
  3. Composable Event Streaming Representation (CESR) Specification https://github.com/WebOfTrust/cesr
  4. Attributable Identifiers (AIDs,SCIDs) for Issuers and Holders using the did:keri Method (secure attribution) https://github.com/WebOfTrust/aid
  5. KERI Decentralized Identifiers (AIDs) did:keri Specification https://github.com/WebOfTrust/did-keri
  6. Self Addressing Identifiers (SAIDs) https://github.com/WebOfTrust/said
  7. Schema Immutability Specification (SIS) https://github.com/WebOfTrust/sis
  8. Composable Event Streaming Representation (CESR) Proof Format https://github.com/WebOfTrust/cesr-acdc-proof
  9. ToIP Authentic Chained Data Container (ACDC) Specification https://github.com/trustoverip/TSS0033-technology-stack-acdc
    1. (Informative) JSON required as defined in https://www.w3.org/TR/vc-data-model/#json
      1. Exception @context MUST NOT be included.
  10. Issuance Exchange Protocol Specification for ACDC and KERI (Key Event Receipt Infrastructure)
  11. Presentation Exchange Protocol Specification for ACDC and KERI
    1. WACI PEx https://github.com/decentralized-identity/waci-presentation-exchang
  12. Public Transaction Event Log (PTEL) Specification


Core Components of KERI  Robet Mitwicki

Key Provanance Log -> KEL
Self-Certifying Identifier -> SAI, SCI, keri prefix
General purpose registry -> TEL
Secure communication proctocol CESR/DIDComm?
Self Describing cryptograhic material encoding - CESR/Multicodec/CDE/JOSE/COSE
Key Storage


Relationship between ACDC and W3C VC 2.0


2021-08-16

OCA as a SAID based Schema Immutability specification

More details on ToIP glossary wiki facility

HCF working with ESSIF on Rules section of ACDC  https://github.com/decentralised-dataexchange/automated-data-agreements

...