1. SWIM Service Description Handbook
  2. Guidance on individual requirements

SWIM-SERV-017 Message exchange pattern

Last updated: DECEMBER 5th, 2019


Requirement

Title

Message exchange pattern

Identifier

SWIM-SERV-017

Requirement

A service description shall include the message exchange pattern used by the service.

Rationale

The message exchange pattern helps understanding how the information interaction with the service works.

Verification

Completeness: Verify that the information is included.

Consistency: Verify that the information is consistent with the selected service interface binding.

Correctness: Not Applicable.

Examples/Notes

Note: Typical message exchange patterns (as from the SWIM Technical Infrastructure Yellow Profile [RD 3]):

  • Request/Reply (synchronous or asynchronous);
  • Publish/Subscribe (Push or Pull);
  • One Way (also known as Fire and Forget).

Level of Implementation

Mandatory

Guidance

Understanding message exchange patterns

The document MEP identification, developed in the SWIM-TEC community, provides information on the various notions of message exchange pattern (MEP). 

  • it introduces the concept of MEP
  • it explains the difference between primitive MEPs and application MEPs.
  • it provides the semantic of each MEP in text and diagram


Info

This requirement refers to the application message exchange pattern used by the service.

Examples

See the Message exchange pattern section within the Donlon TOBT Setting Service Description.