Comment on page
DIVOC 3.0 Release Features
- September 21, 2022
With this release, the DIVOC platform can now generate different types of verifiable credentials. It is no longer restricted to vaccination-specific verifiable credentials.
A list of the common terms used in this document:
- Verifiable credentials (VCs) represent information found in physical credentials, such as birth registration and driving license, as well as objects that have no physical equivalent, such as ownership of a bank account. VCs are typically QR codes whose information can only be unlocked by verifiers (for example, a medical council registration certificate with a QR code). When a digital document (for example, a lab test report) has a normal QR code, anyone can read all the information inside the QR by using widely available software on the internet. Such software can read the QR code and then replace it with another QR code with different information. Whereas the information in a verifiable QR code cannot be replaced as the original data or information cannot be changed without a “private key.”
- Issuer: Refers to an issuing authority who can issue claims about a particular entity or individual that can be validated. An issuer gathers the information that needs to be contained in the VC from the entities and sends it across to DIVOC through tenant software. Example: Medical Councils.
- Tenant: Refers to any source system of issuers linked to the DIVOC platform to issue VCs. Examples: Council Software, University software, etc.
- Source systems: The tenant software that interacts with the DIVOC platform to issue VCs.
- Schema: A schema is essentially a template that tells the issuer the content, type, and description required for an attribute that needs to be part of the VC. For example, a schema can be as follows with multiple rows for other parameters:
- Beneficiary: Refers to the holder of the VC. Examples: Doctors, students, etc.
- UI: User interface
*Error codes and their corresponding responses