Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

render the updates #4

Merged
merged 1 commit into from
Jan 13, 2025
Merged

render the updates #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion spec/index.html
View file
Open in desktop
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
Loading