MOBILE-ID · TRUSTED LTANS
Contract versioning
Manage REST, event and applied-policy versions while preserving integration traceability.
Compatibility and version selection
Website, REST, event and policy versions have separate lifecycles. REST is 3.0.0-draft; event envelope is 2.0. These are target designs, not provisioned backend URLs.
| Change | Handling |
|---|---|
| Editorial clarification | No schema/field meaning change; check examples and routes. |
| New required field / tighter enum | Breaking for old clients; version, test consumers and plan migration. |
| Effective policy | Retain each record’s applied snapshot/revision; new settings do not rewrite history. |
Migrating from draft 2 to draft 3
Clients read ExportResult/TransferResult/HoldResult instead of ResourceResult at the affected endpoints. Acknowledgement accepts TransferAcknowledgement instead of Digest. Consumers must understand resourceType/resourceId, aggregateRevision and envelope 2.0. This is not backward compatible.