-
Notifications
You must be signed in to change notification settings - Fork 39
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
Add links to repos for public implementations #86
Comments
Good point, agreed. |
(Leaving this open while new links trickle in. We have some links now, waiting on the other ones.) |
I was about to raise a "what do the columns represent?" issue, but perhaps this issue is close enough. Please add some prose about what the columns represent. Are they pieces of software? The link to https://github.com/decentralized-identity/did-jwt-vc suggests yes, though originally I thought perhaps they were perhaps collections of claims documents submitted by some source, and the rows were evaluations of whether the documents did or did not meet various constraints. Ah... the relevant text seems to exist already; please cite / excerpt it:
for (my) reference: I developed a tool to "upgrade" discord identities by binding them to public keys. I wonder if having that tool conform to this spec would add any value. |
I also think it makes sense to reference the evaluated implementations somewhere in the report. One reason for this is that there are at least two implementations that call themselves "verifiable-credential-java". ;-) It also might make sense to reference the evaluated version, git commit, or something like that. |
Just wanted to follow up on this, getting this would be great! |
The current implementation report does not contain links to current (public) implementations. I would like to invite everyone to also provide a link to the corresponding repo when submitting test results. This would help a lot with transparency regarding W3C process and CR requirements.
Please feel free to reply to this issue and I'll put together the list.
The text was updated successfully, but these errors were encountered: