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

feat: add bbs bls signature and key definitions #53

Merged
merged 1 commit into from
Aug 19, 2020
Merged

Conversation

tplooker
Copy link
Collaborator

@tplooker tplooker commented Jul 29, 2020

Adds the definitions for the BBS+ signatures and associated keys documented here

Requires merging of w3c/vc-di-bbs#34 and w3c-ccg/ld-cryptosuite-registry#35

index.html Show resolved Hide resolved
index.html Show resolved Hide resolved
</p>
<pre class="example prettyprint language-jsonld">
{
"@context": ["https://w3id.org/security/v1", "http://json-ld.org/contexts/person.jsonld"]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this example correct? I would expect to see your context here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was just following the pattern of JsonWebSignature2020, should I amend both?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Im not sure... I feel like a registry should always have examples that are as accurate as possible, but we're obviously still in the middle of cleaning up security vocab.... I think for now, leave it off, and just work really hard to get it into sec context v3 so we can do a big pass updating all these examples.

Copy link
Collaborator

@OR13 OR13 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is well documented, only nit is the examples could be better potentially... but thats not a reason to block merging given the state of other examples.

@OR13
Copy link
Collaborator

OR13 commented Aug 19, 2020

This is pr against unstable, merging, names may change in the future.

@OR13 OR13 merged commit e7750d5 into master Aug 19, 2020
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

Successfully merging this pull request may close these issues.

None yet

2 participants