| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:i:interface_contract [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:i:interface_contract to dido:99_annexes:annex-b-terms-and-definitions:i:interface_contract nick_dido | dido:99_annexes:annex-b-terms-and-definitions:i:interface_contract [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| ====== Interface Contract ====== | ====== Interface Contract ====== |
| |
| [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] | [[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] |
| |
| ===== Discussion ===== | ===== Discussion ===== |
| |
| An interface contract identifies a version-controlled specification governing the exchange of [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:s:structured_information_artifact|structured information]] across an [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:a:attachment_point]]. | An interface contract identifies a version-controlled specification governing the exchange of [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:s:structured_information_artifact|structured information]] across an [[dido:99_annexes:annex-b-terms-and-definitions:a:attachment_point]]. |
| |
| An interface contract defines the structural, semantic, operational, and governance expectations that apply at an attachment point. These expectations support consistent exchange, validation, interpretation, traceability, and conformance evaluation. | An interface contract defines the structural, semantic, operational, and governance expectations that apply at an attachment point. These expectations support consistent exchange, validation, interpretation, traceability, and conformance evaluation. |
| |
| An interface contract differs from an implementation interface. An implementation interface realises an exchange mechanism through a selected technology. An interface contract defines the governed architectural expectations for the exchange independently of the selected implementation technology. | An interface contract differs from an implementation interface. An implementation interface realizes an exchange mechanism through a selected technology. An interface contract defines the governed architectural expectations for the exchange independently of the selected implementation technology. |
| |
| ===== Definition ===== | ===== Definition ===== |
| |
| //version-controlled specification governing the exchange of structured information across an [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:a:attachment_point]]// | //version-controlled specification governing the exchange of structured information across an [[dido:99_annexes:annex-b-terms-and-definitions:a:attachment_point]]// |
| |
| ===== Source ===== | ===== Source ===== |
| |
| Structured Information Processing [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]] | Structured Information Processing [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]] |
| |
| ===== Note ===== | ===== Note ===== |
| ===== Example ===== | ===== Example ===== |
| |
| An interface contract specifies the required structure, semantic interpretation, validation rules, version identifier, and governance constraints for structured information exchanged between a [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:d:data_plane]] service and a downstream processing service. | An interface contract specifies the required structure, semantic interpretation, validation rules, version identifier, and governance constraints for structured information exchanged between a [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane]] service and a downstream processing service. |
| |
| ---- | ---- |