From 32430060d6a29a4bb0fead24f79d45f66e6c33a8 Mon Sep 17 00:00:00 2001
From: Manu Sporny Level of Assurance
href="#privacy-considerations"> is applicable for such extensions.
+This specification does not require or suggest the use of any specific type of +verifiable data registry. Different use cases might result in different +requirements. Different requirements might suggest different resource usage +trade-offs. For example, trade-offs between computation (energy usage), trust +(deference to authority), coordination (network bandwidth), or memory (physical +storage) might be appropriate for a certain threat model. Other threat models +might not make the same trade-offs. Those that need to consider resource usage +trade-offs for their threat models are directed to the DID Method Rubric, which provides +evaluation criteria to help decision makers evaluate whether or not a particular +verifiable data registry is appropriate for their use cases. +
+
From 253768cfb1ffae44bc7c4268575676348606f544 Mon Sep 17 00:00:00 2001
From: Manu Sporny Level of Assurance
This specification does not require or suggest the use of any specific type of verifiable data registry. Different use cases might result in different -requirements. Different requirements might suggest different resource usage +requirements. Different requirements might suggest different considerations with different trade-offs. For example, trade-offs between computation (energy usage), trust (deference to authority), coordination (network bandwidth), or memory (physical -storage) might be appropriate for a certain threat model. Other threat models -might not make the same trade-offs. Those that need to consider resource usage -trade-offs for their threat models are directed to the DID Method Rubric, which provides evaluation criteria to help decision makers evaluate whether or not a particular -verifiable data registry is appropriate for their use cases. +DID Method is appropriate for their use cases.