Proposal for a new CCG Work Item - Wallet Attached Storage (WAS)

Hi all,

Over the past year or so, the Digital Credentials Consortium (DCC) team at
MIT Open Learning, along with colleagues from the RIPL/Arkansas Launch
project (led by Judson Neer), as well as several others (big shoutout to
Benjamin Goering for all his hard work on the spec and implementations),
has been working on a storage protocol and data model useful for verifiable
credential wallets and other adjacent systems.
And I think the CCG might find it useful, since it builds on several
CCG-incubated specifications (DIDs, zCaps, secure storage of Verifiable
Credentials, and is meant to work with Encrypted Data Vaults to provide
optional end-to-end encryption).

The current working name for the spec is WAS (Wallet Attached Storage);
some other names that have been bandied about included Web Spaces API, or
Agentic Storage API.

It's basically an HTTP REST API that's meant to be a general purpose front
end for any kind of permissioned storage. It uses a familiar three tiered
data model -- Spaces (equivalent to a disk drive partition, a cloud storage
workspace, or a relational database), Collections (equivalent to a file
system directory, folder, object storage Bucket, or database table), and
Resources (any data item you'd want to read and write, from structured JSON
documents to images or binary blobs).
Reads, writes, and collections listings are modeled with HTTP CRUD verbs.
And zCaps are used for DID-based authorization (not authentication :) ).

It's particularly useful to serve as a general purpose standardized back
end for Verifiable Credential wallets, but can also be used for any sort of
permissioned AI agent storage, or as a component to user-centric "Bring
Your Own Storage" type of apps.

Some links:
* DCC Blog post:
https://blog.dcconsortium.org/what-is-wallet-attached-storage-439917ba4fa5
* Poster at ePIC2025 in Paris:
https://drive.google.com/file/d/16rd2WpYHvjwHhCiXyl26XtO2dSsXyGON/view
* WAS Specification:
https://digitalcredentials.github.io/wallet-attached-storage-spec/

The DCC team would be very interested in collaborating on this spec and
donating it to the CCG. Several members of the community (including Phil
Long and several others) have expressed preliminary interest in
collaborating.

As always, though, for a spec to be adopted as a CCG work item, we need at
least one more party to formally express interest / support for this work.
Hence the question to the group -- is this something that would be of
interest to the community?

(Happy to answer any questions of course.)

Dmitri