RosterUpdates is the root tag for a batch of roster updates. A roster update gives a publisher the ability to communicate changes to the groups of people playing various roles on its behalf in the investment research marketplace. The common case would be a financial services firm updating its roster of research analysts with aggregator partners. ComplexType for RosterUpdates This is to facilitate the unique identification of a particular batch of roster updates. Enables a consumer of this information to keep track of which batches have been applied to its database and which are duplicates. We recommend UUIDs to ensure uniqueness. This marks the date/time at which this batch of roster updates was formed. It is expressed using ISO 8601 as refined by the World Wide Web Consortium's note http://www.w3.org/TR/NOTE-datetime. In addition, RIXML requires the use of UTC (GMT +/- n hours:minute:seconds). All times are absolute and easier to compute, rather than using a relative (i.e. 08:30 +5) time. Indicates the language of the instance document -- i.e. the language of the publisher-supplied tag values contained in the XML file for this roster item. Described using the ISO 639-2/T Code. A roster update gives a publisher the ability to communicate changes to the groups of people playing various roles on its behalf in the investment research marketplace. The common case would be a financial services firm updating its roster of research analysts with aggregator partners. ComplexType for RosterUpdate For publishingActionType attribute, use: Published=Add, Revised=Update, Deleted=Delete. This is to facilitate the unique identification of a particular individual roster update. Enables a consumer of this information to keep track of which updates have been applied to its database and which are duplicates. We recommend UUIDs to ensure uniqueness. Areas of expertise associated with an organization that publishes research. ComplexType for OrganizationExpertise