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

Draft: Adding ability for vcdi presentation proof #7

Conversation

supersonicwisd1
Copy link
Collaborator

No description provided.

@supersonicwisd1 supersonicwisd1 changed the title Draft: Adding ability fro vcdi presentation proof Draft: Adding ability for vcdi presentation proof Mar 5, 2024
@@ -54,6 +54,13 @@ class Format(Enum):
".formats.dif.handler.DIFPresFormatHandler"
),
)
VCDI = FormatSpec(
"dif/",
Copy link

Choose a reason for hiding this comment

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

are we sure this should be identical to DIF above? if they are identical then why do we have separate one?

Copy link

Choose a reason for hiding this comment

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

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

For presentation we are using the DIF Presentation Exchange from https://github.com/hyperledger/aries-rfcs/blob/main/features/0510-dif-pres-exch-attach/README.md. I was following the attachment format.

@@ -127,6 +127,11 @@ class V20PresProposalByFormatSchema(OpenAPISchema):
required=False,
metadata={"description": "Presentation proposal for DIF"},
)
vc_di = fields.Nested(
DIFProofProposalSchema,
Copy link

Choose a reason for hiding this comment

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

shouldn't this be VCDI?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I didn't want to write another proposal schema since DIFProofProposalSchema already exist to avoid redundancy

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

},
PRES_20: {
V20PresFormat.Format.INDY.api: "hlindy/[email protected]",
V20PresFormat.Format.DIF.api: "dif/presentation-exchange/[email protected]",
V20PresFormat.Format.VCDI.api: "dif/presentation-exchange/[email protected]"

Choose a reason for hiding this comment

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

@supersonicwisd1 do we still need this, do you want to do a fresh PR into clean-base with the needed things?

@supersonicwisd1 supersonicwisd1 deleted the feat/w3c-implementation branch April 12, 2024 13:38
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.

2 participants