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.

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

Open
mkhraisha opened this issue Mar 10, 2023 · 11 comments · May be fixed by #666
Open

New Section: Relationship to VC-API #529

mkhraisha opened this issue Mar 10, 2023 · 11 comments · May be fixed by #666
Assignees
Labels
v1.0 Issues that are ready for the v1.0 cut of the spec

Comments

@mkhraisha
Copy link
Collaborator

The spec should have a section that outlines the relation ship of the Trace Interop to the VC-API

@mkhraisha mkhraisha self-assigned this Apr 18, 2023
@mkhraisha
Copy link
Collaborator Author

Separate Definitions of profile:

Profile = Strict subset of the thing we are based on.
Profile = Strict subset of the thing we are based on with added information.

You do not need to read the VC-API spec to understand our spec.
We will informatively reference it but not normatively.

@nissimsan
Copy link
Collaborator

Yes. Please update the wording on this.

@nissimsan
Copy link
Collaborator

Ping @mkhraisha , updates on this?

@rhofvendahl
Copy link
Collaborator

@mkhraisha Pinging

@mkhraisha
Copy link
Collaborator Author

per patrick's comment we should point out the options field discrepancy between vc api and trace api.

@mkhraisha mkhraisha added the v1.0 Issues that are ready for the v1.0 cut of the spec label Jan 9, 2024
@PatStLouis
Copy link
Contributor

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.

@mkhraisha
Copy link
Collaborator Author

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.

@mkhraisha
Copy link
Collaborator Author

@PatStLouis to work on it soon.

@nissimsan
Copy link
Collaborator

@PatStLouis confirmed still on this.

@mkhraisha
Copy link
Collaborator Author

@PatStLouis any updates?

@nissimsan
Copy link
Collaborator

Issue pending PR resolve.

@brentzundel brentzundel linked a pull request Aug 1, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v1.0 Issues that are ready for the v1.0 cut of the spec
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants