Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:99_annexes:annex-b-terms-and-definitions:s:structure [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:s:structure [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Structure ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | Structure defines the form, organization, | ||
| + | |||
| + | Structure remains distinct from data values. It also remains distinct from semantics. A structure may identify a field named currency, but the field' | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //formal organization and constraint model governing a class of data// | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Informed by SIP-RA separation of data and structure; adapted from FX Demo Reference Architecture material on Data Structure Definition, Common Data Type, Topic Framework, and Data Structure Framework. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | Structure does not by itself define all semantic meaning or interpretation logic. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A Data Structure Definition for a cash-flow obligation may identify required fields such as transaction identifier, payment date, currency, amount, payer, receiver, and provenance reference. | ||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||