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 didcomm v2 service model #57

Merged
merged 8 commits into from
Jul 8, 2023
Merged

feat: add didcomm v2 service model #57

merged 8 commits into from
Jul 8, 2023

Conversation

dbluhm
Copy link
Member

@dbluhm dbluhm commented Jan 6, 2023

Signed-off-by: Daniel Bluhm dbluhm@pm.me

Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
@dbluhm
Copy link
Member Author

dbluhm commented Jan 6, 2023

Needs some tests

pydid/service.py Outdated Show resolved Hide resolved
DIDCommService = DIDCommV1Service


class DIDCommV2ServiceEndpoint(ServiceEndpoint):
Copy link
Contributor

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>
@dbluhm dbluhm marked this pull request as ready for review July 8, 2023 15:29
Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
@dbluhm dbluhm merged commit 506002d into main Jul 8, 2023
6 checks passed
@dbluhm dbluhm deleted the feature/didcomm-v2 branch October 20, 2023 17:51
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.

3 participants