ntication and transaction information. Flow control and other information that will help in message management. - XMP namespace field for grouping. It can also be used for versioning to ensure a transparent conversion of the message for different versions sup- ported by the various XMLP processors. XMLP body blocks: This is the actual payload of the message and there will be multiple body blocks in a single message envelope. The body blocks do not have any information about message transfer and is only processed at the final destination. 18.4 XML Protocol Binding The binding defines the mapping of an XMLP message, also called an XML info- set into a specific "on-the-wire" representation. This on-the-wire representation is specific to the transport and application protocol that is used to actually send the message across. So the advantage of making message definition in XML protocol independent of the transport is achieved using the concept of XMLP binding. For example, the same XML infoset could have: An XML document representation that could be sent across a vanilla TCP/ IP session. A DOM object representation that could be used to send it in a distributed computing environment. An HTML object representation that could be used to send it as a regular Web page. The XML infoset (short for information set) is an abstract data model to describe the information available from an XML document based on specification from W3C. This makes it easier to work on an XML document without the need to ana- lyze and interpret the XML syntax. There are different ways by which information XML-Based Protocols in the XML infoset can be accessed with DOM object and HTML being some of the ways that have specific APIs to satisfy the requirements of the programming language. XML protocol binding with HTTP is the most popular transport for most specifications considering that the XML protocol can be used for Web-based network and operations management. For packet-based intermittent traffic, even UDP over the XML protocol can be looked in