Description: The Request-Response pattern is a basic communication method where one system sends a request for data, and another system processes the request and returns a response. Typically used in client-server architectures, this pattern ensures a two-way conversation between applications. In its synchronous form, like HTTP web service calls, the requester waits for a reply before proceeding. Asynchronous versions also exist, where responses may arrive later, often used in systems requiring time-consuming operations, such as human workflows or complex data aggregation. This model contrasts with one-way communication, where no reply is expected. Publisher: W3C Source: https://www.w3.org/2000/xp/Group/1/10/11/2001-10-11-SRR-Transport_MEP Last modification: 2024-01-28 Identifier: http://data.europa.eu/dr8/RequestResponseMessagePatternInteroperabilitySpecificationContract LOST view: Technical view - application EIRA concept: eira:SolutionBuildingBlock Additional identifier: http://data.europa.eu/dr8/RequestResponseMessagePatternInteroperabilitySpecificationContract ABB name: eira:RequestResponseMessagePatternInteroperabilitySpecificationContract EIF Layer: N/A Interoperability Dimension: Behavioral IoP Interoperability Saliency: The interoperability specification ABB is salient for legal interoperability because it establishes the normative statements for ensuring interoperability in public services. This ABB is salient for organizational interoperability by establishing the business principles to exchange data between public services. The Interoperability specification ABB is salient for semantic interoperability too in terms of identifying technical standards for the exchange of information between public services. And finally, the ABB is salient for technical interoperability due to it determines the technical requirements to implement the interoperability between public services. Additional information: Key Points: 1) One-to-one communication; 2) Synchronous interaction, where the client waits for the response; 3) Common in web services, APIs, and remote procedure calls.