Message Compliance Dump Format

Bloomberg LP
MESSAGE COMPLIANCE DUMP FORMAT
Version 1.6
September 14, 2009
NOTICE: Copyright Bloomberg L.P., 2003 - 2007 All Rights Reserved. Property of Bloomberg L.P. (BLP) This document is made available solely pursuant to the terms of a BLP license agreement, which governs its use.
MSG Daily Dump XML Format Section 1 1
NY R&D Message Compliance Version: 1.6
General Information .................................................................................................................................................................. 3 Business Objective ............................................................................................................................................................ 3 1.1 1.2 Feature Definition ............................................................................................................................................................. 3 1.3 Revision History ................................................................................................................................................................ 3 2 Dump Format............................................................................................................................................................................. 6 2.1 Plain-Text ........................................................................................................................................................................... 6 2.2 XML Format...................................................................................................................................................................... 8 3 Appendix A ............................................................................................................................................................................... 24 3.1 XSD Format Specification ............................................................................................................................................. 24 3.2 Sample XML File ............................................................................................................................................................ 28 4 Glossary ..................................................................................................................................................................................... 35
Author:
Hector M Olmeda Page 2 of 40 Date: DO NOT DISTRIBUTE WITHOUT PERMISSION DI
September 14, 2009
MSG Daily Dump XML Format Section 1
1 General Information 1.1 BUSINESS OBJECTIVE

To standardize the daily compliance dumps being generated by Bloomberg.
1.2 FEATURE DEFINITION

This document outlines the format semantics as well as explains the meaning of the various data elements.
1.3 REVISION HISTORY

Highlights 1. 2. 3. 4. 5. 6.
Initial release. Revision to add subject field. Revision to add disclaimer. Added <ForwardedBy> optional tag as well as <OnBehalfOf> optional group. Added <Disclaimer> group. Marked for GA Added <AccountNumber>, <BloombergUUID> and <FirmNumber> optional tags as well as <SharedMessenger> optional group. Added <MsgLang> tag as well as <OrigSender> optional group. Redefined optional groups <OnBehalfOf> and <SharedMessenger> as an optional choice group within <Message>. Redefined optional group <Attachment> plus added tags <FileSize> and <Reference>. Added <Greeting> optional tag UTF-8 support
Version
0.1 0.2 0.3 0.4 1.0 1.1
Changes made by
Arun Kumar Arun Kumar Arun Kumar Hector M Olmeda Hector M Olmeda Hector M Olmeda
Comments
None Thanks to Kim for detecting the anomaly. Added disclaimer reference. Added additional tags to support LOGU and Forwarded changes. Added Disclaimer text tag and group. Made available to clients. Added additional tags to the UserInfo group for account number, firm number and UUID. Added additional tags to support SMSG. Added additional tag for message language as well as an optional group to support the original sender for the Message group. Changed some dependencies for other Message subgroups as well. Added tag for file size as well as another one for reference/web links under the Attachment group.
7.
1.2
Hector M Olmeda
8. 9.
1.3 1.4
Hector M Olmeda Hector M Olmeda
10.
Add <MsgTimeUTC> tag as well as optional <MsgType> and <NextFile> tags.

Add optional <FileId> tags. <ForwardedTo> and
1.5
Hector M Olmeda
Added glossary. Added additional optional tag to support MSG9 greeting text for the Message group Character set encoding has been changed from ISO-8859-1 and Shift-JIS to UTF-8. Appropriate translations are being performed on subject and body text. In addition to displaying the message creation time in EST, we now report it as UTC . Also, well optionally report specific message types.
11.
1.6
ForwardedTo will containt autofwding details for each Bloomberg recipient if enabled. FileId will be used for referencing the attachments in the .tar. September 14, 2009
Author:
MSG Daily Dump XML Format Section 1 Highlights 12

Added clarification on Reference type attachments not including any file data.
NY R&D Message Compliance Version: 1.6 Version 1.7 Changes made by Martijn Vels Comments
Author:
Hector M Olmeda Page 4 of 40 Date: DO NOT DISTRIBUTE WITHOUT PERMISSION
September 14, 2009
Author:
September 14, 2009
2 Dump Format 2.1 PLAIN-TEXT

2.1.1 2.1.1.1 Line 1 =====BEGIN MESSAGE===== =====BEGIN MESSAGE===== 2.1.2 2.1.2.1 Line 2 Message#: followed by the message count. This number is left justified and not padded with spaces.
Message: 10
2.1.3 2.1.3.1 2.1.3.2 2.1.3.3 2.1.3.4 Line 3 Message Sent: MM/DD/YYYY (Date the message was sent in UTC) A space hh:mm:ss (Time at which the message was sent in UTC)
Message sent: 8/04/2003 16:41:03

2.1.4 2.1.4.1 2.1.4.2 2.1.4.3 2.1.4.4 2.1.4.5 2.1.4.6 Line 4 From: Email Address | followed by full name (20 characters max) | followed by the account name (20 characters max) | followed by the firm number (this is blank if the firm number is unavailable) | followed by the account number (this number is blank if the account number is unavailable)
From: JDOE@bloomberg.net|JOHN DOE|TESTGROUP GLOBAL MAR|1234|123456

Author: Hector M Olmeda Page 6 of 40 Date: DO NOT DISTRIBUTE WITHOUT PERMISSION DI September 14, 2009
MSG Daily Dump XML Format Section 2 2.1.5 2.1.5.1 2.1.5.2 2.1.5.3 2.1.5.4 2.1.5.5 2.1.5.6 Line 5 Number of Recipients To: Email address | followed by full name (20 characters max) | followed by the account name (20 characters max)
| followed by the firm number (this is blank if the firm number is unavailable) | followed by the account number (this number is blank if the account number is unavailable)
To: JDOE@bloomberg.net|JOHN DOE|TESTGROUP GLOBAL MAR|1234|123456
2.1.6 2.1.6.1
Line 6/ Line number following the To: fields Subject:
Subject:
2.1.7 2.1.7.1
Line 7/ Subsequent line Body of the message
Game show network adds distributed media content.

2.1.8 2.1.8.1 Last line/ End of message =====End Message=====
=====End Message=====
Author:
September 14, 2009
2.2 XML FORMAT

Schema MsgXml.xsd
schema location: attribute form default: element form default: P:\AutoEx\MSG\Compliance\Format\MSG\v1.6\MsgXml.xsd qualified
Elements AccountName AccountNumber Attachment BloombergEmailAddress BloombergUUID ClientID1 ClientID2 CorporateEmailAddress Disclaimer DisclaimerReference DisclaimerText FileDump FileID FileName FileSize FirmNumber FirstName ForwardedBy ForwardedTo Greeting LastName Message MsgBody MsgID MsgLang MsgTime MsgTimeUTC MsgType NextFile OnBehalfOf OrigSender Recipient Reference Sender SharedMessenger Subject UserInfo Version
schema location: attribute form default: element form default: targetNamespace:
altova://ystream/xml.xsd
http://www.w3.org/XML/1998/namespace
Attributes base id lang space
Attr. groups specialAttrs
Author:
September 14, 2009
element AccountName
diagram
properties used by source
content mixed element
complex true UserInfo
<xs:element name="AccountName"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element AccountNumber
diagram
<xs:element name="AccountNumber"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element Attachment
diagram
properties children used by source
content
complex
FileName Reference FileID FileSize element Message
<xs:element name="Attachment"> <xs:complexType> <xs:sequence> <xs:choice> <xs:element ref="FileName"/> <xs:element ref="Reference"/> </xs:choice> <xs:element ref="FileID" minOccurs="0"/> <xs:element ref="FileSize" minOccurs="0"/> </xs:sequence> </xs:complexType>
Author:
September 14, 2009

</xs:element>
element BloombergEmailAddress
diagram
<xs:element name="BloombergEmailAddress"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element BloombergUUID
diagram
<xs:element name="BloombergUUID"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element ClientID1
diagram
<xs:element name="ClientID1"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element ClientID2
diagram
properties used by
Author:
September 14, 2009

source <xs:element name="ClientID2"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element CorporateEmailAddress
diagram
<xs:element name="CorporateEmailAddress"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element Disclaimer
diagram
content
complex
DisclaimerReference DisclaimerText element FileDump
<xs:element name="Disclaimer"> <xs:complexType> <xs:sequence> <xs:element ref="DisclaimerReference"/> <xs:element ref="DisclaimerText"/> </xs:sequence> </xs:complexType> </xs:element>
element DisclaimerReference
diagram
content complex mixed true elements Disclaimer Message <xs:element name="DisclaimerReference"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
Author:
September 14, 2009
MSG Daily Dump XML Format Section 2 element DisclaimerText

diagram
complex true Disclaimer
<xs:element name="DisclaimerText"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element FileDump
diagram
properties children source
content
complex
Version Message Disclaimer NextFile <xs:element name="FileDump"> <xs:complexType> <xs:sequence> <xs:element ref="Version"/> <xs:element ref="Message" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="Disclaimer" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="NextFile" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element>
element FileID
diagram
complex true Attachment
<xs:element name="FileID"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
Author:
September 14, 2009
MSG Daily Dump XML Format Section 2 element FileName

diagram
<xs:element name="FileName"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element FileSize
diagram
<xs:element name="FileSize"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element FirmNumber
diagram
<xs:element name="FirmNumber"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element FirstName
diagram
<xs:element name="FirstName"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/>
Author:
September 14, 2009

</xs:complexType> </xs:element>
element ForwardedBy
diagram
complex true Recipient
<xs:element name="ForwardedBy"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element ForwardedTo
diagram
content Recipient element
complex
Recipient
<xs:element name="ForwardedTo"> <xs:complexType> <xs:sequence> <xs:element ref="Recipient" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element>
element Greeting
diagram
complex true Message
<xs:element name="Greeting"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element LastName
diagram
Author:
September 14, 2009

properties used by source content mixed element complex true UserInfo
<xs:element name="LastName"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element Message
diagram
content
complex
MsgID MsgTime MsgTimeUTC MsgLang MsgType OnBehalfOf SharedMessenger OrigSender Sender Recipient Subject Attachment MsgBody DisclaimerReference Greeting element FileDump
<xs:element name="Message"> <xs:complexType> <xs:sequence> <xs:element ref="MsgID"/> <xs:element ref="MsgTime"/> <xs:element ref="MsgTimeUTC"/> <xs:element ref="MsgLang"/> <xs:element ref="MsgType" minOccurs="0"/>
Author:
September 14, 2009

<xs:choice minOccurs="0"> <xs:element ref="OnBehalfOf"/> <xs:element ref="SharedMessenger"/> </xs:choice> <xs:element ref="OrigSender" minOccurs="0"/> <xs:element ref="Sender"/> <xs:element ref="Recipient" maxOccurs="unbounded"/> <xs:element ref="Subject"/> <xs:element ref="Attachment" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="MsgBody"/> <xs:element ref="DisclaimerReference" minOccurs="0"/> <xs:element ref="Greeting" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element>
element MsgBody
diagram
<xs:element name="MsgBody"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element MsgID
diagram
<xs:element name="MsgID"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element MsgLang
diagram
<xs:element name="MsgLang"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType>
Author:
September 14, 2009

</xs:element>
element MsgTime
diagram
<xs:element name="MsgTime"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element MsgTimeUTC
diagram
<xs:element name="MsgTimeUTC"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element MsgType
diagram
<xs:element name="MsgType"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element NextFile
diagram
properties used by
complex true FileDump
Author:
September 14, 2009

source <xs:element name="NextFile"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element OnBehalfOf
diagram
content UserInfo element
complex
Message
<xs:element name="OnBehalfOf"> <xs:complexType> <xs:sequence> <xs:element ref="UserInfo"/> </xs:sequence> </xs:complexType> </xs:element>
element OrigSender
diagram
complex
Message
<xs:element name="OrigSender"> <xs:complexType> <xs:sequence> <xs:element ref="UserInfo"/> </xs:sequence> </xs:complexType> </xs:element>
element Recipient
diagram
properties children
content
complex
UserInfo ForwardedBy ForwardedTo
Author:
September 14, 2009

used by attributes source element Message Type xs:string Use Default
Name DeliveryType
Fixed
annotation
<xs:element name="Recipient"> <xs:complexType> <xs:sequence> <xs:element ref="UserInfo"/> <xs:element ref="ForwardedBy" minOccurs="0"/> <xs:element ref="ForwardedTo" minOccurs="0"/> </xs:sequence> <xs:attribute name="DeliveryType" type="xs:string" default=" "/> </xs:complexType> </xs:element>
attribute Recipient/@DeliveryType
type properties source xs:string isRef default 0
<xs:attribute name="DeliveryType" type="xs:string" default=" "/>
element Reference
diagram
<xs:element name="Reference"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element Sender
diagram
complex
Message
<xs:element name="Sender"> <xs:complexType> <xs:sequence> <xs:element ref="UserInfo"/> </xs:sequence> </xs:complexType> </xs:element>
Author:
September 14, 2009
MSG Daily Dump XML Format Section 2 element SharedMessenger

diagram
complex
Message
<xs:element name="SharedMessenger"> <xs:complexType> <xs:sequence> <xs:element ref="UserInfo"/> </xs:sequence> </xs:complexType> </xs:element>
element Subject
diagram
<xs:element name="Subject"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
element UserInfo
diagram
properties children
content
complex
FirstName LastName FirmNumber AccountName AccountNumber BloombergUUID BloombergEmailAddress
Author:
September 14, 2009

CorporateEmailAddress ClientID1 ClientID2 used by source elements
ForwardedTo OnBehalfOf OrigSender Recipient Sender SharedMessenger
<xs:element name="UserInfo"> <xs:complexType> <xs:sequence> <xs:element ref="FirstName"/> <xs:element ref="LastName"/> <xs:element ref="FirmNumber" minOccurs="0"/> <xs:element ref="AccountName"/> <xs:element ref="AccountNumber" minOccurs="0"/> <xs:element ref="BloombergUUID" minOccurs="0"/> <xs:element ref="BloombergEmailAddress"/> <xs:element ref="CorporateEmailAddress"/> <xs:element ref="ClientID1" minOccurs="0"/> <xs:element ref="ClientID2" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element>
element Version
diagram
complex true FileDump
<xs:element name="Version"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>
attribute base
namespace type used by annotation http://www.w3.org/XML/1998/namespace xs:anyURI attributeGroup specialAttrs
documentation See http://www.w3.org/TR/xmlbase/ for information about this attribute. <xs:attribute name="base" type="xs:anyURI"> <xs:annotation> <xs:documentation>See http://www.w3.org/TR/xmlbase/ for information about this attribute.</xs:documentation> </xs:annotation> </xs:attribute>
source
attribute id
namespace type annotation http://www.w3.org/XML/1998/namespace xs:ID documentation See http://www.w3.org/TR/xml-id/ for information about this attribute.
Author:
September 14, 2009

source <xs:attribute name="id" type="xs:ID"> <xs:annotation> <xs:documentation>See http://www.w3.org/TR/xml-id/ for information about this attribute.</xs:documentation> </xs:annotation> </xs:attribute>
attribute lang
namespace type used by annotation http://www.w3.org/XML/1998/namespace union of (xs:language, restriction of xs:string) attributeGroup specialAttrs
documentation Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/lang-tag-apps.htm for further information. The union allows for the 'un-declaration' of xml:lang with the empty string.
source
<xs:attribute name="lang"> <xs:annotation> <xs:documentation>Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/lang-tag-apps.htm for further information. The union allows for the 'un-declaration' of xml:lang with the empty string.</xs:documentation> </xs:annotation> <xs:simpleType> <xs:union memberTypes="xs:language"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value=""/> </xs:restriction> </xs:simpleType> </xs:union> </xs:simpleType> </xs:attribute>
attribute space
namespace type used by facets source http://www.w3.org/XML/1998/namespace restriction of xs:NCName attributeGroup enumeration enumeration specialAttrs default preserve
<xs:attribute name="space"> <xs:simpleType> <xs:restriction base="xs:NCName"> <xs:enumeration value="default"/> <xs:enumeration value="preserve"/> </xs:restriction> </xs:simpleType> </xs:attribute>
Author:
September 14, 2009
attributeGroup specialAttrs
namespace attributes http://www.w3.org/XML/1998/namespace Name base Type Use Default Fixed annotation documentation See http://www.w3.org/TR/xmlbase/ for information about this attribute. documentation Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/langtag-apps.htm for further information. The union allows for the 'undeclaration' of xml:lang with the empty string. space source <xs:attributeGroup name="specialAttrs"> <xs:attribute ref="xml:base"/> <xs:attribute ref="xml:lang"/> <xs:attribute ref="xml:space"/> </xs:attributeGroup>
lang
XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy
Author:
September 14, 2009
3 Appendix A 3.1 XSD FORMAT SPECIFICATION

<?xml version="1.0" encoding="UTF-8" standalone="no"?>  <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <xs:import namespace="http://www.w3.org/XML/1998/namespace"/> <xs:element name="FileDump"> <xs:complexType> <xs:sequence> <xs:element ref="Version"/> <xs:element ref="Message" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="Disclaimer" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="NextFile" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Message"> <xs:complexType> <xs:sequence> <xs:element ref="MsgID"/> <xs:element ref="MsgTime"/> <xs:element ref="MsgTimeUTC"/> <xs:element ref="MsgLang"/> <xs:element ref="MsgType" minOccurs="0"/> <xs:choice minOccurs="0"> <xs:element ref="OnBehalfOf"/> <xs:element ref="SharedMessenger"/> </xs:choice> <xs:element ref="OrigSender" minOccurs="0"/> <xs:element ref="Sender"/> <xs:element ref="Recipient" maxOccurs="unbounded"/> <xs:element ref="Subject"/> <xs:element ref="Attachment" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="MsgBody"/> <xs:element ref="DisclaimerReference" minOccurs="0"/> <xs:element ref="Greeting" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Disclaimer"> <xs:complexType> <xs:sequence> <xs:element ref="DisclaimerReference"/> <xs:element ref="DisclaimerText"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="UserInfo"> <xs:complexType> <xs:sequence> <xs:element ref="FirstName"/> <xs:element ref="LastName"/> <xs:element ref="FirmNumber" minOccurs="0"/> <xs:element ref="AccountName"/>
Author:
September 14, 2009
<xs:element ref="AccountNumber" minOccurs="0"/> <xs:element ref="BloombergUUID" minOccurs="0"/> <xs:element ref="BloombergEmailAddress"/> <xs:element ref="CorporateEmailAddress"/> <xs:element ref="ClientID1" minOccurs="0"/> <xs:element ref="ClientID2" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="OnBehalfOf"> <xs:complexType> <xs:sequence> <xs:element ref="UserInfo"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="OrigSender"> <xs:complexType> <xs:sequence> <xs:element ref="UserInfo"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Recipient"> <xs:complexType> <xs:sequence> <xs:element ref="UserInfo"/> <xs:element ref="ForwardedBy" minOccurs="0"/> <xs:element ref="ForwardedTo" minOccurs="0"/> </xs:sequence> <xs:attribute name="DeliveryType" type="xs:string" default=" "/> </xs:complexType> </xs:element> <xs:element name="Sender"> <xs:complexType> <xs:sequence> <xs:element ref="UserInfo"/> </xs:sequence> <xs:attribute name="DeviceType" type="xs:string" default=" "/> </xs:complexType> </xs:element> <xs:element name="SharedMessenger"> <xs:complexType> <xs:sequence> <xs:element ref="UserInfo"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="ForwardedTo"> <xs:complexType> <xs:sequence> <xs:element ref="Recipient" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Attachment"> <xs:complexType> <xs:sequence> <xs:choice> <xs:element ref="FileName"/> <xs:element ref="Reference"/> </xs:choice> <xs:element ref="FileID" minOccurs="0"/>
Author:
September 14, 2009
<xs:element ref="FileSize" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="AccountName"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element> <xs:element name="AccountNumber"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element> <xs:element name="BloombergEmailAddress"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element> <xs:element name="BloombergUUID"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element> <xs:element name="ClientID1"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element> <xs:element name="ClientID2"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element> <xs:element name="CorporateEmailAddress"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element> <xs:element name="DisclaimerReference"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element> <xs:element name="DisclaimerText"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element> <xs:element name="FileID"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element> <xs:element name="FileName"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element> <xs:element name="FileSize"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType>
Author:
September 14, 2009

</xs:element> <xs:element name="FirmNumber"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" </xs:complexType> </xs:element> <xs:element name="FirstName"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" </xs:complexType> </xs:element> <xs:element name="ForwardedBy"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" </xs:complexType> </xs:element> <xs:element name="Greeting"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" </xs:complexType> </xs:element> <xs:element name="LastName"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" </xs:complexType> </xs:element> <xs:element name="MsgBody"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" </xs:complexType> </xs:element> <xs:element name="MsgID"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" </xs:complexType> </xs:element> <xs:element name="MsgLang"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" </xs:complexType> </xs:element> <xs:element name="MsgTime"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" </xs:complexType> </xs:element> <xs:element name="MsgTimeUTC"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" </xs:complexType> </xs:element> <xs:element name="MsgType"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" </xs:complexType> </xs:element> <xs:element name="NextFile"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" </xs:complexType> </xs:element> <xs:element name="Reference"> <xs:complexType mixed="true">
maxOccurs="unbounded"/>
Author:
September 14, 2009
<xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element> <xs:element name="Subject"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element> <xs:element name="Version"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element> </xs:schema>
3.2 SAMPLE XML FILE

<?xml version="1.0" encoding="UTF-8"?> <FileDump> <Version>MSGXML 1.6</Version> <Message> <MsgID>558195618</MsgID> <MsgTime>2008-03-11-00.00.07.000000</MsgTime> <MsgTimeUTC>1205208007</MsgTimeUTC> <MsgLang>English</MsgLang> <Sender> <UserInfo> <FirstName>DAVID</FirstName> <LastName>HOUSEMANN</LastName> <AccountName>GLOBAL CITY MARKETS</AccountName> <BloombergEmailAddress>DHOUSEMANN@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress></CorporateEmailAddress> </UserInfo> </Sender> <Recipient DeliveryType = " "> <UserInfo> <FirstName>JULIAN</FirstName> <LastName>MAYORAL</LastName> <FirmNumber>222555</FirmNumber> <AccountName>ATR FUND MANAGEMENT</AccountName> <AccountNumber>553311</AccountNumber> <BloombergUUID>99775533</BloombergUUID> <BloombergEmailAddress>JMAYORAL@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress></CorporateEmailAddress> </UserInfo> </Recipient> <Recipient DeliveryType = " "> <UserInfo> <FirstName>WHITNEY</FirstName> <LastName>FUNK</LastName> <FirmNumber>222555</FirmNumber> <AccountName>ATR FUND MANAGEMENT</AccountName> <AccountNumber>553311</AccountNumber> <BloombergUUID>99775522</BloombergUUID> <BloombergEmailAddress>WFUNK@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress></CorporateEmailAddress> </UserInfo> </Recipient> <Subject> jdsu 77.25-77.75 v 1.55 </Subject>
Author:
September 14, 2009
<MsgBody> jdsu 77.25-77.75 v 1.55 </MsgBody> <Greeting>Looking for >8% yield</Greeting> </Message> <Message> <MsgID>1594419787</MsgID> <MsgTime>2008-03-11-08.09.57.000000</MsgTime> <MsgTimeUTC>1205237397</MsgTimeUTC> <MsgLang>English</MsgLang> <OrigSender> <UserInfo> <FirstName>WHITNEY</FirstName> <LastName>FUNK</LastName> <FirmNumber>222555</FirmNumber> <AccountName>ATR FUND MANAGEMENT</AccountName> <AccountNumber>553311</AccountNumber> <BloombergUUID>99775522</BloombergUUID> <BloombergEmailAddress>WFUNK@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress></CorporateEmailAddress> </UserInfo> </OrigSender> <Sender> <UserInfo> <FirstName>JULIAN</FirstName> <LastName>MAYORAL</LastName> <FirmNumber>222555</FirmNumber> <AccountName>ATR FUND MANAGEMENT</AccountName> <AccountNumber>553311</AccountNumber> <BloombergUUID>99775533</BloombergUUID> <BloombergEmailAddress>JMAYORAL@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress></CorporateEmailAddress> </UserInfo> </Sender> <Recipient DeliveryType = " "> <UserInfo> <FirstName>GUS</FirstName> <LastName>MIKONOS</LastName> <AccountName>XYZ CAPITAL MARKETS</AccountName> <BloombergEmailAddress>CMIKONOS@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress></CorporateEmailAddress> </UserInfo> </Recipient> <Subject> BUYER </Subject> <MsgBody> STONE CONTAINER SSCC 7 1/4 95__2MM </MsgBody> </Message> <Message> <MsgID>3452656403</MsgID> <MsgTime>2008-03-11-08.10.32.000000</MsgTime> <MsgTimeUTC>1205237432</MsgTimeUTC> <MsgLang>English</MsgLang> <Sender> <UserInfo> <FirstName>SANTORO</FirstName> <LastName>ADEMA</LastName> <AccountName>GLOBAL CITY MARKETS</AccountName> <BloombergEmailAddress>SADEMA@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress></CorporateEmailAddress> </UserInfo>
Author:
September 14, 2009
</Sender> <Recipient DeliveryType = " "> <UserInfo> <FirstName>JULIAN</FirstName> <LastName>MAYORAL</LastName> <FirmNumber>222555</FirmNumber> <AccountName>ATR FUND MANAGEMENT</AccountName> <AccountNumber>553311</AccountNumber> <BloombergUUID>99775533</BloombergUUID> <BloombergEmailAddress>JMAYORAL@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress></CorporateEmailAddress> </UserInfo> <ForwardedTo> <Recipient> <UserInfo> <FirstName>JOE</FirstName> <LastName>YANOV</LastName> <AccountName>GLOBAL SYNC FUND</AccountName> <BloombergEmailAddress>JYANOV@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress></CorporateEmailAddress> </UserInfo> <ForwardedBy>"Julian Mayoral ATR FUND"</ForwardedBy> </Recipient> </ForwardedTo> </Recipient> <Recipient DeliveryType = " "> <UserInfo> <FirstName>BERNIE</FirstName> <LastName>PARKAY</LastName> <FirmNumber>222555</FirmNumber> <AccountName>ATR FUND MANAGEMENT</AccountName> <AccountNumber>553311</AccountNumber> <BloombergUUID>99775511</BloombergUUID> <BloombergEmailAddress>BPARKAY@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress>bparkay@atrfund.com</CorporateEmailAddress> </UserInfo> </Recipient> <Recipient DeliveryType = " "> <UserInfo> <FirstName>WHITNEY</FirstName> <LastName>FUNK</LastName> <FirmNumber>222555</FirmNumber> <AccountName>ATR FUND MANAGEMENT</AccountName> <AccountNumber>553311</AccountNumber> <BloombergUUID>99775522</BloombergUUID> <BloombergEmailAddress>WFUNK@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress></CorporateEmailAddress> </UserInfo> </Recipient> <Subject> Fwd: **Correlation Color 8/17** </Subject> <MsgBody> slow day in correlation space. In 5y, after a very volatile day yesterday, equity seemed be very stable, trading wider only __pt, leaving it wrapped44pts. Little activity in 3-7% and 7-10%, however, prints on thesewere tighter (3-7: 148, 147, 7-10: 42, 41__). In 10y, 3-7% traded upthe second straight day to 650, and saw the first flurry of activity in atime on 15-30%, ended up the day wrapped around 35. In general, saw a lotactivity earlier in the week up and down the capital structure in different, and saw the market become a little firmer with more size going through.everyone enjoys their weekend. </MsgBody> </Message>
Author:
September 14, 2009
<Message> <MsgID>3463244760</MsgID> <MsgTime>2008-03-11-08.11.00.000000</MsgTime> <MsgTimeUTC>1205237460</MsgTimeUTC> <MsgLang>English</MsgLang> <OnBehalfOf> <UserInfo> <FirstName>QUENTIN</FirstName> <LastName>KNAPP</LastName> <AccountName>WHATEVER SECURITIES</AccountName> <BloombergEmailAddress>QKNAPP@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress></CorporateEmailAddress> </UserInfo> </OnBehalfOf> <Sender DeviceType="M"> <UserInfo> <FirstName>LINDA</FirstName> <LastName>TOMMY</LastName> <AccountName>WHATEVER SECURITIES</AccountName> <BloombergEmailAddress>LTOMMY@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress></CorporateEmailAddress> </UserInfo> </Sender> <Recipient DeliveryType = " "> <UserInfo> <FirstName>MARIKO</FirstName> <LastName>NIKATA</LastName> <FirmNumber>222555</FirmNumber> <AccountName>ATR FUND MANAGEMENT</AccountName> <AccountNumber>553311</AccountNumber> <BloombergUUID>99775544</BloombergUUID> <BloombergEmailAddress>MNIKATA@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress>mnikata@atrfund.com</CorporateEmailAddress> </UserInfo> </Recipient> <Recipient DeliveryType = " "> <UserInfo> <FirstName>CHARLES</FirstName> <LastName>PFIZAR</LastName> <FirmNumber>222555</FirmNumber> <AccountName>ATR FUND MANAGEMENT</AccountName> <AccountNumber>553311</AccountNumber> <BloombergUUID>99775555</BloombergUUID> <BloombergEmailAddress>CPFIZAR@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress>cpfizar@atrfund.com</CorporateEmailAddress> </UserInfo> </Recipient> <Recipient DeliveryType = " "> <UserInfo> <FirstName>TAKA</FirstName> <LastName>KASSAM</LastName> <FirmNumber>222555</FirmNumber> <AccountName>ATR FUND MANAGEMENT</AccountName> <AccountNumber>553311</AccountNumber> <BloombergUUID>99775566</BloombergUUID> <BloombergEmailAddress>TKASSAM@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress>tkassam@atrfund.com</CorporateEmailAddress> </UserInfo> </Recipient> <Recipient DeliveryType = " "> <UserInfo> <FirstName>BERNIE</FirstName> <LastName>PARKAY</LastName>
Author:
September 14, 2009
<FirmNumber>222555</FirmNumber> <AccountName>ATR FUND MANAGEMENT</AccountName> <AccountNumber>553311</AccountNumber> <BloombergUUID>99775511</BloombergUUID> <BloombergEmailAddress>BPARKAY@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress>bparkay@atrfund.com</CorporateEmailAddress> </UserInfo> </Recipient> <Subject> Fwd: WEEKLY RECAP: MACRO DRIVES THE MICRO </Subject> <MsgBody> STATS:+1.85% TPX +2.03% S&P +1.45% NASDAQ +1.29%+9.2% (ALL TIME HIGH) $/?LAT _/?1.3% _/$ +1.3% BEST:MINERS +6.02%, IRON & STEEL +4.4%, WAREHOUSE +3.76%WORST:AIR TRANSPORTS 7BPS, UTILITIES +48BPS, RUBBER PRODUCTS +50BPS *Japan and the U.S HIGHER for 6 days in a row led by RESOURCES and CYCLICALS.the second week in a row, Japanese Banks were in focus(tho' a bit upstagedmaterials) as the sector received two UPGRADES from competitors and onespecific(MIZUHO 8411) DOWNGRADE from a third. For the week, Banks close +2.10% and the chart suggests momentum is to the UPSIDE {TPNBNK Index GPO<go>} *Macro proved MIXED with Weaker Than Expected(WTE) data being largely ignoredBetter than Expected(BTE) data was what was paid attention too.(A sign ofpsychology) Japanese GDP and IP both WTE but DEFLATOR & MACHINE ORDERS. US PPI & CPI show inflation TAME.(but a May number when Crude was -7.5%)MFG and IP BTE but PHILLY FED WTE. DOE data showed a big DRAW in Crude(Crude BULLISH) giving RISE to energy shares globally. N.A.Semi B to B.85 vs .81 for Apr and at 2005 HIGHS continues to show IMPROVEMENT. LastlyIP and FIXED ASSET INVESTMENT both BTE and both played a BIG role in this's RALLY in Resources, Cyclicals and Commodities. *The Macro drives the Micro, putting a bid in stocks globally with "Tech Heavy"at 13 month HIGHS, "Old" Europe hitting 3 year HIGHS, and "Resource Rich" Australia capturing ALL TIME HIGHS! Resources(ie. Oil & Miners) OUTPERFORM ondata. Cyclicals(Steels, Chems) OUTPERFORM despite sensitivity to HIGHERcosts. SHIN ETSU(4063)+3.3%, DOW +4%, JFE(5411)+5.2%, X+8%, ARCELOR(LOR FP)+6.6%. China and US I.P. UNDERPIN commodities. Copper(+16.7% since 5/23)with an ALL TIME HIGH. Aluminum +1.5% for the week too. Reflecting thein Cyclicals, Chemicals and Commodities has been US Homebuilders.+28% YTD and TOLL BROS(TOL)+53% YTD. All of the above may give the Fed cause to keep RAISING rates longer than expected reported last week about gold and its apparent decoupling from thewith the $.(INVERSELY related) As you will note from the ed, the $ has COOLED vs the _ but Gold $438.70 continues to trade{GOLDS Comdty GPO<GO>}There are a few POSSIBLE reasons for this. Tradersbe BEARISH on prospects for the _ and concerned about the health of $ somove it to Gold. Another plausible reason could be that on the back of its decision to FORGIVE $40B in debt to 18 African nations,the G8 has DROPPED to sell Gold held by the IMF. Instead, the G8 has said the IMF has enoughto fund debt owed to it without the need to make sales (BN) </MsgBody> <Greeting> Ask me about Copper </Greeting> </Message> <Message> <MsgID>3204072625</MsgID> <MsgTime>2008-03-11-08.11.31.000000</MsgTime> <MsgTimeUTC>1205237491</MsgTimeUTC> <MsgLang>English</MsgLang> <Sender> <UserInfo>
Author:
September 14, 2009
<FirstName>BRANDON</FirstName> <LastName>SMYTHE</LastName> <AccountName>ACME FINANCIAL PRODU</AccountName> <BloombergEmailAddress>BSMYTHE@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress></CorporateEmailAddress> </UserInfo> </Sender> <Recipient DeliveryType = " "> <UserInfo> <FirstName>JULIAN</FirstName> <LastName>MAYORAL</LastName> <FirmNumber>222555</FirmNumber> <AccountName>ATR FUND MANAGEMENT</AccountName> <AccountNumber>553311</AccountNumber> <BloombergUUID>99775533</BloombergUUID> <BloombergEmailAddress>JMAYORAL@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress></CorporateEmailAddress> </UserInfo> </Recipient> <Recipient DeliveryType = " "> <UserInfo> <FirstName>BERNIE</FirstName> <LastName>PARKAY</LastName> <FirmNumber>222555</FirmNumber> <AccountName>ATR FUND MANAGEMENT</AccountName> <AccountNumber>553311</AccountNumber> <BloombergUUID>99775511</BloombergUUID> <BloombergEmailAddress>BPARKAY@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress>bparkay@atrfund.com</CorporateEmailAddress> </UserInfo> </Recipient> <Subject> DVN 0% LOCKED LOCKED v 49.35, 57.45 locked! </Subject> <MsgBody> DVN 0% LOCKED LOCKED v 49.35, 57.45 locked! </MsgBody> </Message> <Message> <MsgID>2453686440</MsgID> <MsgTime>2008-03-11-08.17.20.000000</MsgTime> <MsgTimeUTC>1205237840</MsgTimeUTC> <MsgLang>English</MsgLang> <Sender> <UserInfo> <FirstName>YELENA</FirstName> <LastName>MILLS</LastName> <AccountName>BLUES BROTHERS, INC</AccountName> <BloombergEmailAddress>YMILLS@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress></CorporateEmailAddress> </UserInfo> </Sender> <Recipient DeliveryType = " "> <UserInfo> <FirstName>CHARLES</FirstName> <LastName>PFIZAR</LastName> <FirmNumber>222555</FirmNumber> <AccountName>ATR FUND MANAGEMENT</AccountName> <AccountNumber>553311</AccountNumber> <BloombergUUID>99775555</BloombergUUID> <BloombergEmailAddress>CPFIZAR@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress>cpfizar@atrfund.com</CorporateEmailAddress> </UserInfo>
Author:
September 14, 2009
</Recipient> <Subject> GDT/JNJ 2.85 unwinder 100K </Subject> <MsgBody> GDT/JNJ 2.85 unwinder 100K </MsgBody> <Greeting> EUR/JPY Swaps are HOT!!! </Greeting> </Message> <Message> <MsgID>2716215466</MsgID> <MsgTime>2008-03-11-08.18.17.000000</MsgTime> <MsgTimeUTC>1205237897</MsgTimeUTC> <MsgLang>English</MsgLang> <Sender> <UserInfo> <FirstName>CHARLES</FirstName> <LastName>PFIZAR</LastName> <FirmNumber>222555</FirmNumber> <AccountName>ATR FUND MANAGEMENT</AccountName> <AccountNumber>553311</AccountNumber> <BloombergUUID>99775555</BloombergUUID> <BloombergEmailAddress>CPFIZAR@bloomberg.net</BloombergEmailAddress> <CorporateEmailAddress>cpfizar@atrfund.com</CorporateEmailAddress> </UserInfo> </Sender> <Recipient DeliveryType = " "> <UserInfo> <FirstName></FirstName> <LastName>Roger Bandido</LastName> <AccountName></AccountName> <BloombergEmailAddress></BloombergEmailAddress> <CorporateEmailAddress>rbandido@yahoo.com</CorporateEmailAddress> </UserInfo> </Recipient> <Subject> ***GYI 159__-160 VS 74.10... </Subject> <Attachment> <FileName>tradequotes.txt</FileName> <FileID>1234567890ABC45678901234.txt</FileID> <FileSize>2590</FileSize> </Attachment> <MsgBody> ***GYI 159__-160 VS 74.10... </MsgBody> <DisclaimerReference>999999</DisclaimerReference> </Message> </FileDump>
Author:
September 14, 2009
4 Glossary
<Account Name> Data element that represents a given users Bloomberg account name which comes from the user setup information. Is blank if given user is not associated to a Bloomberg account. Member of the UserInfo group definition. Data element that represents a given users Bloomberg account number which comes from the user setup information. Tag and data are present if given user has a Bloomberg account and certain business rules have been satisfied. Member of the UserInfo group definition. Group element that defines the characteristics of a given attachment that was included in one or more Message groups. This element can represent either a file (Word document, Excel spreadsheet, PDF document, etc.) or reference to a Bloomberg internal document (news story, web link, etc.). If the attachment defines a file, the actual file data is provided in the attachment archive accompanying the xml data. If the attachment defines a reference, no actual file data is included, only the value of the reference (link to function, News story) is provided. Member of the Message group definition. Data element that represents a given users Bloomberg email address (bloomberg.net) which comes from the user setup information. Is blank if given user is not associated to a Bloomberg account. Member of the UserInfo group definition. Data element that represents a given users Bloomberg unique user identifier which comes from the user setup information. Present if given user has a Bloomberg account and certain business rules have been satisfied. Member of the UserInfo group definition. Data element that represents a given users firm-specific identifier which comes from user information provided by the users firm. Tag and data are present if the data is not blank and certain business rules have been satisfied. Member of the UserInfo group definition. Data element that represents a given users firm-specific identifier which comes from user information provided by the users firm. Tag and data are present if the data is not blank and certain business rules have been satisfied. Member of the UserInfo group definition. Data element that represents a given users firm-specific email address which comes from the user setup information. Data is always present if given user does not have a Bloomberg account. Member of the UserInfo group definition. September 14, 2009
<Account Number>
<Attachment>
<BloombergEmailAddress>
<BloombergUUID>
<ClientID1>
<ClientID2>
<CorporateEmailAddress>
Author:
Author:
September 14, 2009
<Disclaimer>
Group element that utilizes multiple data elements to represent a given disclaimer notice. There can be no instances of this group within a file or many. Member of the FileDump group definition. Data element that represents a given firm or account disclaimer reference number which was used within a given Message group. It can also be used as a data element within a given Disclaimer group in order to cross-reference to the actual disclaimer text. Member of the Disclaimer and Message group definitions. Data element that represents a given firm or account disclaimer text that was referenced (using the DisclaimerReference data element) by one or more Message groups. Member of the Disclaimer group definition. Root group element that includes the Version data element as well as zero to many Message or Disclaimer group elements.
<DisclaimerReference>
<DisclaimerText>
<FileDump>
<FileID>
Data element that represents the id of a file that will be used in the attachment tar provided with the dump. This id will always be present when filename and filesize are present. Member of the Attachment group definition.
<FileName>
Data element that represents the name of a file that was included in a given message. There is only one instance of this data element whenever its present. However, it cannot be present if the Reference data element already exists. Member of the Attachment group definition.
<FileSize>
Data element that represents the size in bytes of a file that was included in a given message. Tag and data will only appear if there is a valid FileName and the actual size is known. Member of the Attachment group definition. Data element that represents a given users Bloomberg firm number which comes from the user setup information. Present if given user has a Bloomberg account and certain business rules have been satisfied. Member of the UserInfo group definition. Data element that represents a given users first name which comes from the user setup information. Is blank if given user is not associated to a Bloomberg account. Member of the UserInfo group definition. Hector M Olmeda Page 37 of 40 Date: DO NOT DISTRIBUTE WITHOUT PERMISSION DI September 14, 2009
<FirmNumber>
<FirstName>
Author:
<ForwardedBy>
Data element that represents the user name who implicitly forwarded a given messages recipient. Member of the Recipient group definition.
<ForwardedTo>
Data element that represents the list of additional recipients this recipient was set to autofwd to. Member of the Recipient group definition.
<Greeting>
Data element that represents the senders MSG9 greeting text that was in place when the message was sent. Member of the Message group definition. Data element that represents a given users last name which comes from the user setup information. Always non-blank whether given user is associated to a Bloomberg account or not. Member of the UserInfo group definition.
<LastName>
<Message>
Group element that utilizes multiple data and group elements to represent a given message. There can be no instances of this group within a file or many. Member of the FileDump group definition. Data element that represents the actual body text for a given message. Member of the Message group definition. Data element that represents the Bloomberg-specific message identifier for a given message. Member of the Message group definition. Data element that represents the language setting or Bloomberg-specific font code page used when composing a given message. Member of the Message group definition. Data element that represents the date and time of when a given message was initially composed and sent. The data is presented from the Eastern Standard Time (EST) zone or Eastern Daylight Savings Time (EDT) zone perspective based on whether Daylight Savings Time is in effect according to US rules. Member of the Message group definition. Data element that represents the date and time of when a given message was initially composed and sent. The data is presented from the Coordinated Universal Time (UTC) perspective. September 14, 2009
<MsgBody>
<MsgID>
<MsgLang>
<MsgTime>
<MsgTimeUTC>
Author:
MSG Daily Dump XML Format Section 3 Member of the Message group definition. <MsgType>
Data element that represents which type category a given message belongs to. Only CHAT, TMSG and VMSG messages will contain this tag. Member of the Message group definition. Data element that represents the name of the file that is to be read or processed next in this report series. The data will only appear if there is another file. Member of the FileDump group definition. Group element that utilizes the UserInfo group to represent the user whose credentials were used to send a given message. There is only one instance of this group whenever its present. However, it cannot be present if the SharedMessenger group already exists. Member of the Message group definition.
<NextFile>
<OnBehalfOf>
Author:
September 14, 2009
<OrigSender>
Group element that utilizes the UserInfo group to represent the user who originated the message that was sent. There is only one instance of this group whenever its present. Member of the Message group definition. Group element that utilizes the UserInfo group to represent the user who is to receive a given message. It also utilizes the ForwardedBy data element. There is at least one instance of this group for each message sent but there can be many. Member of the Message group definition. Data element that represents a Bloomberg-specific reference to a document or web link that was included in a given message. Member of the Attachment group definition. Group element that utilizes the UserInfo group to represent the user who initiated and sent a given message. There is only one instance of this group for each message sent. Member of the Message group definition. Group element that utilizes the UserInfo group to represent the user who actually sent a given message as part of a Bloomberg-specific shared message group. There is only one instance of this group whenever its present. However, it cannot be present if the OnBehalfOf group already exists. Member of the Message group definition. Data element that represents the subject line for a given message. Member of the Message group definition. Group element that is used by other group elements to describe user specific data elements such as FirstName, LastName and CorporateEmailAdress to name a few. Data element that represents the version of the schema definition used to produce a given file. Member of the FileDump group definition.
<Recipient>
<Reference>
<Sender>
<SharedMessenger>
<Subject>
<UserInfo>
<Version>
Author:
September 14, 2009

Message Compliance Dump Format - 1.6

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Message Compliance Dump Format - 1.6

Hochgeladen von

Copyright:

Verfügbare Formate

Bloomberg LP

September 14, 2009

MSG Daily Dump XML Format Section 1 1

NY R&D Message Compliance Version: 1.6

Hector M Olmeda Page 2 of 40 Date: DO NOT DISTRIBUTE WITHOUT PERMISSION DI

September 14, 2009

MSG Daily Dump XML Format Section 1

NY R&D Message Compliance Version: 1.6

1 General Information 1.1 BUSINESS OBJECTIVE

1.2 FEATURE DEFINITION

1.3 REVISION HISTORY

Hector M Olmeda Hector M Olmeda

Add <MsgTimeUTC> tag as well as optional <MsgType> and <NextFile> tags.

Hector M Olmeda Page 3 of 40 Date: DO NOT DISTRIBUTE WITHOUT PERMISSION DI

MSG Daily Dump XML Format Section 1 Highlights 12

Hector M Olmeda Page 4 of 40 Date: DO NOT DISTRIBUTE WITHOUT PERMISSION

September 14, 2009

MSG Daily Dump XML Format Section 2

NY R&D Message Compliance Version: 1.6

Hector M Olmeda Page 5 of 40 Date: DO NOT DISTRIBUTE WITHOUT PERMISSION DI

September 14, 2009

MSG Daily Dump XML Format Section 2

NY R&D Message Compliance Version: 1.6

2 Dump Format 2.1 PLAIN-TEXT

Message sent: 8/04/2003 16:41:03

From: JDOE@bloomberg.net|JOHN DOE|TESTGROUP GLOBAL MAR|1234|123456

NY R&D Message Compliance Version: 1.6

To: JDOE@bloomberg.net|JOHN DOE|TESTGROUP GLOBAL MAR|1234|123456

Line 6/ Line number following the To: fields Subject:

Line 7/ Subsequent line Body of the message

Game show network adds distributed media content.

Hector M Olmeda Page 7 of 40 Date: DO NOT DISTRIBUTE WITHOUT PERMISSION DI

September 14, 2009

MSG Daily Dump XML Format Section 2

NY R&D Message Compliance Version: 1.6

2.2 XML FORMAT

schema location: attribute form default: element form default: targetNamespace:

Attributes base id lang space

Attr. groups specialAttrs

Hector M Olmeda Page 8 of 40 Date: DO NOT DISTRIBUTE WITHOUT PERMISSION DI

September 14, 2009

MSG Daily Dump XML Format Section 2

NY R&D Message Compliance Version: 1.6

properties used by source

content mixed element

complex true UserInfo

<xs:element name="AccountName"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>

properties used by source

content mixed element

complex true UserInfo

<xs:element name="AccountNumber"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>

properties children used by source

FileName Reference FileID FileSize element Message

Hector M Olmeda Page 9 of 40 Date: DO NOT DISTRIBUTE WITHOUT PERMISSION DI

September 14, 2009

MSG Daily Dump XML Format Section 2

NY R&D Message Compliance Version: 1.6

properties used by source

content mixed element

complex true UserInfo

<xs:element name="BloombergEmailAddress"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"/> </xs:complexType> </xs:element>