-
Notifications
You must be signed in to change notification settings - Fork 11
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 didcomm v2 service model #57
Conversation
Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
Needs some tests |
DIDCommService = DIDCommV1Service | ||
|
||
|
||
class DIDCommV2ServiceEndpoint(ServiceEndpoint): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Piggybacking on this PR because I was looking at adding a similar thing.
Since the W3C spec supports AIPs with the accept
field, I think it is correct that DIDCommMessaging
and the accept
are valid to use for didcomm v1 services. Right ?
Maybe splitting the DIDCommService
structures between the "aries flavor" of did-communication
vs the W3C spec is a more sensible way to go than v1 vs v2 ?
And a minor compat correction for flake8 Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
Signed-off-by: Daniel Bluhm dbluhm@pm.me