Skip to content

Commit

Permalink
Fix non-object language in verifiableCredential requirements.
Browse files Browse the repository at this point in the history
Co-authored-by: Dave Longley <[email protected]>
  • Loading branch information
msporny and dlongley committed Dec 26, 2023
1 parent 1af8541 commit 9a092d0
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -2288,10 +2288,11 @@ <h3>Presentations</h3>
The <code>verifiableCredential</code> <a>property</a> MAY be present. The value
MUST be one or more <a>verifiable credential</a> and/or
<a href="#enveloped-verifiable-credentials">enveloped verifiable credential</a>
objects. For the avoidance of doubt, the values MUST NOT be non-object values such as
numbers, strings, or URLs. These types of objects are called
objects (for the avoidance of doubt, the values MUST NOT be non-object values such as
numbers, strings, or URLs). These types of objects are called
<a href="#verifiable-credential-graphs">verifiable credential graphs</a> and
MUST be secured using a <a href="#securing-mechanisms">securing mechanism</a>.
MUST express information that is secured using a
<a href="#securing-mechanisms">securing mechanism</a>.
See Section <a href="#verifiable-credential-graphs"></a> for further details.
</dd>
<dt><var id="defn-holder">holder</var></dt>
Expand Down

0 comments on commit 9a092d0

Please sign in to comment.