- Maybe shorten
DIDDocStore
/DIDDocStorage
names to simplyDocStore
/DocStorage
. - Prototype a did:webplus resolver (via
ssi
crate) and incorporate that into this demo. - Consider making the
id
fields of the elements ofverificationMethod
also contain the appropriate query params (versionId
,selfHash
, and potentially evenvalidFrom
), so that the DID represents the exact value of thekid
field that should go in the header for signatures using JWS and JWT, and it doesn't need to be separately tracked by the wallet. - In verified cache operations which store a "current as of" timestamp, need to figure out robust rules regarding comparing timestamps from different systems. Make it clear that the "current as of" timestamp is a local timestamp, and that other timestamps are remote. Perhaps make it clear that local and remote timestamps aren't necessarily directly comparable in the naive way. Maybe the VDR should timestamp its responses so that the DID resolver can reason about local vs remote timestamps. Yes, it should timestamp its responses, so that the DID document metadata can be correctly formed.
- Add a "valid_until" timestamp to DID doc store rows and records, so that it's easy to determine validity duration and perform SQL queries on validity duration.