Show pageOld revisionsBacklinksAdd to bookExport to PDFODT exportBack to top Backlinks This is a list of pages that seem to link back to the current page. Application Programming Interface (API)Audit Recording RoleCrucibleCData Structure InstanceData Distribution Service (DDS)EndpointFX Audit and Provenance NodeFX Audit RecordFX Audit Record EndpointFX Cash-Flow Obligation EndpointFX Contract State EndpointFX Control Command EndpointFX Endpoint TraceabilityFX Node Status EndpointFX Policy Decision EndpointFX Provenance RecordFX Provenance Record EndpointFX Registry and Coordination NodeFX Release Package EndpointFX Replay Request EndpointFX Replay Result EndpointFX Semantic Interpretation EndpointFX Transaction Intake EndpointFX Validation Result EndpointInterface Definition Language (IDL)K3sKubernetesPart 1 Concept to FX Logical Profile ElementPart 1 Concept to FX Logical Profile ElementProtocol BuffersProvenance Recording RoleRegistry and Coordination RoleRepresentational State Transfer (REST)Remote Procedure Call (RPC)Test ItemTraceabilityP1-REQ-13-4-001P1-REQ-13-4-006P1-REQ-13-4-011P1-REQ-13-4-013P1-REQ-13-9-003P2-REQ-16-3-007Introduction1. Scope3.1 Traceability to SIP-RA3.3 Coverage of the Original FX Demo Reference Architecture4.1 Separation of Concerns7.1 Overview7.6 Communication Endpoint8.7 Cross-Plane Relationships10.3 Conceptual Element to Logical Element / PIM10.4 Logical Element / PIM to Implementation Artifact / PSM10.6 Deployment Artifact to Evidence10.7 Bidirectional Review and Impact Analysis11.2 Conceptual Elements Remain Distinct11.3 Conceptual Architecture Does Not Prescribe Realization Mechanisms11.6 Implementation Mappings Do Not Redefine Concepts12.2 Conceptual Elements Become Logical Elements12.3 Logical Architecture Preserves Conceptual Meaning12.6 Logical Architecture Provides the Basis for Implementation Profiles12.7 Traceability from Part 1 to Part 213.4 Core Conceptual Element Requirements13.9 Relationship to Logical Architecture / PIM RequirementsForewordIntroduction1. Scope3.3 Traceability to Part 1 Conceptual Architecture4.2 Explicit Communication over Implicit Coupling4.6 Traceability from Concept to Logical Model5.7 Logical Traceability Model7.1 Overview13.4 What Domain Profiles Preserve16.3 Logical Node RequirementsForewordIntroduction1. Scope3.1 Traceability to SIP-RA3.3 Traceability to Part 1 Conceptual Architecture4.1 Domain Specialization without Conceptual Redefinition4.7 Traceability from Concept to Logical Profile5.8 FX Demo Logical Traceability Model16.1 Overview20.2 Implementation Artefacts Do Not Redefine Logical Elements20.3 DDS Topics Do Not Redefine Logical Communication Endpoints20.7 Repository Layout Does Not Redefine Architecture20.12 Implementation Constraints Summary dido/99_annexes/annex-b-terms-and-definitions/c/communication_endpoint.txt Last modified: 2026/07/18 12:33by 127.0.0.1