scope:

General

This part of IEC 61968 defines how messages may be exchanged between cooperating systems in order to facilitate the transfer of application-specific data. Such application-specific data include but are not limited to the message payloads defined in IEC 61968 (Parts 3 to 9 and Part 13), IEC 61970 and IEC 62325.

About this document

This document provides normative definitions for:

• a set of message archetypes (Clause 5);

• a set of message exchange patterns that both sending and receiving systems are expected to implement (Clause 6);

• the exact format of the messages that are to be transmitted over the various integration technologies including a precise description of the information that each message must contain (Clause 7);

• a set of constraints and conventions to which applications must adhere in order to facilitate message exchange using IEC 61968-100 (Clause 8);

• the details of how IEC 61968-100 messages should be implemented using various underlying transport mechanisms (Clause 9).

What is not covered by this document

Security considerations lie outside the scope of IEC 61968-100. This document defers to the IEC 62351 series for definitions and practices relating to the secure transmission of messages.

Future considerations

Choice of Encoding Mechanisms

This document prescribes XML as the normative encoding mechanism for all messages defined by this document.

Future editions of IEC 61968-100 may specify additional normative encoding methods including support for JSON (RFC 4627) documents whose semantics are defined by the IEC CIM and whose syntax is defined by an IETF JSON schema.

Choice of Web Service Technologies

This document provides normative definitions for the use of SOAP Web Services (9.2) and Java Message Service (9.3) for the transport of messages.

Future editions of IEC 61968-100 may specify additional normative web service technologies such as REST.