Versions Compared

Version Old Version 6 New Version 7
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 SWIM-SERV-018 TI Profile and bindings

Requirement

Panel
borderColorlightgrey
bgColorwhitesmoke
borderStyledashed

Title

SWIM TI Profile and interface bindings

Identifier

SWIM-SERV-250

Requirement

A service description shall include or refer to information about the profile and interface bindings for each service interface, including:

  • the selected SWIM TI Profile and its version;
  • a reference to a service interface binding as specified in the selected SWIM TI Profile;
  • a reference to a network interface binding as specified in the selected SWIM TI Profile; and
  • references to additionally supported requirements as specified in the selected SWIM TI Profile.

Rationale

To support the concept of interoperability between the service provider and service consumer, the SWIM TI Profiles only allow a certain set of technical solutions, which can be chosen by the service designer.

This is used by technical experts to assess feasibility to implement.

Verification

Completeness: Verify that the reference information is provided for each provider side and consumer side interface.

Consistency: Verify that the selected service interface binding, network interface binding and additionally supported requirements are consistent with the selected SWIM TI Profile and version.

Correctness: Not Applicable.

Examples/Notes

Note: If configuration options are available in the service interface binding, it is best practice to document them (e.g. use of GZIP compression, Message Transmission Optimization Mechanism (MTOM) encoding).

Example additionally supported requirements:

  • “SWIM-TIYP-0092, SWIM-TIYP-0098”.

Level of Implementation

Mandatory

Guidance

Verification Support

Completeness

Check that:

[  ] The service description includes or refers to information about the profile and interface bindings for each service interface.

[  ] The  information about the profile and interface bindings includes the selected SWIM TI Profile and its version.

[  ] The  information about the profile and interface bindings includes a reference to a service interface binding as specified in the selected SWIM TI Profile.

[  ] The  information about the profile and interface bindings includes a reference to a network interface binding as specified in the selected SWIM TI Profile.

[  ] The  information about the profile and interface bindings includes references to additionally supported requirements as specified in the selected SWIM TI Profile.

Consistency

Check that:

[  ] The selected service interface binding, network interface binding and additionally supported requirements are consistent with the selected SWIM TI Profile and version.

Examples

The following example shows the content as a table.

XML requests and replies embedded into SOAP messages, themselves embedded into HTTP requests and responses. Operation names are associated to SOAP requests.

SWIM TI profile and interface bindings





profile name

TI Yellow Profile specification

profile version

Edition Number 1.01

selected service interface binding

WS SOAP

selected network interface binding
IPV4_UNICAST

supported optional requirements

-

The following example shows an extract of the content of a JSON file that conforms to the Service Metadata Schema

Code Block
languagejs
titleExample of SWIM-SERV-250 using Service Metadata Schema
tbd"serviceInterface": [{
 "serviceInterfaceBinding": {
  "name": "SWIM_TI_YP_1_1_WS-N_SOAP",
  "description": "XML requests and replies embedded into SOAP messages, themselves embedded into HTTP requests and responses. Operation names are associated to SOAP requests. The interface does not use compression or message transmission optimization mechanism (MTOM). The following cipher suites are allowed in accordance with ECRYPT-CSA recommendations https://www.ecrypt.eu.org/csa/documents/D5.4-FinalAlgKeySizeProt.pdf: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384."
 },
 "networkInterfaceBinding": {
  "name": "IPV4_UNICAST"
 }
}

Complete examples are available at Example service description.