MOBILE-ID · TRUSTED LTANS
Claim & Evidence Register
Classify statements as organizational records, standards references or integration design.
Interpret each claim type
| Claim | Required basis | Do not infer |
|---|---|---|
| Certification | Correct subject, number, scope, dates and source; maintenance when verifiable. | Organizational ISO/PAD/eID does not automatically certify LTANS or QTSP. |
| Standards reference | Document, clause, capability mapping and test. | Design mapping is not certification or interoperability acceptance. |
| Tested | Environment, versions, data, procedure and results; separate fixtures from backend. | Valid JSON does not imply valid ERS. |
| Customer / connection | Scope, date and publication authority; connector acceptance when claimed. | Other PKI experience is not automatically a Trusted LTANS deployment. |
From claim to supporting record
Due-diligence requests should identify the question, object, environment and time. Mobile-ID confirms shareable records and scope; preserve provenance and change history. Unsupported extensions remain references or designs.