Differences

This shows you the differences between two versions of the page.

--- dido:99_annexes:annex-b-terms-and-definitions:c:contract [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:c:contract [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 9: / Line 9: @@
 In a [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_system|Financial System]], a Contract provides the business basis for transaction interpretation, contract state management, cash-flow computation, settlement expectations, audit, provenance, evidence, and review.
-The FX Demo uses Contract as a logical business concept. Later logical profiles and implementation profiles define the information structures, states, computations, endpoints, services, and artefacts that represent or process contract information.
+The FX Demo uses Contract as a logical business concept. Later logical profiles and implementation profiles define the information structures, states, computations, endpoints, services, and artifacts that represent or process contract information.
 ===== Definition =====
@@ Line 17: / Line 17: @@
 ===== Source =====
-Generalised from financial contract concepts in FIBO Contracts Ontology and from ACTUS financial contract modelling concepts; specialised for use in the FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
+Generalised from financial contract concepts in FIBO Contracts Ontology and from ACTUS financial contract modeling concepts; specialized for use in the FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
 ===== Note =====
-A Contract is not a legal document, database record, ledger entry, API payload, DDS sample, smart contract, executable model, or deployment artefact. Those artefacts may represent, evidence, execute, store, or process contract information.
+A Contract is not a legal document, database record, ledger entry, API payload, DDS sample, smart contract, executable model, or deployment artifact. Those artifacts may represent, evidence, execute, store, or process contract information.
 ===== Example =====