Verifier Universal Interface (VUI)

JavaScript isn't enabled in your browser, so this file can't be opened. Enable and reload.

Estimated survey time: 3 minutes

VUI is an interop initiative that aims to standardize all the interfaces necessary in a verifier’s component. The main objective is for any wallet to be able to interoperate with any verifier component, and for any verifier component to interop with any DID resolver and registries. It is an ambitious project that tries to leverage all existing work (standard proposals and initiatives already defined), suggest improvements and fill the gaps.

There have been bi-weekly meetings held with an average of 8-10 participants from different SSI companies with following results:
- A VUI draft proposal defined as ground work for discussion. https://gataca-io.github.io/verifier-apis/
- A prototype Sandbox environment so that anyone can do very fast interop testing with these APIs. https://openapis.demo.gataca.io/home
- Engaged participants (10 organizations)
- Funding

As we transition from a small interop initiative to a standardization proposal, we'd like to engage with the broader community and start prioritizing the APIs we should start working on.

This short survey will help us focus on the activities the community needs the most.

Thank you for your time.

Do you or your organization have a tool for Verifiers (that is, do you have APIs implemented to validate Verifiable Credentials)?

Yes

Other:

Clear selection

Which other tools does your organization provide? (Please specify if other)

ID Wallet

DID method

Proprietary Schemas

A proprietary list of trusted issuers (trusted Issuer DIDs)

Other:

If your organization has an ID wallet, what formats do you support? (Please select all that apply)

Mobile App (credentials stored locally)

Desktop-based (credentials stored locally)

Browser extension (credentials stored locally)

Cloud-based (credentials stored remotely)

Do you use any existing standard draft/protocol? (Please select all that apply)

Decentralized Identifier (DID) as defined in W3C

DID resolution As defined in W3C

Verifiable Credential (VC) As defined in W3C

Verifiable Presentation (VP) As defined in W3C

Revocation List 2017/2020 as defined in W3C

DIDComm Messaging as defined in DIF

Presentation Exchange as defined in DIF

Credential Manifest as defined in DIF

Aries RFC 0037: Present Proof Protocol

Aries 0160: Connection Protocol

Aries 0167, Consent Lifecycle

Wallet Storage Design as defined in Indy

Schema.org

TRAIN

DID-SIOP

CHAPI

VC-HTTP-API

Other:

Out of the following APIs, which ones are you most interested in having standardized?

Presentation exchange (request and receive Verifiable Credentials as per W3C)

DID resolution (get public key associated to a DID)

Issuer resolution (determine if the issuer of a credential can be trusted)

VC Schema resolution (get all available schemas - get the schema catalogue)

VC status resolution (get the status of a Verifiable Credential)

Policy management (gather the policies regarding accepted credentials, issuers and levels of trust)

Consent (share an independent consent object to prove a credential sharing transaction)

Other:

Out of the following APIs, which one would you like to help standardize?

Presentation exchange

Consent

DID resolution

Issuer resolution

Schema resolution

VC status resolution

Policy management

None

Other:

If you'd like to know more, please leave your email

Submit

Clear form

Never submit passwords through Google Forms.

This form was created inside of Gataca. Report Abuse

Forms