In the EDI industry, a message is a formalized data record transmitted between computers. In cryptography, a document (or other content) to which cryptographic techniques are applied to ensure privacy or authenticity, for example. In the context of e-mail, a unit of transmission from one individual to another.

(USA) The entire data stream including the outer envelope. (International) The equivalent of transaction set in the USA. OASIS Organization for the Advancement of Structured Information Standards

A collection of data that represents a entity of some sort, such as a purchase order, an activity notification, a request, etc. Within an integration context, an event is the basic unit of data that is exchanged between processes or systems. The terms event, document and message are often used interchangeably.

A block of information in EDI making up a business transaction or part of a business transaction within an international standard

Any data that has been encoded for transmission to or received from a person or entity. Messages may be encrypted for privacy, digitally signed for authentication purposes, or both.

Complete transmission of data or text. Sometimes used interchangeably with block.

The communication of information from a source to one or many destinations. This term can be used to describe a set of transactions in Electronic Data Interchange (EDI) or Extended Markup Language. The transaction can include data for a purchase order, a shipping notice, or any other electronic document.

A complete set of information transmitted among players in a game. Messages may be broken into packets by NetSprocket for actual transmission over the network.

A set of data elements used to exchange information between institutions (or their agents). No communications (header/trailer, protocol, or character code) or security implications are assumed or identified.

The EDIFACT term for a transaction set. A message is the collection of data, organized in segments, exchanged by trading partners engaged in EDI. Typically, a message is an electronic version of a document associated with a common business transaction, such as a purchase order or shipping notice. A message begins with a message header segment, which identifies the start of the message (e.g., the series of characters representing one purchase order). The message header segment also carries the message type code, which identifies the business transaction type. EDIFACT's message header segment is called UNH; in ANSI X12 protocol, the message header is called ST. A message ends with a message trailer segment, which signals the end of the message (e.g., the end of one purchase order). EDIFACT's message trailer is labeled UNT; the ANSI X12 message trailer is referred to as SE.

a collection of typed data

a cross layer data packet that travels all of the layers to the top

a data stream comprising a plurality of packets

a large block, so maybe a too long MIDI connection or a bad MIDI cable can result in corrupt data

a meaningful unit of data that a node can process (average or filter, etc

an abstract description of what the exchanged data looks like

an atomic packet of data that can be transmitted on a channel

a potentially multi-part package of documents and context data that constitutes

a structure with various fields of data, the content and format of which is only accessible to compatible sender and receiver components

a user-defined data unit whereas a packet is a network-defined data unit

A meaningful unit of information. A Protocol Data Unit (PDU) of defined format and purpose. Refers to the basic unit of data being transmitted.

The business information piece of an EDI transmission. For example, the purchase orders, or the invoices, or shipping information.

The basic unit of data exchange between peers; each message contains an ordered sequence of named sub sections, called message elements, which can hold any form of data. Messages are exchanged by the Pipe Services and the End Point Services.

The fundamental unit of email, a message consists of a header and a body and is often contained in an envelope while it is in transit from the sender to the recipient.

A block of information in EDI, making up a business transaction, or part of a business transaction. In North America, this is normally called a transaction set.

A collection of data, organized in segments, and exchanged to convey meaning between partners engaged in EDI. Also called a "document" or "transaction set". It represents a common business transaction. Each message starts with a message header segment and ends with a message trailer segment. The message type identifying the type of business transaction is given in the message header segment.

A message is a complete unit of data available to be sent or received by services. It is a self-contained unit of information exchange. A message always contains a SOAP envelope, and may include additional MIME parts as specified in MTOM, and/or transport protocol headers.

A unit of information that may be composed of one or more data fields. The data portion of a transaction.

In IS-95, a data structure consisting of a length field, message body (or payload), and CRC for detection of errors.

The smallest unit by which data can be transferred within an interchange in the HA/GP Links Project.

An arbitrary amount of information whose beginning and end are defined. In data communications, a message consists of a header, a body, and a trailer.

Application layer (Layer 7) logical grouping of information, often composed of a number of lower-layer logical groupings such as packets. The terms datagram, frame, packet, and segment are also used to describe logical information groupings at various layers of the OSI reference model and in various technology circles.

Data typically sent in a single request packet. A group of characters and control bits transferred as a unit; the data portion of a packet.