Closed JSAssassin closed 11 months ago
Currently, the issuers/verifiers tagged with these labels here aren't being used.
I think we should clarify which "implementations" cover which specs/tests via which tags. I'd remove any that are duplicated currently in those lists, and update the READMEs in each repo to state which tags are associated with which suite.
Essentially, now that some of these specs have moved into the W3C org, their tagged implementations should also "move" to the implementations repo there.
If that sounds right @JSAssassin @dlongley, I'm happy to do the cleanup.
Currently, the issuers/verifiers tagged with these labels here aren't being used.
I think we should clarify which "implementations" cover which specs/tests via which tags. I'd remove any that are duplicated currently in those lists, and update the READMEs in each repo to state which tags are associated with which suite.
Essentially, now that some of these specs have moved into the W3C org, their tagged implementations should also "move" to the implementations repo there.
If that sounds right @JSAssassin @dlongley, I'm happy to do the cleanup.
@BigBlueHat Sorry, I forgot to reply to this. I think that sounds right. I've opened an issue for this here - https://github.com/w3c-ccg/vc-api-test-suite-implementations/issues/85
@BigBlueHat @aljones15 cc: @msporny Do we want to retain the issuers and verifiers associated with
ecdsa-rdfc-2019
,eddsa-rdfc-2022
,vc2.0
, andEd25519Signature2020
for all implementers in this repository or should they be removed? The tests for those live in the w3c organization and the test suites there are using thevc-test-suite-implementation
repository to get the implementers. Currently, the issuers/verifiers tagged with these labels here aren't being used.