W3C home > Mailing lists > Public > public-credentials@w3.org > March 2021

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

From: Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net>
Date: Wed, 24 Mar 2021 16:05:14 +0000
To: "Michael Herman (Trusted Digital Web)" <mwherman@parallelspace.net>, Adam Stallard <adam.stallard@gmail.com>, "Daniel Buchner (Personal) (danieljb2@gmail.com)" <danieljb2@gmail.com>, "Manu Sporny (msporny@digitalbazaar.com)" <msporny@digitalbazaar.com>, "Dmitri Zagidulin (dzagidulin@gmail.com)" <dzagidulin@gmail.com>
CC: "sds-wg@lists.identity.foundation" <sds-wg@lists.identity.foundation>, "sds-wg@dif.groups.io" <sds-wg@dif.groups.io>, Credentials Community Group <public-credentials@w3.org>, Daniel Buchner <daniel.buchner@microsoft.com>, "Chris Were (chris@verida.io)" <chris@verida.io>, "Orie Steele (orie@transmute.industries)" <orie@transmute.industries>
Message-ID: <MWHPR1301MB20941CD94E6A57BBDE396CE5C3639@MWHPR1301MB2094.namprd13.prod.outlook.com>
PROPOSAL: Confidential Storage Specification Refactoring 0.1 – 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).



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:image005.jpg@01D72095.2C4A4600]



Best regards,
Michael Herman
Far Left Self-Sovereignist

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

[cid:image006.jpg@01D72095.2C4A4600]



image005.jpg
(image/jpeg attachment: image005.jpg)

image006.jpg
(image/jpeg attachment: image006.jpg)

Received on Wednesday, 24 March 2021 16:05:31 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 24 March 2021 16:05:32 UTC