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
mDOC supports nested claims (e.g. driving_privileges), however the claims description path as defined in Appendix B & C only allows the path array to have a length of two.
It would be useful to also enable setting claim descriptions for nested entries in mDOC credentials, especially since there is no vct with additional metadata that can be fetched for mDOC.
There's probably some complexity involved in mapping CBOR structure to a claims path, but for straighforward CBOR types such as object/map/array it would be quite easy to define.
I tried looking into the discussion of PR #276, but it's quite big and couldn't directly find a rationale for limiting the mDOC type.
The text was updated successfully, but these errors were encountered:
mdocs' nested claim driving_privileges does not allow to selectively disclose the claims inside the object AFAIK (CDDL does allow deeper nesting, but mdoc spec does not). so for mdoc, 2-layers is the deepest it can go. for driving_privileges, it would be doctype.namespace.driving_privileges. no more.
if this has changed it is a big breaking change for VP spec as well, but otherwise, it's by design
mDOC supports nested claims (e.g. driving_privileges), however the claims description path as defined in Appendix B & C only allows the path array to have a length of two.
It would be useful to also enable setting claim descriptions for nested entries in mDOC credentials, especially since there is no
vct
with additional metadata that can be fetched for mDOC.There's probably some complexity involved in mapping CBOR structure to a claims path, but for straighforward CBOR types such as object/map/array it would be quite easy to define.
I tried looking into the discussion of PR #276, but it's quite big and couldn't directly find a rationale for limiting the mDOC type.
The text was updated successfully, but these errors were encountered: