You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 37 Next »

Purpose

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

  1. ACDC TSS—a specification of Authentic Chained Data Containers. The original Pre-Draft Deliverable is here (PDF). A set of slides with diagrams from the white paper may be found here  Slides. This will be superseded by a wiki page draft. 

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


Milestones

Key milestones will include, but are not limited to:

Task List

This table tracks active tasks assigned to the TF members.

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

Robert Mitwicki

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

Daniel Hardman

Data graph with verificationBoarding a plane for international travelhttps://hackmd.io/QYlbK-mmTSGKHkpyP_-VSgDaniel Hardman
Pure data provenanceCiting sourceshttps://hackmd.io/QiOf8YjnT261g8MMAh2yJADaniel Hardman

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



Agenda Minutes


2021-05-17

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

Summary


Abstract

The abstract offers the reader a brief overview of white paper’s main points. It allows the reader to ensure they have found a document relevant to their needs. After reading, the reader should be able to know if they are in the right place.
DELETE THIS COMMENT

Audience

Who are the intended readers of this document?
DELETE THIS COMMENT

Motivation

Why are we doing this? What use cases does it support? What is the expected outcome?
DELETE THIS COMMENT

Scope

Briefly describe the scope of this document – how it presents the architecture of this particular enabler.  Include an explanation of how this architecture relates to Organization Name activity.  If it adds clarity, also describe what is not in the scope of this architecture.  DELETE THIS COMMENT

Problem Statement

The problem statement specifies the issue the white paper will address. The problem needs to be defined and placed into a context to ensure it’s understood by the reader.
DELETE THIS COMMENT

Background

This section provides the background information required for the audience to grasp the problem and, ultimately, the solution. The content may be detailed and technical or broad and high-level. The content depends on the reader and the problem.
DELETE THIS COMMENT

Support Research

If original research is completed for the white paper, the methods should be communicated.
DELETE THIS COMMENT

Solution

The ‘ta-da’ moment of the white paper.

Based on the preceding information, the solution is now presented. It is developed and argued for using the gathered evidence and the expertise of the author and their company.
DELETE THIS COMMENT

Conclusion

This section summarizes the white paper’s major findings. Recommendations based on the solution are provided.
DELETE THIS COMMENT

References

2021-05-10

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

2021-03-26

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

2021-03-01

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

2021-03-01

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

2021-02-15

Followup on getting repo setup in MkDocs

Use Cases Selected:

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.

2021-02-01

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

UETA  https://www.uniformlaws.org/committees/community-home?CommunityKey=2c04b76c-2b7d-4399-977e-d5876ba7e034

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

2021-01-18

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


2021-01-04

Use Case Summaries

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


Attribution Chaining Semantic Super Semantic

     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


  • No labels