-
Notifications
You must be signed in to change notification settings - Fork 10
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
New Section: Relationship to VC-API #529
Comments
Separate Definitions of profile: Profile = Strict subset of the thing we are based on. You do not need to read the VC-API spec to understand our spec. |
Yes. Please update the wording on this. |
Ping @mkhraisha , updates on this? |
@mkhraisha Pinging |
per patrick's comment we should point out the options field discrepancy between vc api and trace api. |
Can we close #589 and refer to it in this issue? We have confirmed there was no misalignment now we just need a mention of this in a PR. @mkhraisha You can assign this to me. |
This should basically say go to VC API to figure out communication within trust boundary. The should say the only thing we care about is interoperable communication across trust boundaries in a supply chain setting. |
@PatStLouis to work on it soon. |
@PatStLouis confirmed still on this. |
@PatStLouis any updates? |
Issue pending PR resolve. |
The spec should have a section that outlines the relation ship of the Trace Interop to the VC-API
The text was updated successfully, but these errors were encountered: