Skip to content

Commit c48544c

Browse files
David-Chadwickdlongleykdenhartog
authored
Edit of Proof Format section (#857)
Co-authored-by: Dave Longley <[email protected]> Co-authored-by: Kyle Den Hartog <[email protected]>
1 parent ac7877f commit c48544c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

index.html

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3447,11 +3447,11 @@ <h3>Proof Formats</h3>
34473447
The data model described in this specification is designed to be proof format
34483448
agnostic. This specification does not normatively require any particular digital
34493449
proof or signature format. While the data model is the canonical representation
3450-
of a <a>verifiable credential</a> or <a>verifiable presentation</a>, the
3450+
of a <a>credential</a> or <a>presentation</a>, the
34513451
proofing mechanisms for these are often tied to the syntax used in the
34523452
transmission of the document between parties. As such, each proofing mechanism
3453-
has to specify whether the validation of the proof is calculated against the
3454-
state of the document as transmitted, against the transformed data model, or
3453+
has to specify whether the verification of the proof is calculated against the
3454+
state of the document as transmitted, against the possibly transformed data model, or
34553455
against another form. At the time of publication, at least two proof formats
34563456
are being actively utilized by implementers and the Working Group felt
34573457
that documenting what these proof formats are and how they are being used would

0 commit comments

Comments
 (0)