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.
Please add your name to this list if you wish to be a chair:
Please add your name to this list in any desired role:
Secondary Editors
Secondary Reviewers
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
Key milestones will include, but are not limited to:
This table tracks active tasks assigned to the TF members.
Task | Description | Link | Authors |
---|---|---|---|
GLEIF use case | https://hackmd.io/dlnfd8xOSqmD90v4Y6mzFQ | Sam and Drummond | |
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 | Daniel Hardman |
Pure data provenance | Citing sources | https://hackmd.io/QiOf8YjnT261g8MMAh2yJA | Daniel Hardman |
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:
This task force uses the following for communications
This task force uses the following for communications
Issues with security privacy suggested pull request (Daniel Hardman)
Terminology (Daniel Hardman)
How to formally manage terminology in Specs: (Other group) create terms wiki
Order of creation of SAIDs (Daniel Hardman)
Degree of Saidification (Sam Smith)
Continue discussion on Schema and SAIDs
IGrant Data Agreement with ACDC (Robert Mitwicki)
GLEIF ACDC vs VC models
LPG model
Continue discussion on Schema and SAIDs
LPG model
Alighnment with VC data model
Multiple Endorsers
Continue discussion on Schema and SAIDs
Phil talk about JSON Schema and SAID
Change meeting time ?
Proof signature
Alighnment with VC data model
Multiple Endorsers
discussed and refined example in index.md of draft spec. Decided that certain blocks in VC MUST use SAI (self addressing identifiers) so that can reason about the data using the identifier.
This allows compactness and secure universal verifiability. Either the block is explicitly included or instead of the block a SAI
The schema is nested with SAI blocks for the corresponding blocks in the VC
schema of data payload
schema of rules
Write spec outline
Abstract Model
Two concrete implementations. One VC Linked-Data with schema.org with security caveats, the Other JSON and immutable JSON-Schema
https://w3c-ccg.github.io/vc-json-schemas/
Abstract
Introduction
Terminology
Specification
Overview
Security
Guarantees
Storage
Versioning
Definition
Versioning Guidelines
Revision
Model
Extensibility
Examples
Verifiable Credentials
Drawbacks
Alternatives
Security & Privacy Considerations
Interoperability
Security
Semantics
Index
Terms defined by this specification
References
Informative References
Motivation
Scope
Problem Statement
Solution
References
Semantic inference and reasoning under uncertainty
https://github.com/SmithSamuelM/Papers/blob/master/whitepapers/VC_Enhancement_Strategy.md
Work Item for next week write spec outline
OCA (Overlays Capture Architecture) Robert Mitwicki (input and semantic WG at ToIP) standard
Deck: https://docs.google.com/presentation/d/17DS11jHQm3jGAUXCNwP5qFUBJrw7tcKiSGMgH2k0giA/edit?usp=sharing
OCA Article: https://humancolossus.foundation/blog/cjzegoi58xgpfzwxyrqlroy48dihwz
OCA editor: https://editor.oca.argo.colossi.network/
OCA spec draft: https://github.com/the-human-colossus-foundation/oca-spec
JSON-LD Security EndState Sam
Proposal Identifiers Sam
MetaDiscussion Daniel
RoadMap
Hypothesis
Continue Discussion
Notes about ADC and its structure: https://hackmd.io/RX8ZAycxQhSpGZgBfRzqbg
Data Item Model
Authentic Data Item = Attestation
Data Controller ID: DID namespace controller
Attestation ID: (in order to reason with data)(IETF RATS Alignment) ID of the Attributable Item Attestion.
Derived DID from DID namespace
Derived from Data Item Content (such as https://iscc.codes)(correlate attestations)
Verifiable Registry of Data Item
Data Attributes:{NonAuthentic Attributes}
Data Controller Signature on Data Item: (nonredudiable, integral)
Data Mesh Meetup
MKDocs GitHub
https://github.com/trustoverip/TSS0033-technology-stack-acdc
https://tools.ietf.org/html/draft-ietf-tls-subcerts-10
Delegation chain separate from identity chain
hiding part of the chain
privacy in both direction walking back up to the root and privacy walking down from the root
Followup on getting repo setup in MkDocs
Supply Chain (Mitwicki)
GLEIF (Smith and Reed)
Delegation (Hardman)
Data Source Provenance (Hardman and Smith)
IoT (Hardjono)
Next task
Create proposals for chaining semantics with syntax. (assume Verifiable Credential Based)
Express each use case in each chaining proposal.
Iterate on proposals.
Open Question:
Syntax should at least support Trees and DAGs (Directed Acyclic Graphs) not merely linear chain
Should syntax also support cyclical graphs.
Finalize choice of MkDocs vs SpecUp: Decided on MKDocs:
Action Item: Sam work with TOIP to setup GitHub repo with MkDocs
EiDas Links: (See 2021-02-01) Robert Mitwicki. Discussion of SSI etc in EiDAS
Relation to Legal Framework for Digital Signatures
https://en.wikipedia.org/wiki/Electronic_signatures_and_law
https://acrobat.adobe.com/content/dam/doc-cloud/en/pdfs/adobe-sign-us-guide-e-signatures-wp-ue.pdf
ESIGN Act https://www.fdic.gov/regulations/compliance/manual/10/X-3.1.pdf
EiDAS
Advanced Electronic Signature Qualified Electronic Signature Notaries with Certificate = Handwrittern Signature
Review Use Cases:
Semantic Containers: Pauls Knowles Semantic Container. Nested Forms. Consent.
Distinguish between different types of containers as part of specification for ACDC
Action Item Robert Mitwicki add information on EIDAS regulation allows for linking.
Discussed CCG Meeting on ZCap vs VC Authorization
Discussed Use Cases
MkDocs vs Spec Up (Tables?)
Action Item Sam review and present at next meeting
GLEIF vLEI https://hackmd.io/dlnfd8xOSqmD90v4Y6mzFQ (Sam Smith ProSapien)
Supply Chain https://hackmd.io/vYztT346RC-m34aVmFB7vg (Robert Mitwiki Human Colossus )
Global ID for life https://hackmd.io/vYztT346RC-m34aVmFB7vg (IdNum - Robert)
Digital Immunization Passport https://hackmd.io/vYztT346RC-m34aVmFB7vg (Robert)
Authorizations for Encrypted Backups use_case.md (Charles Cunningham Eugeniu Rusu Jolocom)
Guardianship Chain of Credentials (Evernym Daniel and Drummond)
Delegating Access to Rented Car (Evernym)
Provenancing Inherited Attributes (Daniel Hardman Evernym ProSapien)
Delegation of Certification Authority PKI Certificate Like Chaining (Ned Smith Intel)
Object Capabilities Like Authorizations (See authorizations for encrypted backups)
Critical Supply Chain Provenancing (Carsten Stoecker Spherity)
Open Accredited Market Participation Energy Market (Jolocom
Provenance Virtuous Supply Chains Conscious Consumers Demand Pull
Data Supply Chain Provenance
Data Supply Chain Consent Provenance Consented Data Privacy (Samuel Smith ProSapien)
Content Distrubution Networks (copyright, acknowledgement, usage, attribution) (Thomas Hardjano MIT)
IoT Onboarding Devices (Ned Smith Intel, Thomas Hardjano MIT)
Attestation Chaining
Anonymized Data Chains - https://hackmd.io/vYztT346RC-m34aVmFB7vg
Representing business processes/entity lifecycles with SSI - Representing Lifecycles of Entities using States + SSI.pdf
Secure Attribution of statement to controller of a decentralized identifier
A securely attributed chaining statement links two securely attributed statements together
A chaining statement is a special case statement whose semantics are to securely linked by attribution.
This chaining may be applied recursively.
The chained statements that are not chaining statements may convey sub-semantics such as authorization, delegation, attestation, provenance, etc.
Attribution Verification Types: Nonrepudiable Signatures. ZKPs. Anonymized Data.
Certificate Result Certification
Certifying the result of a decision
Verifiable Algorithm
CoSWID Tags IETF