search

oauth-wg / oauth-sd-jwt-vc

draft-terbu-sd-jwt-vc
Creative Commons Zero v1.0 Universal
19 stars 12 forks source link

Add type metadata for basic display/rendering information #224

Open bc-pi opened 6 months ago

bc-pi commented 6 months ago

This is qualified with "for example" but the type metadata in the PR currently doesn't define this stuff. I'm still unsure about leaving portions of sd-jwt-vc-types like claims and display out of this PR. But should we at least track that in an issue?

_Originally posted by @bc-pi in https://github.com/oauth-wg/oauth-sd-jwt-vc/pull/220#discussion_r1548311395_

the "stuff" mentioned was other content/concepts from https://github.com/vcstuff/sd-jwt-vc-types, which PR #220 was based on

danielfett commented 6 months ago

For an MVP (i.e., our next draft release), we should IMO add:

babisRoutis commented 5 months ago

A single issue tracking the features to be added (from types), I think, is not so convenient.

Perhaps it would be better to use some more specific labels like for instance meta-display and /or meta-claims for annotate related issues. In this way, issues reported to types repo can be transferred here and new issues can be added freely.

awoie commented 5 months ago

A single issue tracking the features to be added (from types), I think, is not so convenient.

Perhaps it would be better to use some more specific labels like for instance meta-display and /or meta-claims for annotate related issues. In this way, issues reported to types repo can be transferred here and new issues can be added freely.

You can also create new issues if you believe other things are missing for your use case.