Add support for DID Auth and encryption/capabilities based on the pub key refs in a DID Doc.
Multi-instance masterless operation, with active/active replication between instances.
The ability to differentially replicate subsets of the logical whole dataset across different instances.
Three modes for data: public plaintext data, shared encrypted data, private encrypted data.
Multi-writer ingest, with the ability for the owner of the datastore to authorize any entity to write that they choose.
Ability to limit writes/reads by external entities. An example of this would be Alice, the datastore owner, being able to limit writes and reads of objects she specifies to Bob and others, in keeping with access and permissioning criteria she sets.
Ability to keep private objects out of public circulation.
Support for both Last-Write-Wins complete replacement of objects and objects that can be seamlessly merged via conflict-free replicate data mechanisms.
Implementations that can run in Web platform, native/mobile app, and remote server environments.
EDV accounts are substitutable across multi-tenant cloud hosts and native, occasionally connected mobile device hosts.
EDV accounts do not presume or benefit from access to a HSM or IntelSGX infrastructure.
The ability for authorized parties to listen for new changes (via feed, pub/sub, etc.) on public objects and encrypted objects (individually or sets) they are authorized to have.
An API that provides inferential queries on semantic data can be directly addressed and fetched via type or a set of well-known metadata values (e.g. an HTTP GET that “Gives me all of Alice’s public https://schema.org/SocialMediaPosting objects”).