# Glossary

<table><thead><tr><th width="187">Term</th><th>Description</th></tr></thead><tbody><tr><td>ABIS</td><td><a href="https://docs.mosip.io/1.2.0/id-lifecycle-management/supporting-components/biometrics/abis">Automated Biometric Identification System.</a></td></tr><tr><td>AID</td><td><a href="https://docs.mosip.io/1.2.0/id-lifecycle-management/identity-management/identifiers#rid-aid">Application ID.</a></td></tr><tr><td>Auth</td><td>The process of verifying one’s identity.</td></tr><tr><td>CBEFF</td><td><a href="https://docs.mosip.io/1.2.0/id-lifecycle-management/supporting-components/biometrics/cbeff-xml#cbeff">Common Biometric Exchange File Format.</a></td></tr><tr><td>CTK</td><td><a href="https://docs.mosip.io/compliance-tool-kit">Compliance Tool Kit.</a></td></tr><tr><td>Device</td><td>Hardware capable of capturing biometric information.</td></tr><tr><td>Device Provider</td><td>An entity that manufactures or imports the devices in their name. This entity should have legal rights to obtain an organization-level digital certificate from the respective authority in the country.</td></tr><tr><td>Device Provider Certificate</td><td>A digital certificate is issued to the "Device Provider". This certificate proves that the provider has been certified for L0/L1 respective compliance. The entity is expected to keep this certificate in secure possession in an HSM. All the individual trust certificates are issued using this certificate as the root. This certificate is issued by the countries in conjunction with a trusted registry.</td></tr><tr><td>Device Registration</td><td>The process of a device obtaining a certificate from the management server.</td></tr><tr><td>FPS</td><td>Frames Per Second.</td></tr><tr><td>FTM</td><td>Foundational Trust Provider.</td></tr><tr><td>FTM Provider</td><td>An entity that manufactures or guarantees the trustworthiness of the foundational trust module. This can be the device provider as well.</td></tr><tr><td>FTM Provider Certificate</td><td>A digital certificate issued to the "Foundational Trust Provider". This certificate proves that the provider has successfully gone through the required Foundational Trust Provider evaluation. The entity is expected to keep this certificate in secure possession in an HSM. All the individual FTM trust certificates are issued using this certificate as the root. This certificate would be issued by the countries in conjunction with a trusted registry.</td></tr><tr><td>Handle</td><td>A handle as username is a unique identifier used instead of system generated usernames/passwords for enabling login, identification, or online interactions.</td></tr><tr><td>Header in signature</td><td>The header in the signature means the attribute with "alg" set to RS256 and x5c set to base64encoded certificate.</td></tr><tr><td>ID Schema</td><td>A standard JSON schema that defines a dataset that can be stored in the Identity repository for a resident.</td></tr><tr><td>ISO format timestamp</td><td>ISO 8601 with format yyyy-mm-ddTHH:MM:ssZ (Example: 2020-12-08T09:39:37Z). This value should be in UTC (Coordinated Universal Time).</td></tr><tr><td>KYC</td><td>Know Your Customer. The process of providing consent to perform profile verification and update.</td></tr><tr><td>L0 Certified Device/L0 Device</td><td>A device is certified as one where the encryption is done on the host machine device driver or the SBI service.</td></tr><tr><td>L1 Certified Device/L1 Device</td><td>A device certified as capable of performing encryption in line with this specification in its trusted zone.</td></tr><tr><td>MA</td><td><a href="https://docs.mosip.io/1.2.0/id-lifecycle-management/identity-issuance/registration-processor/test/manual-adjudication-and-verification#manual-adjudication-request-to-queue-is-as-follows">Manual Adjudication.</a></td></tr><tr><td>MDS</td><td><a href="https://docs.mosip.io/1.2.0/id-lifecycle-management/supporting-components/biometrics/mds-specification">MOSIP Device Service.</a></td></tr><tr><td>Management Server</td><td>A server run by the device provider to manage the life cycle of the biometric devices.</td></tr><tr><td>MOSIP</td><td><a href="https://www.mosip.io/#1">Modular Open Source Identity Platform.</a></td></tr><tr><td>MV</td><td><a href="https://docs.mosip.io/1.2.0/id-lifecycle-management/identity-issuance/registration-processor/test/manual-adjudication-and-verification#verification">Manual Verification.</a></td></tr><tr><td>Open Source</td><td>Open source refers to freely available software for anyone to use, modify, and share, ensuring trusted and transparent technology that adheres to global standards.</td></tr><tr><td>Payload</td><td>Payload is the byte array of the actual data, always represented as base64 url encoded.</td></tr><tr><td>Pre-registration</td><td>A resident-facing web-based portal that allows a resident to provide basic demographic data, upload document proofs, and book an appointment at a preferred registration centre, to complete the rest of the registration process.</td></tr><tr><td>Registration</td><td>A process that allows an individual to provide basic demographic information and biometrics to register and avail a Unique Identification Number (UIN).</td></tr><tr><td>SBI</td><td><a href="https://docs.mosip.io/1.2.0/id-lifecycle-management/supporting-components/biometrics/sbispec">Secure Biometric Device Interface.</a></td></tr><tr><td>SDK</td><td>Software Development Kit.</td></tr><tr><td>Signature</td><td>All signatures should be as per RFC 7515.</td></tr><tr><td>Signature(Base64)</td><td>Base64 url encoded signature bytes.</td></tr><tr><td>UIN</td><td>A unique number assigned to a resident. UIN never changes and is non-revocable. UIN is randomized, so one should not be able to derive any Personal Identifiable Information (PII) from the number itself.</td></tr><tr><td>Vendor-Neutral</td><td>An approach that is not dependent on or restricted to a specific vendor, allowing interoperability and flexibility to integrate with a wide range of MOSIP compliant technologies/service providers.</td></tr><tr><td>VID</td><td>Virtual ID is an alias identifier that can be used for authentication transactions. To know more, click <a href="https://docs.mosip.io/1.2.0/id-lifecycle-management/identity-management/identifiers#vid">here</a>.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mosip.io/1.2.0/general/glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
