Closed bc-pi closed 1 month ago
For an MVP (i.e., our next draft release), we should IMO add:
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.
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 /ormeta-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.
@bc-pi @danielfett I believe we have addressed all items in this issue in the spec. I believe we can close this issue, right?
_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