Differences

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

--- public:99_annexes:annex-b-terms-and-definitions:a:api [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:a:api to public:99_annexes:annex-b-terms-and-definitions:a:api nick_dido
+++ public:99_annexes:annex-b-terms-and-definitions:a:api [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
 ====== Application Programming Interface (API) ======
-[[private:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 ===== Discussion =====
@@ Line 7: / Line 7: @@
 An Application Programming Interface (API) provides an implementation interface through which software components, systems, services, applications, tools, or users request, provide, exchange, or control information or behavior.
-In the FX Demo [[private:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]], API references usually identify implementation mechanisms that later profiles may select. Logical architecture terms such as [[private:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], [[private:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], [[private:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]], and [[private:99_annexes:annex-b-terms-and-definitions:d:data_structure_instance|Data Structure Instance]] do not prescribe an API.
+In the FX Demo [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]], API references usually identify implementation mechanisms that later profiles may select. Logical architecture terms such as [[public:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], [[public:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], [[public:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]], and [[public:99_annexes:annex-b-terms-and-definitions:d:data_structure_instance|Data Structure Instance]] do not prescribe an API.
 An API can implement, expose, or support a logical communication pattern, but it does not define the logical meaning of the information exchanged.
@@ Line 17: / Line 17: @@
 ===== Source =====
-Generalised from common software architecture usage and specialized for use in the FX Demo [[private:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
+Generalised from common software architecture usage and specialized for use in the FX Demo [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
 ===== Note =====
-An API is not a logical [[private:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], [[private:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], data structure, runtime plane, or deployment artifact. An implementation profile may use an API to realize or expose those architectural elements.
+An API is not a logical [[public:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], [[public:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], data structure, runtime plane, or deployment artifact. An implementation profile may use an API to realize or expose those architectural elements.
 ===== Example =====