PROPOSAL: Confidential Storage Specification Refactoring 0.2 – March 24, 2021 - updated from version 0.1

PROPOSAL: Confidential Storage Specification Refactoring 0.2 – March 24, 2021



Based on the March 11 Zoom discussion where we worked hard to discern the differences between Agents, Hubs, and EDVs (and I believe were largely successful IMO), I’ve like to propose to the SDS/CS WG that we refactor the current Confidential Storage specification into 3 separable parts/specifications.  I also present a high-level roadmap (simple ordering) for how the WG might proceed if this refactoring is accepted (or at least, if the first part/first new specification is accepted).



Version 0.2 adds some comments about inter-specification and specification version dependencies.



Separable Part 1: Factor the current EDV-related components of the current Confidential Specification into its own specification document. This document would be a ZCAP/HTTP-specific specification document for EDVs. I also propose that the title of this specification document clearly reflect that orientation.  For example, the proposed title for this specification document is: EDV Specification 1.0: ZCAP/HTTP Data Vault Storage.



Separable Part 2: Factor the Hub-related components of the current Confidential Specification into its own specification document. This document would define the Hub components that an Agent or App can talk to as well as describe how a Hub “sits on top of an EDV service instance”. I also propose that the title of this specification document clearly reflect that orientation.  For example, the proposed title for this specification document is: Data Hub Specification 1.0: Federated (or Aggregated) Personal Data Access (or something like that).



Separable Part 3: Develop a specification for the Layer A Trusted Content Storage Kernel as its own specification document (see the diagram below). This document would document a public lower-level interface for directly interacting with local-device hosted/attached EDVs without needing or requiring a higher-level remote access protocol (e.g. HTTP). I also propose that the title of this specification document clearly reflect that orientation.  For example, the proposed title for this specification document is: EDV Kernel Specification 1.0: Layer A Trusted Content Storage Kernel. This is in support of apps like the Fully Decentralized Dewitter scenario.



Roadmap: The scope of the above specifications and a high-level roadmap (simple ordering) for these specifications is illustrated below.



[cid:image001.jpg@01D720C7.D517B380]



Dependencies



  1.  EDV Specification 1.0: ZCAP/HTTP Data Vault Storage. The intent is for this specification to be fast-tracked based on the 3 existing prototype/PoC implementations. This specification would neither have nor take any dependencies on either of the 2 specifications below.  In particular, this specification would neither have nor take any dependencies on the EDV Kernel Specification.  A future version or variation of the EDV Specification may take a dependency against whatever is the current version of the EDV Kernel Specification - if the WG chooses to.

  2.  Data Hub Specification 1.0: Federated (or Aggregated) Personal Data Access. This specification would likely take a dependency against whatever is the current version of the EDV Specification (likely EDV Specification 1.0) - if the WG chooses to.

  3.  EDV Kernel Specification 1.0: Layer A Trusted Content Storage Kernel. This specification would not have nor take any hard dependencies against either of the above specifications. The EDV Kernel Specification would be guided by the needs/requirements of the prevailing EDV Specification 1.0: ZCAP/HTTP Data Vault Storage implementations in addition to the Fully Decentralized Twitter (Dewitter) user scenario. Ideally, Layer A of one of the prevailing implementations may act as the reference implementation for the EDV Kernel Specification (assuming its source code and documentation are freely licensed and open-sourced).


Best regards,
Michael Herman
Far Left Self-Sovereignist

Self-Sovereign Blockchain Architect
Trusted Digital Web
Hyperonomy Digital Identity Lab
Parallelspace Corporation

[cid:image004.jpg@01D720C8.AE7B4060]



_._,_._,_
________________________________
Links:

You receive all messages sent to this group.

View/Reply Online (#122)<https://lists.identity.foundation/g/sds-wg/message/122> | Reply To Group<mailto:sds-wg@lists.identity.foundation?subject=Re:%20%3D%3FUTF-8%3FB%3FW3Nkcy13Z10gUFJPUE9TQUw6IENvbmZpZGVudGlhbCBTdG9yYWdlIFNwZWNpZmljYXRpb24gUmVmYWN0b3JpbmcgMC4xIOKAkyBNYXJjaCAyNCwgMjAyMQ%3D%3D%3F%3D> | Reply To Sender<mailto:mwherman@parallelspace.net?subject=Private:%20Re:%20%3D%3FUTF-8%3FB%3FW3Nkcy13Z10gUFJPUE9TQUw6IENvbmZpZGVudGlhbCBTdG9yYWdlIFNwZWNpZmljYXRpb24gUmVmYWN0b3JpbmcgMC4xIOKAkyBNYXJjaCAyNCwgMjAyMQ%3D%3D%3F%3D> | Mute This Topic<https://lists.identity.foundation/mt/81580527/1997675> | New Topic<https://lists.identity.foundation/g/sds-wg/post>
Your Subscription<https://lists.identity.foundation/g/sds-wg/editsub/1997675> | Contact Group Owner<mailto:sds-wg+owner@lists.identity.foundation> | Unsubscribe<https://lists.identity.foundation/g/sds-wg/leave/9912086/1997675/2030013897/xyzzy> [mwherman@parallelspace.net]
_._,_._,_