You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imagine that we start with the core VCDM (i.e. application/vc+ld+json) and want to secure it according to Section 3 (Securing the Core VC Data Model). The VCDM may have additional property fields defined by the issuer (for the sake of this example, let's say the issuer populated a verified_claims property). If interpreted as a JWT, the claim who's name is verified_claims was registered in this spec.
What's the guidance on conflicting JWT Claim names and VC property names when securing the core VCDM?
Personally, I think we should be wrapping the VCDM inside the vc registered claim; but it seems like we've moved in a different direction.
The text was updated successfully, but these errors were encountered:
Imagine that we start with the core VCDM (i.e.
application/vc+ld+json
) and want to secure it according to Section 3 (Securing the Core VC Data Model). The VCDM may have additional property fields defined by the issuer (for the sake of this example, let's say the issuer populated averified_claims
property). If interpreted as a JWT, the claim who's name isverified_claims
was registered in this spec.What's the guidance on conflicting JWT Claim names and VC property names when securing the core VCDM?
Personally, I think we should be wrapping the VCDM inside the
vc
registered claim; but it seems like we've moved in a different direction.The text was updated successfully, but these errors were encountered: