1.3.6 Protocols - default should be a "C callable API" not, for example, HTTP

decentralized-identity / confidential-storage

Confidential Storage Specification and Implementation

https://identity.foundation/confidential-storage/

Apache License 2.0

80 stars 23 forks source link

1.3.6 Protocols - default should be a "C callable API" not, for example, HTTP #167

Open mwherman2000 opened 3 years ago

mwherman2000 commented 3 years ago

The base/default "protocol" should be something like a "C callable API" for working against a Layer A Secure Content Storage store. Call it the Layer A Secure Content Storage API.

The other categories of protocols (e.g. HTTP) can be implemented as Layer D Services on top of Layer A Secure Content Storage API.

Reference: https://identity.foundation/confidential-storage/#protocols

mwherman2000 commented 3 years ago

One way to think about this is: If

Alice makes available an EDV software implementation that supports HTTP as its primary protocol (and doesn't publish a C-callable API), and
Bob makes available an EDV software implementation that supports HTTP to be compatible with the current specification and also publishes a C-callable API, which implementation, in general, are developers likely to prefer?

mwherman2000 commented 3 years ago

Of course, a well-designed/conceived "C-callable API" can be used can be used to automatically generate a variety of protocols/service endpoints (e.g. HTTP REST).

mwherman2000 commented 3 years ago

Visually, what I refer to as the Layer A "C callable API" is the "EDV Microkernel" API in the diagram below (https://github.com/decentralized-identity/confidential-storage/issues/167):