Partial deletion marks a record for deletion but continues to store some or all of the original information. This mode of operation can be useful if -there are requirements to be able to audit all credentials or presentations over -a particular time period or if recovering the original credential might be a -useful feature to provide an entity. +there are audit requirements for all credentials and/or presentations over +a particular time period, or if recovering an original credential might be a +useful feature to provide.
Complete deletion purges all information related to a given verifiable credential or verifiable presentation in a way that is unrecoverable. This mode of operation can be useful when removing information -that is outdated and beyond the needs of an audit or when responding to any +that is outdated and beyond the needs of any audit or when responding to any sort of "right to be forgotten" request.
-When deleting a verifiable credential, what to do with the status -information needs to be considered. Some use cases might call for a deletion +When deleting a verifiable credential, handling of its status +information needs to be considered. Some use cases might call for deletion of a particular verifiable credential to also set the revocation -and suspension bits of the verifiable credential such that any sort of -status check for the deleted credential fails and usage of the credential is +and suspension bits of that verifiable credential, such that any sort of +status check for the deleted credential fails and use of the credential is halted.
-Given the scenarios above, it is advisable that implementers allow the -moderation of what happens after a delete to be programmable such that -system flexibility is achieved to address any verifiable credential use -case. +Given the scenarios above, implementers are advised to allow the system actions +that occur after a delete to be configurable, such that system flexibility is +sufficient to address any verifiable credential use case.