-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use path
for mdoc
#368
Use path
for mdoc
#368
Conversation
|
||
The result of the processing is the set of selected JSON elements. | ||
|
||
## Semantics for ISO mdoc-based credentials |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this section here and not in the mdoc credential format appendix? It's explicitly for ISO mdoc, so I don't understand why it should be here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think for the symmetry with JSON-based credentials section. will merge as-is since there are enough approvals and no other blockers. we can fix this later if necessary, as we did with the mdoc section in the very first DCQL PR.
A question from my side: In the mdoc case, is it valid to have a path with a single element (the namespace)? If not, should somehow this constraint appear on the spec in the mdoc section? |
my understanding is that path for mdoc always has at least 2 elements, so we should make that clear |
It seems that I hadn't read carefully the PR. |
No description provided.