MOBILE-ID · TRUSTED LTANS
Bilingual terminology
Look up business definitions and bilingual terminology for preservation and integration.
Terminology dictionary
| Term | Definition |
|---|---|
| Archive Object | A data unit registered for preservation. |
| Evidence Record | Cryptographic evidence bound to one or more data objects. |
| Archive Time-Stamp | A timestamp plus the hash-tree context needed to bind data. |
| Archive Time-Stamp Chain | Ordered archive timestamps connected through timestamp renewal. |
| Archive Time-Stamp Sequence | Ordered chains whose evolution includes hash-tree renewal. |
| Reduced Hash Tree | The sibling digest values needed to reconstruct a root for selected data. |
| Timestamp Renewal | A renewal that protects preceding timestamp evidence while the data hash remains suitable. |
| Hash-Tree Renewal | A renewal that reprocesses archived data and prior evidence with a secure digest. |
| Time-Stamp Token | A signed TSA token binding a digest to trusted time. |
| Message Imprint | The algorithm identifier and digest submitted to the TSA. |
| Nonce | Request context used to correlate a timestamp response when present. |
| Archive Policy | Identified preservation and access rules applying to archived objects. |
| LTANS Profile | A versioned selection of policy, TSA, syntax and storage settings. |
| Archival Period | The agreed time or event-based period of preservation. |
| Retention | Rules controlling how long an object remains preserved. |
| Legal Hold | An authorized restriction blocking disposition within a case scope. |
| Controlled Disposition | Approved removal after retention, hold and storage-lock checks. |
| Deposit Acknowledgement | Acceptance evidence that does not assert evidence generation has finished. |
| Archive Group | A set of related objects preserved with an explicit grouping context. |
| Metadata | Descriptive information supporting retrieval and interpretation. |
| Reference | An identifier or locator whose possession alone does not grant access. |
| Data Custody | Allocation of payload, evidence and access responsibilities. |
| Provider-Managed | Custody where the provider retains agreed payload and evidence. |
| Customer-Managed | Custody where the customer retains the payload or storage control. |
| Bring Your Own Storage | Customer-controlled storage connected under durable access terms. |
| Hash-Only | A model retaining digests while original data remains externally held. |
| External Reference | A locator pointing to data whose availability needs separate assurance. |
| Original Data | The exact bytes whose integrity the evidence protects. |
| Payload | The archived content as distinct from its evidence and metadata. |
| Evidence Version | An immutable revision linked to the preceding preservation history. |
| Validation Material | Certificates, revocation data and context required for verification. |
| Trust Anchor | A verifier-selected trusted certificate or key for path evaluation. |
| Trust Context | Versioned trust inputs, validation time and governing policy. |
| Certificate Path | The certification chain evaluated under the selected trust policy. |
| Certificate Status | A status result whose source and freshness must be evaluated. |
| Revocation | Withdrawal of certificate validity under issuer rules. |
| Verification Report | Recorded check outcomes and reasons for a specific data/evidence pair. |
| Indeterminate | An outcome where available material cannot establish validity or invalidity. |
| Algorithm Suitability | Assessment of a cryptographic algorithm for a preservation horizon. |
| Crypto-Agility | The ability to change cryptographic mechanisms through governed renewal. |
Digest | The fixed-length output of a specified hash algorithm. |
| Hash Tree | A structure aggregating data digests into a timestamped root. |
| Root Hash | The top digest authenticating a hash tree. |
| Canonicalization | Defined processing that produces a deterministic representation. |
| Cryptographic Information | Algorithm and validation context accompanying preservation evidence. |
| Supporting Information | Additional material used to interpret or validate evidence. |
| Policy History | The policy versions applicable over an object lifetime. |
| Authentication | Establishing the identity of a requesting principal. |
| Authorization | Deciding whether an authenticated principal may act on an object. |
| Tenant Isolation | Controls separating one tenant's data and access from another. |
| Least Privilege | Granting only the permissions needed for an assigned task. |
| Dual Control | Requiring separate authorized actors for sensitive decisions. |
| Privileged Access | Elevated access subject to additional approval and auditing. |
| Service Account | A non-human identity for scoped machine integration. |
| Idempotency | Ensuring a retried command does not create duplicate effects. |
| Correlation ID | An identifier linking requests, jobs, events and audit records. |
| Request ID | An identifier for one individual request attempt. |
| Async Job | A durable resource tracking deferred execution and its result. |
| Retry | A bounded repeated attempt governed by error type and backoff. |
| Backoff | Increasing delay between retry attempts to reduce overload. |
| Dead Letter Queue | A quarantine destination for messages requiring investigation. |
| Replay | Authorized reprocessing of a retained event with duplicate protection. |
| Outbox | A store committing outgoing events with the business transaction. |
| Inbox | A receiver-side record used to deduplicate event processing. |
| Domain Event | A versioned statement of a completed domain fact. |
Webhook | An outbound event notification to a registered HTTPS consumer. |
| Ordering Scope | The aggregate boundary within which event order is preserved. |
| Schema | Machine-readable constraints for a contract object. |
| Error Code | A stable machine identifier for a specific failure category. |
| Rate Limit | A deployment-agreed bound on request frequency. |
| Export Package | A portable collection of payload, evidence and contextual material. |
| Manifest | An inventory identifying package entries and integrity values. |
| Transfer | Movement of preservation responsibility with recipient verification. |
| Provider Exit | A governed transition retaining evidence continuity beyond a provider relationship. |
| Portability | The ability to export and interpret preserved data outside a provider. |
| Reconciliation | Comparing independent records to identify missing or duplicate outcomes. |
| Checkpoint | A durable point from which interrupted work can safely resume. |
| Backup | A recovery copy requiring restoration and consistency checks. |
| Disaster Recovery | Procedures restoring service and verifying data after disruption. |
| Business Continuity | Plans maintaining agreed critical activities during disruption. |
| Evidence Continuity | Preserving verifiable evidence history through changes and recovery. |
| Data Residency | The agreed geographic locations of payload, evidence and copies. |
| Encryption at Rest | Encryption protecting stored data under a governed key lifecycle. |
| Encryption in Transit | Transport protection for data crossing service boundaries. |
| Key Rotation | Replacing active keys while retaining required decryption access. |
| Key Destruction | Irreversible removal that may affect future access and renewal. |
| Object Lock | Storage enforcement preventing modification or deletion under retention rules. |
| Immutable Storage | Storage controls restricting changes; evidence maintenance remains separate. |
| Audit Record | A record of an actor's action and decision context. |
| Transaction Log | Records of service requests, processing outcomes and correlation context. |
| Archived Log Batch | A sealed set of log records preserved as an archive object. |
| Observability | Logs, metrics and traces used to understand system behavior. |
| Distributed Trace | A linked view of one request across service boundaries. |
| Usage Metering | Counting agreed units with duplicate and reconciliation controls. |
| Quota | A plan-specific resource boundary applied under approved terms. |
| Subscription | An agreed entitlement to a versioned service plan. |
| Service Plan | A governed set of features, limits and charging units. |
| Managed Service | A deployment operated by the provider within agreed responsibilities. |
| On-Premise | A deployment controlled in the customer's infrastructure. |
| Go-Live | An approved transition after integration and operational acceptance. |
| Sandbox | A non-production environment using isolated test identities and evidence. |
| Proof of Concept | A bounded evaluation with explicit data and acceptance criteria. |
| Publication Record | Evidence of who approved content, scope and release timing. |
| Target Capability | A product design statement without verified implementation evidence. |
| Organizational Record | A source-bound record applicable only to the stated organizational scope. |