Skip to content

Commit

Permalink
Fix grammar and flow in Protection Information section.
Browse files Browse the repository at this point in the history
Co-authored-by: Ted Thibodeau Jr <[email protected]>
  • Loading branch information
msporny and TallTed committed Jun 27, 2024
1 parent ebc771d commit c8a368c
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -3945,7 +3945,7 @@ <h3>Protected Information</h3>
The data that is protected by any [=data integrity proof=] is the
[=transformation|transformed data=]. [=transformation|Transformed data=]
is generated by a [=transformation algorithm=] that is specified by a
particular [=cryptosuite=]. This protection mechanism is in contrast to some
particular [=cryptosuite=]. This protection mechanism differs from some
more traditional digital signature mechanisms that do not perform any sort of
[=transformation=] on the input data. The benefits of [=transformation=] are
detailed in Section [[[#transformations]]].
Expand All @@ -3971,12 +3971,12 @@ <h3>Protected Information</h3>
N-Quads [[?N-QUADS]], which is then cryptographically hashed and digitally
signed. One benefit of this approach is that the cryptographic signature is
portable to a variety of different syntaxes, such as JSON, YAML, and CBOR,
without invalidating the digital signature. More traditional digital signature
without invalidating the signature. More traditional cryptographic signature
mechanisms do not have this capability.
</p>

<p>
Implementers and developers are urged to not presume or trust information
Implementers and developers are urged to not trust information
that contains a [=data integrity proof=] unless the proof has been [=verified=]
and the verified data is provided in a return value from a software library
that has confirmed that all data returned has been successfully protected.
Expand Down

0 comments on commit c8a368c

Please sign in to comment.