Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dido:99_annexes:annex-b-terms-and-definitions:c:contract [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:c:contract to dido:99_annexes:annex-b-terms-and-definitions:c:contract nick_didodido:99_annexes:annex-b-terms-and-definitions:c:contract [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Contract ====== ====== 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 =====
Line 7: Line 7:
 A Contract represents an agreement that establishes recognised rights, obligations, terms, conditions, or performance expectations among parties. A Contract represents an agreement that establishes recognised rights, obligations, terms, conditions, or performance expectations among parties.
  
-In a [[dido:99_annexes: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.+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 ===== ===== Definition =====
Line 17: Line 17:
 ===== Source ===== ===== 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: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 ===== ===== 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 ===== ===== Example =====
  • dido/99_annexes/annex-b-terms-and-definitions/c/contract.1783793671.txt.gz
  • Last modified: 2026/07/11 11:14
  • by nick_dido