w3c / vc-test-suite

Verifiable Credentials WG Test Suite
https://w3c.github.io/vc-test-suite/
BSD 3-Clause "New" or "Revised" License
69 stars 39 forks source link

Add links to repos for public implementations #86

Open deiu opened 5 years ago

deiu commented 5 years ago

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 commented 5 years ago

Good point, agreed.

dmitrizagidulin commented 4 years ago

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

dckc commented 4 years ago

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 commented 2 years ago

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 commented 8 months ago

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