If we include a new random ID (name-TBD), at the top level of an EDV document, it could be used during the update process to ensure that it has not changed. If it has changed, then any updates to the EDV document would be denied, even if the sequence number matched.
This could allow EDV servers to stop having to tombstone EDV documents, allowing them to be deleted fully instead. This would be because confusion over whether a sequence number applied or not in the event that an EDV document had been previously deleted would be probabilistically infeasible. A newly created EDV document must always use a new random ID (name-TBD).
In theory, this change could be added to existing EDVs, allowing them to delete old tombstoned docs.
If we include a new random ID (name-TBD), at the top level of an EDV document, it could be used during the update process to ensure that it has not changed. If it has changed, then any updates to the EDV document would be denied, even if the sequence number matched.
This could allow EDV servers to stop having to tombstone EDV documents, allowing them to be deleted fully instead. This would be because confusion over whether a sequence number applied or not in the event that an EDV document had been previously deleted would be probabilistically infeasible. A newly created EDV document must always use a new random ID (name-TBD).
In theory, this change could be added to existing EDVs, allowing them to delete old tombstoned docs.