[October 13, 2000] W3C Acknowledges XML Messaging Specification (XMSG). The W3C has acknowledged receipt of a submission for XMSG - XML Messaging Specification. Reference: W3C Note 13-October-2000, by R. Alexander Milowski (of Lexica, LLC). Document abstract: "XMSG is a specification for using XML to send messages that contain a set of XML documents, embedded non-XML data, and references to non-XML documents in a fashion that supports scalable transactions and operates on a participant model." The submission forms a multi-part document consisting of: (1) the XMSG (XML Messaging) Specification, (2) an XMSG DTD, (3) an XMSG Schema, and (4) the XMSG Schema Documentation. Lexica, LLC requests in the submission that the W3C Consortium include the submission as consideration in the XML Protocol Activity. Description: The XML messaging specification "is based on the basic principle of providing a simple way to transport multiple XML documents within one logical XML construct without dictating any layered semantics of a messaging protocol that might be layered on top. The general philosophy is to provide the general structure upon which messaging protocols for specific business or technological purposes can be layered allowing the identification of that messaging intent but not dictating the exact syntax and semantics of the subject message. In this way, manifests, metadata, and other messaging specific constructs can be tailored to specific vertical markets or technology applications. In general, the idea of an XML message presented by this specification is three-fold: (1) A pair or triplet of participants involved in the message are identified by URI values. (2) Metadata may be associated with the message itself. (3) A set of documents is contained and identified by URI allowing for document specific metadata. The goals of this specification are (1) To provide the ability to transport multiple documents and references to associated data objects within a single document (a 'message') and preserve their identity. (2) To provide the ability to associate metadata with both the documents and the message without modifying the original document or schemas for those documents. (3) To provide the ability to transport non-XML data as a document within the message. (4) To provide a simple way to accomplish XML messaging." W3C Team Comment on the NOTE has been provided by Yves Lafon, W3C lead for XML Protocol Activity: "The submission provides a description of using XML to send MIME mail like messages that contain XML documents, non-XML data and references to other documents. In XMSG, a message consists of information about the message itself, such as the origin, the destination, a unique ID used to identify and track it, as well as management-oriented information, such as its priority, expire time and receipt management. XML Documents are embedded using a special tag in the message format, with an ID to provide easy reference inside the message. Even if errors codes remain application-specific, having classes of errors may be helpful for intermediaries..."
On XML (Instant) Messaging, see  Common Profile for Instant Messaging (CPIM);  Jabber XML Protocol;  WAP Wireless Markup Language Specification;  MessageML;  XML Messaging Specification (XMSG);  Wireless Village Initiative.