/
SWIM-DEFN-210 Application message exchange pattern

SWIM Supporting Material

SWIM-DEFN-210 Application message exchange pattern

Owned by WILSON Scott
Last updated: 2024 Jul 11
1 min read

Requirement

Title

Application message exchange pattern

Identifier

SWIM-DEFN-210

Requirement

A service definition shall include or refer to information about the application message exchange pattern(s) expected to be used by the service.

Rationale

The service provider should be aware of the application message exchange pattern to be implemented.

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 (taken from the SWIM Technical Infrastructure Yellow Profile [RD 4]) are:

  • Request/Reply (synchronous or asynchronous);

  • Publish/Subscribe (Push or Pull); and

  • One Way (also known as Fire and Forget).

Level of
Implementation

Mandatory

Guidance

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

Verification Support

Completeness

Check that:

[  ] The service definition includes or refers to information about the application message exchange pattern(s) expected to be used by the service.

Consistency

Check that:

[  ] The information is consistent with the selected service interface binding.

Examples

Links to example service definitions can be found in the example service definitions page. 

Related content

Status: Living Material