Messaging Standard - Revision history

User at 15:51, 9 March 2024

2024-03-09T15:51:23Z

User at 18:18, 16 January 2023

2023-01-16T18:18:17Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T17:03:48Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

User: Message standards ensure that messages are robust, inter-operable and reusable for many business sectors and governments.

2019-01-06T03:15:53Z

Message standards ensure that messages are robust, inter-operable and reusable for many business sectors and governments.

New page

It should be clear what a messaging standard is—right? Well, the first issue here is that messaging means different things to different people, and so, unfortunately, does the word standard. Most of us naturally will think about networking when discussing messaging standards; however, messaging covers anything from a local platform-specific [[Application_Program_Interface_(API)|application-programming interface (API)]] down to a low-level communications interface such as NDIS. Other examples of messaging interfaces include POSIX threads, [[NetBIOS_(Network_Basic_Input/Output_System)|NetBIOS]], [[Remote_Method_Invocation_(RMI)|RMI]], [[Common_Object_Request_Broker_Architecture_(CORBA)|CORBA]], [[Distributed_Component_Object_Model_(DCOM)|DCOM]], [[XML_(Extensible_Markup_Language)|XML]] Web services, Microsoft Windows' Winsock, UNIX's Berkeley sockets, and [[Open_Data-link_Interface_(ODI)|open data interface (ODI)]]. The term message itself refers to any unit of information that has to be moved. A message might be composed of just application data, or data encapsulated in your own messaging layer (if, for example, the interface to which you are writing does not support all of the functions that you need). It is useful to note that one layer's message is another layer's data. In practice, messages have been called many things, including packets, frames, events, or fancier names like [[Protocol_Data_Unit_(PDU)|protocol data units (PDUs)]].
The term standard also is not clear-cut and is widely interpreted in practice. There are true open international standards, de facto standards, and proprietary standards. True standards are usually defined by international standards bodies, or broad consortiums where "open" means that the standard has been forged by a community of interested parties, and these specifications should be available to anybody. The [[Internet_Engineering_Task_Force_(IETF)|Internet Engineering Task Force (IETF)]] is perhaps the most open standards body in this area, because practically anyone can contribute, and all standards—even drafts—are available online at no cost. (Note that some organizations do charge a fee for their standards, and, while one can understand that resources do need support) De facto standards have become standards typically by virtue of their momentum, installed base, or the absence of any other useful alternative.For example, the FIX protocol started life in 1992 as a bilateral communications framework for equity trading between Fidelity Investments and Salomon Brothers, and has since become the de facto messaging standard for pre-trade and trade communications within the equity markets. How truly "open" and specified a de facto standard is might be highly variable and, therefore, could be open to interpretation. For example, Syslog is documented for informational use by the IETF, and several implementations have significant differences, requiring dedicated parsers.<ref>What Is a Messaging Standard? [https://msdn.microsoft.com/en-us/library/bb896742.aspx#anchor2 Microsoft]</ref>

===References===
<references />

===Further Reading===
*Making messaging standards work: from definition to interoperability at runtime [http://www.ncbi.nlm.nih.gov/pubmed/14664066 NCBI]
*Guidance on Messaging Standards for Ireland [https://www.hiqa.ie/system/files/Guidance-on-Messaging-Standards.pdf Hiqa]
*Standardization of Messages [http://tfig.unece.org/contents/standardization-of-messages.htm unece.org]

@@ Line 15: / Line 15: @@
 == See Also ==
 *[[Open Data-link Interface (ODI)]]
 *[[Common Object Request Broker Architecture (CORBA)]]
 *[[Health Level 7 (HL7)]]

@@ Line 1: / Line 1: @@
-It should be clear what a messaging [[standard]] is—right? Well, the first issue here is that messaging means different things to different people, and so, unfortunately, does the word standard. Most of us naturally will think about networking when discussing messaging standards; however, messaging covers anything from a local platform-specific [[Application_Program_Interface_(API)|application-programming interface (API)]] down to a low-level communications interface such as NDIS. Other examples of messaging interfaces include [[POSIX]] threads, [[NetBIOS_(Network_Basic_Input/Output_System)|NetBIOS]], [[Remote_Method_Invocation_(RMI)|RMI]], [[Common_Object_Request_Broker_Architecture_(CORBA)|CORBA]], [[Distributed_Component_Object_Model_(DCOM)|DCOM]], [[XML_(Extensible_Markup_Language)|XML]] Web services, Microsoft Windows' Winsock, UNIX's Berkeley sockets, and [[Open_Data-link_Interface_(ODI)|open data interface (ODI)]]. The term message itself refers to any unit of information that has to be moved. A message might be composed of just [[application]] [[data]], or data encapsulated in your own messaging layer (if, for example, the interface to which you are writing does not support all of the functions that you need). It is useful to note that one layer's message is another layer's data. In practice, messages have been called many things, including packets, frames, events, or fancier names like [[Protocol_Data_Unit_(PDU)|protocol data units (PDUs)]].
+A '''message standard''' defines the syntax, structure, and semantics of a family of messages that are exchanged between counterparts. A message standard contains a message definition for each type of message that it describes. A message definition describes:
-The term standard also is not clear-cut and is widely interpreted in practice. There are true open international standards, de facto standards, and proprietary standards. True standards are usually defined by international standards bodies, or broad consortiums where "open" means that the standard has been forged by a community of interested parties, and these specifications should be available to anybody. The [[Internet_Engineering_Task_Force_(IETF)|Internet Engineering Task Force (IETF)]] is perhaps the most open standards body in this area, because practically anyone can contribute, and all standards—even drafts—are available online at no cost. (Note that some organizations do charge a fee for their standards, and, while one can understand that resources do need support) De facto standards have become standards typically by virtue of their momentum, installed base, or the absence of any other useful alternative.For example, the FIX protocol started life in 1992 as a bilateral communications [[framework]] for equity trading between Fidelity Investments and Salomon Brothers, and has since become the de facto messaging standard for pre-trade and trade communications within the equity markets. How truly "open" and specified a de facto standard is might be highly variable and, therefore, could be open to interpretation. For example, Syslog is documented for informational use by the IETF, and several implementations have significant differences, requiring dedicated parsers.<ref>What Is a Messaging Standard? [https://msdn.microsoft.com/en-us/library/bb896742.aspx#anchor2 Microsoft]</ref>
+*The structure of the messages of a particular type
-===References===
+It should be clear what a '''messaging standard''' is—right? Well, the first issue here is that messaging means different things to different people, and so, unfortunately, does the word standard. Most of us naturally will think about networking when discussing messaging standards; however, messaging covers anything from a local platform-specific application-programming interface (API) down to a low-level communications interface such as NDIS. Other examples of messaging interfaces include POSIX threads, NetBIOS, RMI, CORBA, DCOM, XML Web services, Microsoft Windows' Winsock, UNIX's Berkeley sockets, and open data interface (ODI). The term message itself refers to any unit of information that has to be moved. A message might be composed of just application data, or data encapsulated in your own messaging layer (if, for example, the interface to which you are writing does not support all of the functions that you need). It is useful to note that one layer's message is another layer's data. In practice, messages have been called many things, including packets, frames, events, or fancier names like protocol data units (PDUs).
 <references />
-===Further Reading===
+== Further Reading ==
-*Making messaging standards work: from definition to [[interoperability]] at runtime [http://www.ncbi.nlm.nih.gov/pubmed/14664066 NCBI]
+*[http://www.ncbi.nlm.nih.gov/pubmed/14664066 Making messaging standards work: from definition to interoperability at runtime]
-*Guidance on Messaging Standards for Ireland [https://www.hiqa.ie/system/files/Guidance-on-Messaging-Standards.pdf Hiqa]
+*[https://www.hiqa.ie/system/files/Guidance-on-Messaging-Standards.pdf Guidance on Messaging Standards for Ireland]
-*Standardization of Messages [http://tfig.unece.org/contents/standardization-of-messages.htm unece.org]
+*[http://tfig.unece.org/contents/standardization-of-messages.htm Standardization of Messages]