DID Metadata management

[noandrea]

Decision (2022-03-28): The current implementation of the Metadata is not ideal since it uses a separated key from the DID document:

• unnecessary complicates migrations
• duplicates reads and writes
• at the moment there is no practical use case
• created, updated and versionId can be derived (by the resolver)

Future work: There is a possibility that the metadata will play an important role later on, but the implementation will have the following characteristics:

• metadata will be part of a wrapper around the did document that will contains both the document and the metadata
• the resolver will automatically resolve updated and created f
• the resolver will automatically resolve versionID if it is not set

[minkyraccoon]

Note: this should be turned into an ADR

[github-actions[bot]]

This issue was marked as stale because there was no activity for 15 days