Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Define Reference ID #36

Closed
OR13 opened this issue Mar 12, 2020 · 3 comments
Closed

Define Reference ID #36

OR13 opened this issue Mar 12, 2020 · 3 comments
Assignees
@OR13

Comments

@OR13
Copy link
Contributor

OR13 commented Mar 12, 2020

Is it the vc.id or a linked identifier for it?
@llorllale
Copy link
Contributor

My thoughts on this is it should be opaque to the caller.

@kimdhamilton kimdhamilton reopened this Aug 14, 2020
@kimdhamilton kimdhamilton reopened this Aug 14, 2020
@kimdhamilton kimdhamilton transferred this issue from w3c-ccg/vc-issuer-http-api Aug 14, 2020
OR13 pushed a commit that referenced this issue Sep 18, 2020
@troyronda
Add TrustBloc endpoints. (#36)
b814ef7
@OR13
Copy link
Contributor Author

OR13 commented Jul 20, 2021

believe this is now obsolete, templating no longer supported.

@msporny
Copy link
Contributor

msporny commented Jul 20, 2021

We made a decision on the 2021-07-20 telecon that resolved to not support templating or any other reference IDs, closing based on this resolution:

RESOLVED: Regarding issue #34, if a caller desires to build a VC incrementally of from a template, the caller can use another API to do so and then send the fully formed VC to the VC HTTP API for processing.

@msporny msporny closed this as completed Jul 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@OR13 OR13

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@msporny @llorllale @kimdhamilton @OR13