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

Clarify semantics between jwt claims and vc properties #226

Merged
merged 2 commits into from
Feb 12, 2024
Merged

Clarify semantics between jwt claims and vc properties #226

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
76040bf
clarify sematnics b/w jwt and vc properties
Jan 29, 2024
85b9bf1
Update index.html
decentralgabe Feb 1, 2024
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
11 changes: 10 additions & 1 deletion index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -413,13 +413,22 @@ <h2>JOSE Header Parameters and JWT Claims</h2>
defined in <a data-cite="VC-DATA-MODEL-2.0#validity-period">Validity Period</a>,
which represent the validity of the data that is being secured.
</p>
<p>
The claims and security provided by this specification are independent of the data
secured and semantics provided by the [[VC-DATA-MODEL-2.0]]. This means that while the security
features of this specification ensure data integrity and authenticity, they do
not dictate the interpretation of claim data.

Implementers are RECOMMENDED to avoid conflicting values, especially with claims such as
`issuer` with `iss`, `id` with `jti`, and `credentialSubject.id` with `sub`.
decentralgabe marked this conversation as resolved.
Show resolved Hide resolved
</p>
<p>
The JWT Claim Names <code>vc</code> and <code>vp</code>
MUST NOT be present.
</p>
<p>
Additional members may be present as header parameters and claims.
If they are not understood, they MUST be ignored.
If they are not understood, they MUST be ignored.
</p>
</section>
</section>
Expand Down
Loading