Distribution
|
The challenge of Mail.dat Conformance is one that must be met by all vendors, users, and recipients of the Mail.dat standard. In the now distant past, there was the possibility of reverting to hardcopy, manual, or some other alternative if the Mail.dat fields were inaccurate. That time is past!
|
 |
|
Mail.dat® is presented as a database consisting of files linked by Key Fields. There are 21 files, each with its own record type, from which recipients can extract any set of data serving their purpose. Mail.dat’s potential: serving recipient’s information needs efficiently and effectively while providing for all possible requests. Yet, only a limited number of the files will be used regularly. |
 |
|
Mail.XML Version 1.0 (previously known as the Transportation Messaging Specification) was originally focused on transportation and drop shipment processes, allowing customers to create, update, and cancel appointments and appointments’ content, and receive closeout data. Since the intitial publication, 13 more verisons of MailXML have been published and the scope has broadened to include data distribution (EDoc) and mailing messages. |
 |
|
Mail.XML employs Web Services messaging techonology. As such, it follows a request/response messaging structure. That means that for every request message coming from one party, there is a response message from the recieving party.
There are a number of message types within Mail.XML. These include: |
 |
|
The Mail.XML Working Group defines B2B (Business to Business) XML/ Web Services communication within the postal and mailing industry that supports automation and in the end enables cost avoidance and higher profits through improved competence and effectiveness of communication. Working Group Chairs
Angelo Anagnostopoulos, GrayHair Software
Technical Director
MailXML Specifications
► Link to the MailXML Specifications |
 |
|
Each year the Printers’ Operational Issues Study Effort (POISE) Working Group undertakes special studies and surveys for the postal supply chain from the printer perspective. The results are reported back to the membership. Recent surveys included Intelligent Mail Barcode and bundle strapping. Chair: Erv Drewek, Brown Printing Company |
 |
|
XBITS (XML Book Industry Transaction Standards) is a Working Group of IDEAlliance and a BISG committee that is designing and maintaining the standard XML (Extensible Markup Language) eDocuments to facilitate bi-directional electronic data exchanges between a diverse trading partners comprised of book publishers, manufacturers, paper mills, and component suppliers. |
 |
|
In concert with the International Periodicals Distributors Association (IPDA), the Sn’L Working Group develops industry specifications for efficient communications among those providing delivery instructions, transportation planning, and distribution services for shipment of printed product. Currently Sn’L is developing an Advance Shipping Notice for the delivery of magazines to the newsstand by engaging printers, publishers, transportation and logistics companies, and wholesalers. Chair: Frank Holland, The Clark Group, Inc.
Specifications
► Link to the Shipping and Logistics Specifications ► Link to the Advance Shipment Notice (ASN) Specification |
