Open DRK3 opened 3 years ago
Discussed on July 8, 2021 WG call:
Do we need the ID in a structured document?
Discussed on Sep 2, 2021.
There are two issues here:
1) Does the EDV spec want to be able to reserve keys, in structured documents? 2) Clarifying the algorithm for generating encrypted indexes.
The algorithm for generating encrypted indexes can be found here: https://github.com/decentralized-identity/edv-spec/issues/56#issuecomment-700108603
It should be checked against the edv-client implementation for any updates.
Why not just encode your data as an JWE and directly put it in an
EncryptedDocument
instead of wrapping it in aStructuredDocument
first, seeing as how the server never sees theStructuredDocument
. AStructuredDocument
are already a very general object.Now... assuming that Structured Documents are here to stay... I find the ID constraint strange. In the description for the
StructuredDocument
id
property, it says:Seeing as a
StructuredDocument
is encrypted before being put in anEncryptedDocument
what is the need for the format constraint on theid
property? Why does aStructuredDocument
have an ID anyway?