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 Aries Framework Go Test Vectors to Spec #8

Open
OR13 opened this issue Nov 16, 2020 · 4 comments
Open

Add Aries Framework Go Test Vectors to Spec #8

OR13 opened this issue Nov 16, 2020 · 4 comments

Comments

@OR13
Copy link
Contributor

OR13 commented Nov 16, 2020

hyperledger-archives/aries-framework-go#2314

I believe there is possibly more implementation support than spec support at this point.

We should get test vectors committed here, to prevent implementations from drifting to far apart.

@troyronda
Copy link

troyronda commented Nov 16, 2020

We are adding a client implementation to AFG (as @OR13 referenced above).

We are also working on our WebKMS server implementation here: https://github.com/trustbloc/kms

@peacekeeper
Copy link
Member

I'm looking at this spec, and while it sounds really useful, the spec and the two implementations mentioned here seem to be completely out of sync.

@OR13
Copy link
Contributor Author

OR13 commented Jun 16, 2021

@peacekeeper yes, this has been my experience as well... I don't believe there is a "webkms" standard yet... or even a complete spec with more than 1 implementation.

@dlongley
Copy link
Contributor

dlongley commented Jun 16, 2021

Yes, the spec needs to be brought up to date with current implementations. I believe there are at least three implementations in the wild. Digital Bazaar is currently updating its implementation with lessons learned around addressing root zcaps. We plan on updating the spec once that's finished as soon as we can find some time to do so.

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

4 participants