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

Add links to repos for public implementations #86

Open
deiu opened this issue Jul 23, 2019 · 5 comments
Open

Add links to repos for public implementations #86

deiu opened this issue Jul 23, 2019 · 5 comments

Comments

@deiu
Copy link

deiu commented Jul 23, 2019

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.

@dmitrizagidulin
Copy link
Collaborator

Good point, agreed.

@dmitrizagidulin
Copy link
Collaborator

(Leaving this open while new links trickle in. We have some links now, waiting on the other ones.)

@dckc
Copy link

dckc commented Oct 25, 2019

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:

A conforming processor is any algorithm realized as software and/or hardware that generates or consumes a conforming document. Conforming processors MUST produce errors when non-conforming documents are consumed. -- 1.4 Conformance

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.
https://github.com/rchain-community/rchain-dbr/blob/oauth_gateway/o2r/game/ui/gameSession.html

@stefan2904
Copy link

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.

@LuisOsta
Copy link

Just wanted to follow up on this, getting this would be great!

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

No branches or pull requests

5 participants