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.

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

Propose "instead of" in terms of media type #41

Merged
merged 3 commits into from
Jan 28, 2023
Merged
Changes from all commits
Commits
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
34 changes: 28 additions & 6 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -519,12 +519,14 @@ <h6>JWT Decoding</h6>
</section>
</section>

<section id="version-1.1">
<h2>Version 1.1</h2>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added a section so we can distinguish between production rules for 1.1 and potential production rules for future versions

<section id="production">
<h2>Production</h2>

<p>
This section describes how to produce a VC-JWT encoded
<code>VerifiableCredential</code> from a <code>Credential</code>.
<code>VerifiableCredential</code> from an object of media type <code>application/credential+ld+json</code>.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

replace ambiguous "Credential" with specific media type, this change is potentially blocked by w3c/vc-data-model#1014

If that PR changes substantially, this PR will need to be rejected / reworked.

</p>

<p class="advisment">
Expand All @@ -540,14 +542,14 @@ <h3>In addition to...</h3>

<p>
There are several members (claims) of the
<code>Credential</code> which will need to be translated to their JOSE
<code>application/credential+ld+json</code> which will need to be translated to their JOSE
form, and included next to the <code>vc</code> or
<code>vp</code> member in the JWT Claims Set.
We refer to the JWT Claims Set as <code>payload</code> in this section.
</p>

<p>
If a member is not present in the <code>Credential</code> it MUST NOT
If a member is not present in the <code>application/credential+ld+json</code> it MUST NOT
be present in the <code>VerifiableCredential</code> as either a claim
in the payload or a claim in the <code>vc</code> attribute of the
payload.
Expand All @@ -556,7 +558,7 @@ <h3>In addition to...</h3>
<p>
We start with an empty header, and payload objects, and we add members
to the header and the payload based on the content in the
<code>Credential</code>.
<code>application/credential+ld+json</code>.
</p>

<section>
Expand Down Expand Up @@ -621,10 +623,30 @@ <h4>issuance</h4>

<section>
<h3>Instead of...</h3>
<p class="issue">This section needs to be defined.</p>
<p>
The following steps are one way to obtain this representation:
</p>
<ol>
<li>
Complete the mapping for <a href="#in-addition-to">In Addition To...</a>.
</li>
<li>
Remove any properties from the <code>application/credential+ld+json</code> that were mapped.
</li>
<li>
Set the resulting object to be the <code>vc</code> member of the claim set.
</li>
</ol>

<p class="note">
The object value for the <code>vc</code> property,
when <a href="#instead-of">Instead of...</a> production rules have been applied,
is not of media type <code>application/credential+ld+json</code>.
</p>

</section>
</section>

</section>
<section>
<h2>Privacy Considerations</h2>
</section>
Expand Down