Skip to content

Commit

Permalink
Merge pull request #4 from decentralized-identity/initial-spec-draft
Browse files Browse the repository at this point in the history
render the updates
  • Loading branch information
gvelez17 authored Jan 13, 2025
2 parents f719003 + dcf3aaa commit 097ebe0
Showing 1 changed file with 7 additions and 1 deletion.
8 changes: 7 additions & 1 deletion spec/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -141,10 +141,12 @@ <h2 id="core-pattern"><a class="toc-anchor" href="#core-pattern" >§</a> Core Pa

linkStyle 0,1 stroke:#666,stroke-width:2px,stroke-dasharray: 5
</div>
<div class="caption">In this example. Claim-A makes a statement about some existing subject with a URL. Claim-A itself has an identifier, URI_A, and Claim-B uses this to make a statement about Claim-A. For example, Claim-B might be a corroboration or a rejection of Claim-A</div>
<hr>
<h2 id="linkedclaim-conformance-requirements"><a class="toc-anchor" href="#linkedclaim-conformance-requirements" >§</a> LinkedClaim Conformance Requirements</h2>
<p>A LinkedClaim:</p>
<ul>
<li><strong>MUST</strong> have a subject that can be any valid URI</li>
<li><strong>MUST</strong> have a subject that can be any valid <a path-0="datatracker.ietf.org"path-1="doc"path-2="html"path-3="rfc3986"href="https://datatracker.ietf.org/doc/html/rfc3986" >URI</a></li>
<li><strong>MUST</strong> itself have an identifier that is a well-formed URI (URN is acceptable)</li>
<li><strong>MUST</strong> be cryptographically signed, such as with a DID</li>
<li><strong>SHOULD</strong> provide a mechanism to retrieve deterministic machine-readable content from its URI</li>
Expand Down Expand Up @@ -202,6 +204,8 @@ <h3 id="signer-attestation-and-content-integrity-pattern"><a class="toc-anchor"

linkStyle 0,1 stroke:#666,stroke-width:2px,stroke-dasharray: 5
</div>
<div class="caption">Here Claim-A makes an attestation specifically about the signer of Claim-B. Claim-B also has an evidence field which points to an external URL, and includes a hash of the evidence contents to ensure integrity.</div>
<hr>
<h3 id="public-evidence-supporting-a-private-claim"><a class="toc-anchor" href="#public-evidence-supporting-a-private-claim" >§</a> Public evidence supporting a Private Claim</h3>
<div class="mermaid">
graph LR
Expand Down Expand Up @@ -243,6 +247,8 @@ <h3 id="public-evidence-supporting-a-private-claim"><a class="toc-anchor" href="

linkStyle 0,1 stroke:#666,stroke-width:2px,stroke-dasharray: 5
</div>
<div class="caption">In this pattern, we have a Private-Claim held in a Private-Wallet, which the holder may choose to show upon request; in addition a public Validation-A has been made of Private-Claim, with evidence, which a viewer can see and assemble together with the presented private claim. Viewers without access to the private claim will only see the validation without the private claim details (perhaps containing personal information).</div>
<hr>
<h2 id="minimal-example"><a class="toc-anchor" href="#minimal-example" >§</a> Minimal Example</h2>
<p>Fulfills only the MUST requirements.</p>
<pre><code>{
Expand Down

0 comments on commit 097ebe0

Please sign in to comment.