Skip to content
This repository was archived by the owner on Feb 10, 2025. It is now read-only.

Relationship between this repo and vc-api-issuer-test-suite, vc-api-verifier-test-suite #25

Closed
morgatron opened this issue Jan 30, 2023 · 3 comments · Fixed by #27
Closed

Comments

@morgatron
Copy link

It's not clear (to me) how this repo fits with https://github.com/w3c-ccg/vc-api-issuer-test-suite and https://github.com/w3c-ccg/vc-api-verifier-test-suite

If none are redundant, perhaps the README's should reflect their respective roles?

@morgatron
Copy link
Author

For anyone else as easily confused as me: it seems this repository is being replaced by the other modular suites.

(See this thread on the mailing list: https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0126.html )

@morgatron
Copy link
Author

Leaving open as I think the README should really reflect this.

@TallTed
Copy link
Contributor

TallTed commented Feb 10, 2023

Hi, @morgatron — Thank you for raising this concern. I confess, I may be more easily confused than you, as I don't have the clarity you appear to have found from the single message (not a thread, as there appear to have been no replies) on the mailing list.

I think the best way to remove confusion going forward is to put a clear statement of the relationships between the three repos (vc-api-issuer-test-suite, vc-api-verifier-test-suite, and vc-api-test-suite) into the README for each.

I would be happy to create the necessary PRs, if I understood what that statement (and/or any rewording appropriate to each repo) should say. As you do, but I do not yet, understand what needs to be said, if you would provide drafts of the statement(s), I will create those PRs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants