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
Claims description in the metadata is introduced as
A claims description object as used in the Credential Issuer metadata is an
object used to describe how a certain claim in the Credential should be
displayed to the End-User. It is used in the claims
parameter in the Credential Issuer metadata defined in (#format-profiles).
It however seems to contain information that goes more into the realm of schema definitions with
value_type which denotes the type of a value (removed in the last PR)
claim description that does not contain display - which basically seems to be a signal that this claim exists in the specific credential (especially for claims that are optional in their credential schema)
I am not convinced we need both currently as all major credential formats seem to have their own mechanism to convey schema:
namespace for mdoc
vct for sd-jwt
context for w3c vcdm
To me, it feels like both mechanisms are either under-specified or not entirely necessary & seem to duplicate the schema information of the credential formats.
The text was updated successfully, but these errors were encountered:
Claims description in the metadata is introduced as
It however seems to contain information that goes more into the realm of schema definitions with
value_type
which denotes the type of a value (removed in the last PR)display
- which basically seems to be a signal that this claim exists in the specific credential (especially for claims that are optional in their credential schema)example for the second part:
I am not convinced we need both currently as all major credential formats seem to have their own mechanism to convey schema:
To me, it feels like both mechanisms are either under-specified or not entirely necessary & seem to duplicate the schema information of the credential formats.
The text was updated successfully, but these errors were encountered: