Differences

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

--- fxdemo:01-part:12-relationship-to-the-logical-architecture-pim:12-2-conceptual-elements-become-logical-elements [2026/06/29 14:31] – ↷ Page moved from fxdemo:01-part:12-2-conceptual-elements-become-logical-elements to fxdemo:01-part:12-relationship-to-the-logical-architecture-pim:12-2-conceptual-elements-become-logical-elements owen
+++ fxdemo:01-part:12-relationship-to-the-logical-architecture-pim:12-2-conceptual-elements-become-logical-elements [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 2: / Line 2: @@
 [[fxdemo:01-part:start | Go to Top ]]
-The Logical Architecture / PIM refines conceptual elements into platform-independent logical elements.
+The [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Architecture]] / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] refines conceptual elements into platform-independent logical elements.
-For example, Part 1 defines Node as an architectural participant in a distributed financial system. Part 2 may define Logical Nodes and describe the responsibilities, interactions, and constraints.
+For example, Part 1 defines [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] as an architectural participant in a distributed [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_system|Financial System]]. Part 2 may define Logical Nodes and describe the responsibilities, interactions, and constraints.
-Part 1 defines a Communication Endpoint as a point of information exchange used by one or more Nodes. Part 2 may define logical endpoints, endpoint roles, endpoint relationships, and information-flow patterns without selecting a specific communication technology.
+Part 1 defines a [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] as a point of information exchange used by one or more [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]]s. Part 2 may define logical endpoints, endpoint roles, endpoint relationships, and information-flow patterns without selecting a specific communication technology.
-Part 1 defines Data Structure Definition as a description of the structure, meaning, and constraints of a class of information. Part 2 may define logical information structures, logical message classes, logical event classes, or logical record classes without binding them to IDL, JSON Schema, XML Schema, database schemas, or generated code.
+Part 1 defines [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]] as a description of the [[dido:99_annexes:annex-b-terms-and-definitions:s:structure|Structure]], [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantics]], and constraints of a class of information. Part 2 may define logical information structures, logical message classes, logical event classes, or logical record classes without binding them to IDL, JSON Schema, XML Schema, database schemas, or generated code.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>