3 Terminology
Terminology used within this specification.
Was this helpful?
Terminology used within this specification.
We recognise there are common terms across all ID related Building Blocks (Identity, E-Signature, Consent, Wallet). We define these here.
In addition the following terms are specific to the e-Signature Building Block.
(also known as eSignature, electronic signature, digital signature)
A data unit which is used by a Signatory to indicate his or her link to a Document
Data that links a public key to a natural person and confirms the name of that person
A natural person or an application delegated by the user who can create a digital signature
Configured software and/or hardware used to create an eSignature. Two types of eSignature creation devices are supported:
Local - Private keys are stored locally on mobile devices.
Remote - Private keys are stored on the remote secure storage.
An application that has the Document that needs the Signatory's signature
Data that needs to be signed by the Signatory. It can be any data file in an arbitrary format. Document to be signed is usually handled by a third party and made available to Signatory after signing.
The process of identifying Signatory, issuing a Certificate, and binding it to an eSignature Creation Device. User identification is performed using Govstack's Identity Building Block.
Hardware Security Module - a device or software that can store private keys safely.
Signature Creation Device - Can be local or remote based on where the keys are stored.
A certificate format as defined in V3
Compliant to RFC3161
The process of using SCD or One Time signature APIs to encrypt the hash of the document.
Certificate Signing Request as per RFC 2986
A private key is created upon authentication of the user and expires right after the signature. Should not be confused with OTS or related signature models.
All revocation of certificates will be available over OCSP. Follows the respective standards RFC 8954.
Was this helpful?
Was this helpful?