Working towards the next version of the SWIM Supporting Material

Page tree

Working towards the next version of the SWIM Supporting Material

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


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

Need: use ISRM MEPs explanation

Need

The ISRM MEPs can be a useful explanation. see

Need: clarify rel'p with TI MEP

Need

Clarify potential difference with MEP at technical level

  • No labels