Versions Compared

Version Old Version 5 New Version 6
Changes made by

WILSON Scott

WILSON Scott

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
titlePage Table of Content

Table of Contents

Info
titleVersion

This page concerns v2.0 of the Specification. Supporting material on v1.0 is <tbd>

Requirement

Panel
borderColorlightgrey
bgColorwhitesmoke
borderStyledashed

Title

Application message exchange pattern

Identifier

SWIM-SERV-210

Requirement

A service description shall include or refer to information about the application message exchange pattern(s) 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 4]):

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

Level of Implementation

Mandatory

Guidance

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

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

Example

Application message exchange pattern

The service follows the Synchronous Request/Response Message Exchange Pattern.