Verifying a VC should return the same credential regardless of the verification method

[David-Chadwick]

Our Data Model is that we have a credential, and by adding a proof (external or embedded) we get a verifiable credential. Conversely after verifying a VC, the credential that is returned should be identical regardless of the proofing mechanism

[selfissued]

David is correct. This logic needs to be applied to the ambiguous text in #1393 before it can be merged.

[dlongley]

A credential with a proof field does not "unbecome" a credential, it is just both a credential and a verifiable credential. However, I would be supportive of allowing both of these options to be returned from an "embedded proof" securing mechanism to enable users of either approach.

[msporny]

Conversely after verifying a VC, the credential that is returned should be identical regardless of the proofing mechanism

This was done in PR #1393, commit 8c16fec. Specifically, the text now says:

Securing mechanism specifications MUST provide a verification mechanism that returns only the information in the conforming document that has been secured, without any securing mechanism information included, such as proof or JOSE/COSE metadata. Specifications MAY provide additional mechanisms to convey other information that might be helpful (for example, during validation or for debugging purposes), such as securing mechanism metadata.

This issue is now addressed in the latest version of the specification, closing.