-
Notifications
You must be signed in to change notification settings - Fork 117
Add 'render' hint property to v2 context #1068
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
Conversation
I assume this PR depends on agreement around #1035. I'm not understanding why we would add |
without spec text indicating that the term is being reserved, I don't think adding |
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 do not believe we should add the render property to the core v2 context.
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 agree with @brentzundel that it's unnecessary to add this property.
Sorry it was a mistaken operation about approving the change on adding render property. |
No consensus was able to be reached, closing PR. |
This standalone PR adds the
render
hint property to the VC 2.0@context
. (Note: this separate from PR #1035).The
render
hint allows for linking to, or embedding, issuer display preferences / hints in a flexible manner (see the Rendering Verifiable Credentials paper from RWOT 11 for more info and examples).The intention is to add examples of
render
usage to the VC Spec directory.