EDV data vault migration/upgradability: What is needed in the v1 specification? [Placeholder]

[mwherman2000]

What is needed in the EDV data vault v1 specification to ease the upgrade and migration from one version of technology to a new version of the technology?

• data vault level versioning?
• data vault specific schema versioning?
• ...

[tplooker]

Discussed on the 24th of June WG call, suggestion is that we need versioning on the EDV configuration document which forms the basis for EDV versioning

[msporny]

We should have a version number on the EDV configuration. That version number tells implementers all of the expected data structures and protocols that the EDV supports. We absolutely should not have per-document versioning.

[TallTed]

[@msporny said] We absolutely should not have per-document versioning.

Could you delve a bit into your reasoning for this? I think I disagree, but perhaps I'm misunderstanding what documents your statement is about.

[msporny]

[@msporny said] We absolutely should not have per-document versioning.

Could you delve a bit into your reasoning for this? I think I disagree, but perhaps I'm misunderstanding what documents your statement is about.

I was speaking specifically about the Structured Documents:

https://identity.foundation/edv-spec/#structureddocument

and Encrypted Documents:

https://identity.foundation/edv-spec/#encrypteddocument

So the proposal would be to put a version in here:

https://identity.foundation/edv-spec/#datavaultconfiguration

... and that version applies to all Structured Documents and Encrypted Documents in the encrypted data vault.