Skip to content

Commit f26462c

Browse files
committed
Clarify meaning of unsecured/secured document.
1 parent acba0d7 commit f26462c

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

index.html

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1820,11 +1820,12 @@ <h2>Algorithms</h2>
18201820

18211821
<p>
18221822
The algorithms defined below operate on documents represented as <dfn
1823-
data-cite="RFC8259#section-4">JSON objects</dfn>. This specification follows
1824-
[[JSON-LD-API]] in representing a JSON object as an [[Infra]] [=map=]. An
1825-
<dfn class="export">unsecured data document</dfn> is a [=map=] with no
1826-
`proof` [=map/key=]. A <dfn class="export">secured data document</dfn> is a
1827-
[=map=] with a `proof` [=map/key=].
1823+
data-cite="RFC8259#section-4">JSON objects</dfn>. This specification follows the
1824+
[[[JSON-LD11-API]]] specification in representing a JSON object as an
1825+
[[[Infra]]] [=map=]. An <dfn class="export">unsecured data document</dfn> is a
1826+
[=map=] that has not yet had the desired proof added to it, but it MAY contain a
1827+
proof value added to it by a previous process. A <dfn class="export">secured
1828+
data document</dfn> is a [=map=] that has had the desired proof(s) added to it.
18281829
</p>
18291830

18301831
<p>

0 commit comments

Comments
 (0)