decentralized-identity / waci-didcomm

Wallet And Credential Interactions for DIDComm

WACI DIDComm

WACI [wak-ee] - Wallet And Credential Interactions

QR Codes and Links for wallet and credential interactions.

Meeting Recordings

Available Here

Versions

• v0.1

Test Vectors

• aviarytech

Input Documents

This work item is consolidating a number of input documents

• Notes from IIW32

• Previouss spec: decentralized-identity/wallet-and-credential-interactions

waci-didcomm's Issues

Update VC API supports Exchange

The section describing the VC API should be updated to reflect the current consensus at W3C CCG and Trace WGs.

Spec not updating?

Hi,

I had a PR merged in a few months back but I don't see it reflected on https://identity.foundation/waci-presentation-exchange. Should I do something else to get the page updated?

Thanks!

Is this line still accurate?

This version of the specification also restricts itself to Verifiable Credentials that make use of BBS+ LD-Signatures.

I assume so, but:

• I am unsure of the referent of "this version" - v0.1? v1?
• perhaps I should go through and change every specification to profile, where the referent is this work item?

Generate Test Vectors from AFG

• Lets assume JsonWebSignature2020.
• Pick a use case (like PRC)
• English language description of tests, for both issuance and presentation.
• Define the CM objects (only relevant to issuance)
• Define the PE objects (only relevant to presentation exchange)
• write code in AFG to gather data from the examples, do not attempt AATH until AFG integration is done
• capture the issuance exchange JSON messages
• capture the presentation exchange JSON messages
• save them all to a directory.
• open a pull request here to add examples from the directory to the spec.

Issue Credential and Present Proof v3 - RFC and URI resolution

Currently, the issue_credential v3 and present_proof v3 live in DIF WACI repo https://github.com/decentralized-identity/waci-presentation-exchange. What's the right place to host these ? Based on hyperledger/aries-agent-test-harness#447 (comment)

Also, we need to consider URI resolution

Attachment links not working

Hi,
The links for the presentation exchange attachment formats do not work.
In the protocol you say that "dif/presentation-exchange/[email protected]" and "dif/presentation-exchange/[email protected]" attachment formats can be used (first issue here: It should be only "definition" not "definitions" if you refer to https://github.com/hyperledger/aries-rfcs/blob/main/features/0510-dif-pres-exch-attach/README.md).
But anyway. The links do not work: https://github.com/decentralized-identity/waci-didcomm/blob/main/0510-dif-pres-exch-attach/README.md#propose-presentation-attachment-format with site result 404.
So second issue, where should I find the documentation ?
In the url I can see you refer to Aries 0510 which I guess is more for DIDComm v1 not for the version 2. I googled it by myself, but I am not sure. Shouldn't the attachement format be in regards to Presentation Exchange 2.0? https://identity.foundation/presentation-exchange/#presentation-request

V1 editorial review

Rebranding

• need to create new github repo waci-didcomm - https://github.com/decentralized-identity/waci-didcomm
• preserve github history - https://github.com/decentralized-identity/waci-didcomm
• publish latest spec - https://identity.foundation/waci-didcomm/
• redirect latest old spec to latest new spec
• archive this repo after moving all issues to the new repo.

Editorial and Content Review

Review the sections of the spec, address any spelling, grammar or readability mistakes.

Changes required for changes to serviceEndpoint in didcomm

There are some changes happening to serviceEndpoints in didcomm... These changes will need to be reflected in this spec
decentralized-identity/didcomm-messaging#352

How to do the most basic VC exchange using QR code?

I'm working a fairly basic issuer service, I'm not planning on making it very advanced, but support the basic issuance (automatic with private key on server) and storage for later retrieval.

I'm looking around at the various specifications that have come and gone, I have also investigated multiple wallets and seeing how each of them appears to implement various protocols and patterns for QR code scanning and importing to wallets.

What is the most basic flow I can implement on the service to allow importing in a wallet? Will I need to dig into the specification for individual wallets that exists?

Is there any implementation documentation or examples available?

Are test vectors correct?

hello, is this example wrong in “WACI-DIDComm Interop Profile” section 7.2 Presentation step 3.
The sequence diagram in section 6.2 Presentation describers this step is from Verifier to Wallet, but the example is:

  "from": "did:example:prover",
  "to": [
    "did:example:verifier"
  ],

CredentialFulfillment JSON-LD Document is missing.

CredentialFulfillment JSON-LD Document is not available at:
https://identity.foundation/credential-manifest/fulfillment/v1

Therefore VerifiablePresentation/CredentialFulfillment cannot be canonicalized (processed with JSON-LD Processors) and signed as shown in example:
7.1.5 Step 5 : Issue Credential

Btw why must the issuer in Step 5 sign both Verifiable Credential and VerifiablePresentation (CredentialFulfillment)? Isn't signature over Verifiable Credential enough?

Fix diagram to remove BBS+ dependency

spec generation build failure

https://github.com/decentralized-identity/waci-didcomm/runs/6263552965?check_suite_focus=true

Rendering: Wallet And Credential Interactions
Rendering: Wallet And Credential Interactions
Error: Process completed with exit code 1.