Not for distribution unless authorized by RIXML.org
RIXML.org Limited ("RIXML") is a UK incorporated company. Site content is provided solely by RIXML and is not representative of the views of any one shareholder. Unless otherwise stated RIXML is solely responsible for site content. Terms and conditions of use are published on the web site at www.rixml.org. Copyright 2000, 2001, 2002. All rights reserved.-->
<xsd:documentation>Product refers to a unique "research idea", as opposed to an actual research publication. It is possible to publish multiple documents or other files (called "resources") with the same productID, provided they all refer to the same discrete research idea. Examples of a product include a research note, research report, conference call webcast, and morning meeting compilation. Examples of multiple resources published with the same productID are (1) a document published in English, with exact translations in German, French, and Japanese, (2) an audio file of a presentation and the transcript of the publication or (3) a single report that consists of a PDF and an Excel file.</xsd:documentation>
<xsd:documentation>This is to facilitate the unique identification of a particular product. To ensure uniqueness it is recommended that a Universal Unique IDentifier (UUID) be used as the productID. UUIDs can be generated on any computer, regardless of platform or operating system. A UUID is a 128-bit (16-byte) integer that is virtually guaranteed to be unique in the world across space and time. The Open Software Foundation (OSF) created UUIDs, as part of their Distributed Computing Environment (DCE).</xsd:documentation>
<xsd:documentation>A cue from the publisher that this product is really about an event, so that a hypothetical downstream parsing process might proceed more effectively and efficiently. </xsd:documentation>
<xsd:documentation>Used to indicate any meaningful ordering of the Products contained in this Research item. Particularly useful in publishing compendium products made up of multiple sub-products. Ordering is ascending. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="RelatedProduct">
<xsd:annotation>
<xsd:documentation>Describes how content contained in this product is associated with other products, or how content in other products is associated with this one. Can have none or any number of relationships to other products. </xsd:documentation>
<xsd:documentation>The unique productID of the product to which this product is related (as stored in Product.productID of the related document)</xsd:documentation>
<xsd:documentation>This is to facilitate the unique identification of a particular bundling of products. This is added with some forward thought to hypothetical research distribution systems that may wish to label and refer to result sets.
To ensure uniqueness it is recommended that a Universal Unique IDentifier (UUID) be used as the productID. UUIDs can be generated on any computer, regardless of platform or operating system. A UUID is a 128-bit (16-byte) integer that is virtually guaranteed to be unique in the world across space and time. The Open Software Foundation (OSF) created UUIDs, as part of their Distributed Computing Environment (DCE).</xsd:documentation>
<xsd:documentation>This marks the date/time at which this research bundle 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 Zulu time or Z-time (GMT +/- n hours:minute:seconds). All times are absolute and easier to compute, rather than using a relative (i.e. 08:30 +5) time. </xsd:documentation>
<xsd:documentation>Indicates the language of the RIXML document -- i.e. the language of the publisher-supplied tag values contained in the RIXML-based XML file for this research item. Described using the ISO 639-2/T Code. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<!--Elements for Package 2-ContactInfoPackage-->
<xsd:element name="Address">
<xsd:annotation>
<xsd:documentation>Strongly Recommended. Describes the street address.</xsd:documentation>
<xsd:documentation>A brief description of the contact information can be included here, if desired. This element is intended to pick up where the purpose attribute leaves off. It offers the ability to provide more detail. </xsd:documentation>
<xsd:documentation>Describes the intended purpose of the contact information. Gives the reader an idea of what to expect on the far side. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<!--Elements for Package 1-SourcePackage-->
<xsd:element name="Source">
<xsd:annotation>
<xsd:documentation>The top-level element of the Source section. Used to specify the organization(s) from which this research item originated. Organizations given here are defined as publishers. </xsd:documentation>
<xsd:documentation>The PersonGroup element is used to hold the name(s) of the individual person(s) and/or the name of the group. In the case of an individual person, the person tag and its associated personID are used (no personGroupID or description is needed). PersonGroups can be formally organized groups or they can be fluid groups that come together to deliver content. If the "group" consists of only one person, there is no need to define a group ID and description; it is sufficient to have the 'person' tag and the associated personID under the 'group' tag.</xsd:documentation>
<xsd:documentation>Indicates the name of the group. This is not required, but can be used where groups are formally named or if there is a name created for the group involved with a publication or event. </xsd:documentation>
<xsd:documentation>If the role attribute has the value PublisherDefined, this element is used to hold the publisher's own description of the role. </xsd:documentation>
<xsd:documentation>If there are multiple PersonGroups, and they should appear in a certain order when the content is published, indicate the desired order by associating an appropriate sequence number to each one. </xsd:documentation>
<xsd:documentation>The role of the group relative to this research item. This is especially useful if only the group is specified without any members or if all members share the same role -- as in a group of document authors or meeting attendees. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="PersonGroupMember">
<xsd:annotation>
<xsd:documentation>Used to define the members of a group, for example, the author(s) of the product. The PersonGroupMember highlights primary persons, and describes the display order of multiple persons. </xsd:documentation>
<xsd:documentation>If there are multiple PersonGroupMembers, and they should appear in a certain order when the content is published, indicate the desired order by associating the appropriate sequence number to each PersonGroupMember.</xsd:documentation>
<xsd:documentation>Indicates which member is primary relative to the product. A person group can have more than one primary member. </xsd:documentation>
<xsd:documentation>Indicates the functional role played by the person relative to his/her job in the organization, for example, analyst, strategist, economist, etc.</xsd:documentation>
<xsd:documentation>Strongly Recommended. Indicates how the publisher or person wants the name to be presented, for example: Dr. John Doe Sr. CPA, CFA.</xsd:documentation>
<xsd:documentation>Indicates the official title of the person within an organization -- e.g. Managing Director, Vice President, etc. </xsd:documentation>
<xsd:documentation>An identifier used to identify the person. For accurate identification it is required that the personID be unique for a given publisher, but the implementation of the ID is left to the publishers to implement as they deem fit. Examples: combination of LastName and FirstName, combination of internal employee ID and RIXML publisher ID. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="OrganizationName">
<xsd:annotation>
<xsd:documentation>The name of the organization. An organization can have multiple names as enumerated in the Name Types. At least one name is required for the content to be valid. Display name is the preferred name if only one name is provided.</xsd:documentation>
<xsd:documentation>The name can be one of the following types - legal, local, display, or parent. Use Display if using only one nameType, unless one of the other nameTypes is preferred.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="OrganizationID">
<xsd:annotation>
<xsd:documentation>An identifier used to identify the organization. At least one OrganizationID is required and multiple are possible. For example, for a product distributed via multiple vendors, each vendor may require a different OrganizationID, with the idType for each OrganizationID identifying the name of the vendor in the manner specified by the vendor.
The actual ID is stored as free text in the content of the OrganizationID node.
A UUID can also be used as one of the IDs. This is to facilitate the unique identification of a particular organization. To ensure uniqueness it is recommended that a Universal Unique IDentifier (UUID) be used as the productID. UUIDs can be generated on any computer, regardless of platform or operating system. A UUID is a 128-bit (16-byte) integer that is virtually guaranteed to be unique in the world across space and time. The Open Software Foundation (OSF) created UUIDs, as part of their Distributed Computing Environment (DCE).</xsd:documentation>
<xsd:documentation>Indicates the type of ID used. Examples: CUSIP, VendorCode.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="Organization">
<xsd:annotation>
<xsd:documentation>Describes an organization related to the research item. Multiple organizations may be related to one research item. These organizations can be subsidiaries of the same parent or different organizations (as in a joint venture) working together on a publication or event. However, there can only be one primary publisher organization, which is captured by the primaryIndicator, when contained by the Source element. </xsd:documentation>
<xsd:documentation>For the cases in which the type attribute has the value PublisherDefined, the PublisherDefinedValue element is used to hold the organization's own description of the type. </xsd:documentation>
<xsd:documentation>If there are multiple Organizations, and they should appear in a certain order when the content is published, indicate the desired order by associating the appropriate sequence number to each Organization. </xsd:documentation>
<xsd:documentation>Indicates the primary organization relative to others that may be specified. When multiple organizations (subsidiaries of the same organization or different organizations) come together on a product, one must be listed as primary (generally the parent organization or the name of the joint venture).</xsd:documentation>
<xsd:documentation>A summary of the information contained in the product. Highlights the salient issues in the document or provides a brief description of the event. Suggested maximum length is 3000 characters.</xsd:documentation>
<xsd:documentation>A very brief statement of the subject addressed in the product. This is typically only a few lines and would be appropriate for highly abbreviated displays. Suggested maximum length is 300 characters.</xsd:documentation>
<xsd:documentation>Describes the resource that contains the media representation of the research product. For example, can describe a file, URL, or encoded data that represents the product. There can be any number of Resource elements associated with a product. For example, a product may consist of both a PDF document (one resource) and an Excel spreadsheet (another resource), or there could be multiple language versions of the same document (each one a resource).</xsd:documentation>
<xsd:documentation>Indicates the protocol (rules determining format and transmission). This eliminates the need for parsing this information from the URL.</xsd:documentation>
<xsd:documentation>Indicates the type of media used to store the content. MIMEType is used to determine the software product(s) that can read the content. MIMETypes are described in RFC 2046.</xsd:documentation>
<xsd:documentation>The Name element is intended to provide a research consumer with a suggestion on how to store the particular resource, whether is comes via an actual file, embedded data or remote URL. If this RIXML file arrives with a companion file (PDF, Word, text, etc.) representing this resource, then the Name value is used to match the resource with right companion file. If a payload file is embedded data, the Name value is used by the publisher to suggest a file name to the consumer, who may choose to store the embedded data locally. If a payload file is referenced via URL, the Name value is similarly used by the publisher to suggest a file name to the consumer for local storage. </xsd:documentation>
<xsd:documentation>Any additional comments that are deemed necessary. For example, which software version is required to open the document? Or, how does this resource relate to the others for this product? </xsd:documentation>
<xsd:documentation>Used when the content (data) of the research product needs to be included within the RIXML document. The data must be encoded using the method described by the Resource's encoding attribute.</xsd:documentation>
<xsd:documentation>The unique identifier of the resource within the product. The implementation of the resourceID is left for the publishers of content to implement as they deem fit. At a minimum, the resourceID is required to be unique within the product(s) it appears under. </xsd:documentation>
<xsd:documentation>Indicates the language of the resource, described using the ISO 639-2/T Code. Highly recommended, especially when multiple resources are included that are different translations of the same product. Whereas the language attribute of the Research element represents the language of the metadata describing the Research, the language attribute of the Resource element represents the language of the media representation (often a file) of the product. These two language attributes may be different. </xsd:documentation>
<xsd:documentation>Indicates the encoding format of the content (UTF-16, UTF-64, etc). Used when content is included as encoded data in the Resource.Data element.
<xsd:documentation>Indicates the size of the resource in bytes. Could be used by the end user to estimate the download time and storage needs.</xsd:documentation>
<xsd:documentation>If there are multiple Resources, and they should appear in a certain order when the content is published, indicate the desired order by associating the appropriate sequence number to each Resource.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<!--Elements for Package 4-ContextPackage-->
<xsd:element name="Context">
<xsd:annotation>
<xsd:documentation>The top-level element of the Context section.</xsd:documentation>
<xsd:documentation>Indicates whether the content is for internal or external consumption.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="Discipline">
<xsd:annotation>
<xsd:documentation>Describes the high level content classification of a research product based on its intellectual and analytical approach.</xsd:documentation>
<xsd:documentation>Indicates the analytical technique used to create the content of the research product. Required when disciplineType is Strategy or Investment.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="ProductSeries">
<xsd:annotation>
<xsd:documentation>Used for publications issued as a series / periodical.</xsd:documentation>
<xsd:documentation>Indicates the name of the publication series. The series name should appear in the same way for all items in the series.</xsd:documentation>
<xsd:documentation>Publication number in a volume.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="ProductFocus">
<xsd:annotation>
<xsd:documentation>Indicates the primary focus of the product. This tag is used in conjunction with the primaryIndicator fields in SectorIndustry, Discipline, Issuer, Region, Country, AssetClass, AssetType, SecurityType, Index to indicate the primary topic of the product.
EXAMPLE 1: a report that is an overview of French securities, with a few brief comments about the household durables and insurance industries would have
ProductFocus.focus = Country
ProductFocus.primaryIndicator = Yes
Context.Country.countryCode = FR
Context.Country.countryName = France
Context.Country.primaryIndicator = Yes
Because the product only briefly mentions the household durables and insurance industries, these would both have the Context.sectorIndustry.primaryIndicator set to No. If other countries are mentioned, these additional Context.Country.countryCodes can be listed, with the respective primaryIndicator set to No.
EXAMPLE 2: a company report on a bank that briefly discusses how changes in the banking industry may affect aspects of the real estate industry, would have
<xsd:documentation>Focus indicates whether the product discusses any of certain attributes (such as SectorIndustry, Issuer, Country, etc.). A report primarily about one company would have a focus of Issuer, while a country overview would have a focus of Country.</xsd:documentation>
<xsd:documentation>Used to indicate which of various focus attributes in the product is the primary topic of the product.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="Keyword">
<xsd:annotation>
<xsd:documentation>Free-text keywords relevant to the product, which the consumers may want to search on. There is no maximum length, but should only be populated with terms that would help users locate relevant research products. These keywords, like all other metadata, will be in the language of the Research.Language.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string" />
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="Security">
<xsd:annotation>
<xsd:documentation>Information about a particular security that describes the type of security and how to identify it. A security is always issued by an issuer, therefore, if a security is being mentioned, it must be attached to an Issuer element.</xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing the coverage status of a Security. Example: a publisher initiates coverage of Security ABC.</xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing the weighting of the security. </xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing their recommendation on a Security. Example: a publisher downgrades Security ABC.</xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing their target price estimate for a Security. Example: a publisher increases a target price for Security ABC to $100.</xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing their earnings estimates for a Security. Example: a publisher lowers all their earnings estimates for Security ABC.</xsd:documentation>
<xsd:documentation>If there are multiple Securities, and they should appear in a certain order when the content is published, indicate the desired order by associating the appropriate sequence number to each Security.</xsd:documentation>
<xsd:documentation>Indicates the primary Security or Securities discussed in the research product. If the product is focused at the Security level (i.e. the ProductFocus tag is set to Security), then at least one Security must be marked as primary. Otherwise primaryIndicator is optional.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="Recommendation">
<xsd:annotation>
<xsd:documentation>This is information regarding recommendations. These can be about the issuer of a security or a security itself, or other entities.
<xsd:documentation>This is the period for which the rating is relevant. This may be short-term (less than 270 days), or long-term (greater than 270 days). </xsd:documentation>
<xsd:documentation>Used to indicate whether the recommendation is current or prior (current is the default). Prior is only used to give reference for a change from a prior recommendation. Prior is used to indicate what the prior figure was for the period specified in order to give context to the current figure, not to provide the figure for a prior time period.</xsd:documentation>
<xsd:documentation>Used together with periodYear and periodEnd to indicate the applicable period for a financial value. Example: Q4 2000 ending 31 December.</xsd:documentation>
<xsd:documentation>Used together with period and periodYear to indicate the applicable period for a financial value. Example: Q4 2000 ending 31 December.</xsd:documentation>
<xsd:documentation>The four-digit year used together with period and periodEnd to indicate the applicable period for a financial value. Example: Q4 2000 ending 31 December.</xsd:documentation>
<xsd:documentation>Exact date and time applicable to a financial data item, 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 Zulu time or Z-time (GMT +/- n hours:minute:seconds). All times are absolute and easier to compute, rather than using a relative (i.e. 08:30 +5) time. Generally dateTime is used instead of period, periodYear and periodEnd when a specific date can be assigned to a financial data item, for example, Total Assets as of 31 January 2000.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="IssuerFinancials">
<xsd:annotation>
<xsd:documentation>Financial data related to the issuer of a security.</xsd:documentation>
<xsd:documentation>Indicates the currency of the issuer financials. Represented by the three letter alpha code defined by ISO 4217.</xsd:documentation>
<xsd:documentation>Free-text tag to indicate the source of the numbers. Example: the name of the company that provides the consensus figures.</xsd:documentation>
<xsd:documentation>Indicates whether the financials are current or prior. Defaulted to currentPrior is used to indicate what the prior figure was for the period specified in order to give context to the current figure, not to provide the figure for a prior time period.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="Issuer">
<xsd:annotation>
<xsd:documentation>Describes the Issuer of a security.</xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing coverage status of an Issuer. Example: a publisher initiates coverage of Company XYZ.</xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing the weighting of the issuer. </xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing their recommendation on an Issuer. Example: a publisher downgrades Company XYZ.</xsd:documentation>
<xsd:documentation>If there are multiple Issuers, and they should appear in a certain order when the content is published, indicate the desired order by associating the appropriate sequence number to each Issuer.</xsd:documentation>
<xsd:documentation>Indicates the primary Issuer(s) discussed in the research product. If the product is focused at the Issuer level (i.e. the ProductFocus tag is set to Issuer), then at least one Issuer must be marked as primary. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="Country">
<xsd:annotation>
<xsd:documentation>Strongly recommended. Indicates the country or countries that are discussed in a research product.</xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing coverage status of a country. Example: a publisher initiates coverage of country A.</xsd:documentation>
<xsd:documentation>Highlights an actoin taken by the publisher. Indicates that the publisher is changing the weighting of the country. Example: A publisher maintaining an overweight position of country ABC compared with a particular index. </xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing their recommendation on an Country. Example: a publisher downgrades country A.</xsd:documentation>
<xsd:documentation>If there are multiple Countries, and they should appear in a certain order when the content is published, indicate the desired order by associating the appropriate sequence number to each Country.</xsd:documentation>
<xsd:documentation>Indicates the primary country or countries discussed in the research product. If the product is focused on the Country level (i.e. the ProductFocus tag is set to Country), then at least one Country must be marked as primary. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="SectorIndustry">
<xsd:annotation>
<xsd:documentation>Strongly recommended. The sector or industry classification to which a security belongs, or about which the research product is written.
GICS has been accepted as the official RIXML sector / industry classification scheme . Publishers are required to use this classification scheme to provide the correct GICS sector / industry for a research product. This gives consumers a standardized means of determining the sector / industry that a research product is written about.
The GICS sector / industry classification must be provided for each primary security mentioned in the product. Should the product be focused on the sector / industry level, publishers must provide the GICS sector / industry classification that most closely matches what the product is written about.
Publishers are also able to provide publisher defined sector / industry tags, giving them the flexibility to tag their research using their own industry classification scheme. However, should they do so, they must also provide the closest match from the GICS scheme to ensure consistency on the consumption side.</xsd:documentation>
<xsd:documentation>Identifies the sector under consideration. Refer to the RIXML sector-industry code document for a valid list of RIXML-defined codes. Publisher defined codes can be used in addition to, but not instead of, the RIXML-defined codes.</xsd:documentation>
<xsd:documentation>Since sectors are organized in a hierarchical fashion, the level element indicates the level that a specific SectorIndustry element is at in this hierarchy. There are four levels within the GICS classification scheme, with level 1 referring to Sectors, level 2 to Industry Groups, level 3 to Industries and level 4 to Sub Industries.</xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing coverage status of a SectorIndustry. Example: a publisher initiates coverage of the Entertainment sector.</xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing the weighting of the sector/industry. Example: A publisher recommends having an overweight position in the Energy sector and an underweight position in the Technology sector. </xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing their recommendation on an SectorIndustry. Example: a publisher downgrades the Technology sector.</xsd:documentation>
<xsd:documentation>If there are multiple Sectors and/or Industries, and they should appear in a certain order when the content is published, indicate the desired order by associating the appropriate sequence number to each Sector or Industry.</xsd:documentation>
<xsd:documentation>Indicates whether the current level is the main focus of the product being published. This tag is used in conjunction with the ProductFocus tag to determine the focus of a product. Example: a product focusing on the Entertainment sub-industry, would have the ProductFocus.focus tag set to SectorIndustry, and in the correct SectorIndustry element the following values would be set:
SectorIndustry.classificationType = GICS
SectorIndustry.level = 4
SectorIndustry.focusLevel = Yes
SectorIndustry.primaryIndicator = Yes
SectorIndustry.name = Entertainment.
This allows a consumer to determine the exact focus of the product.</xsd:documentation>
<xsd:documentation>Indicates the primary SectorIndustry or SectorIndustries discussed in the product. If the product is focused on the SectorIndustry level (i.e. the ProductFocus tag is set to SectorIndustry), then at least one SectorIndustry must be marked as primary. </xsd:documentation>
<xsd:documentation>Indicates whether the specified SectorIndustry is an official classification. Specifically, if the classificationType is "GICS", then this value must be supplied and set to "Yes" to indicate a mapping that complies with the official GICS classification. Likewise, this value must be supplied and set to "No" if the related Issuer or Security is mapped only on a best-guess basis and is not part of the official GICS classification. If this optional attribute is not supplied and the classificationType is "GICS", the consumer should assume a value of "No". </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="SecurityID">
<xsd:annotation>
<xsd:documentation>Used to uniquely identify the security</xsd:documentation>
<xsd:documentation>Indicates the organization or company's protocol used for the security identifier (i.e. the Security classification scheme). Examples include CUSIP, RIC, BloombergCode, etc.</xsd:documentation>
<xsd:documentation>If the SecurityID.idType = PublisherDefined, then the publisher can indicate a type of security identifier not in the IssuerSecurityIDTypeEnum list.</xsd:documentation>
<xsd:documentation>The actual unique identifier for this security. Example: MSFT.O is correct idValue for Microsoft Common Shares using the Reuters RIC scheme.</xsd:documentation>
<xsd:documentation>Indicates the organization or company's protocol used for the issuer identifier (i.e. the Issuer classification scheme). Note that since their is no universally accepted means of identifying an Issuer (as opposed to a specific security), IssuerID allows the use of what are technically security identifers as a means of identifying an Issuer (CUSIP, SEDOL, etc).</xsd:documentation>
<xsd:documentation>If the IssuerID.idType = PublisherDefined, then the publisher can indicate what type of identifier has been used.</xsd:documentation>
<xsd:documentation>If the IssuerName.NameType = PublisherDefined, then the publisher can indicate what type of name has been used. </xsd:documentation>
<xsd:documentation>An issuer can have multiple names. The names can be one or more of the following types: legal, local, display, parent, trading. Use Display if using only one nameType, unless one of the other nameTypes is preferred.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="SecurityFinancials">
<xsd:annotation>
<xsd:documentation>Describes the financials associated with a security.
Example: If the SecurityFinancialsType is EPS and the scenario is EPS period = Q1 value = 10 cents, year = 2000, no duration, no datetime, then this is how the XML would look :
<xsd:documentation>Indicates the currency of the security financials. Represented by the three letter alpha code defined by ISO 4217.</xsd:documentation>
<xsd:documentation>Free-text tag to indicate the source of the numbers. Example: the name of the company that provides the consensus figures.</xsd:documentation>
<xsd:documentation>Indicates whether the financials are current or prior. Defaulted to current. Prior is used to indicate what the prior figure was for the period specified in order to give context to the current figure, not to provide the figure for a prior time period.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="Region">
<xsd:annotation>
<xsd:documentation>Indicates a region discussed in the product.</xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing coverage status of a Region. Example: a publisher initiates coverage of the Latin American region.</xsd:documentation>
<xsd:documentation>Highlights an actoin taken by the publisher. Indicates that the publisher is changing the weighting of the region. Example: A publisher maintaining an overweight position of region ABC compared with a particular index. </xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing their recommendation on an Country. Example: a publisher downgrades country A.</xsd:documentation>
<xsd:documentation>If there are multiple Regions, and they should appear in a certain order when the content is published, indicate the desired order by associating the appropriate sequence number to each Region.</xsd:documentation>
<xsd:documentation>Indicates the primary Region(s) discussed in the product. If the product is focused on the Region level (i.e. the ProductFocus tag is set to Region), then at least one Region must be marked as primary. </xsd:documentation>
<xsd:documentation>Used together with lastReportedYear to indicate the period when the financials were last reported. For example, Q1 2000.</xsd:documentation>
<xsd:documentation>Used together with lastReportedPeriod to indicate the period when the financials were last reported. For example, Q1 2000.</xsd:documentation>
<xsd:documentation>Represents the date the numbers were actually published. 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 Zulu time or Z-time (GMT +/- n hours:minute:seconds). All times are absolute and easier to compute, rather than using a relative (i.e. 08:30 +5) time. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="Entitlement">
<xsd:annotation>
<xsd:documentation>A container for more specific entitlement types. Mostly used as a convenient receptacle for attributes that apply to all lower entitlement types. </xsd:documentation>
<xsd:documentation>If there are multiple Entitlements, and they should take precedence in a certain order when the content is published, indicate the desired order by associating the appropriate sequence number to each Entitlement. </xsd:documentation>
<xsd:documentation>If Periodicity.Value = PublisherDefined, then the publisher can indicate a frequency not in the PeriodicityEnum list.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="ProductCategory">
<xsd:annotation>
<xsd:documentation>Describes the manner or format that information is presented within the product. Product categories include Comment, Report, Model, Chart, etc.</xsd:documentation>
<xsd:documentation>If ProductCategory.Value = PublisherDefined, then the publisher can indicate what type of product this is.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="Subject">
<xsd:annotation>
<xsd:documentation>Strongly recommended. Indicates the subject of the product. There is a standard set of subjects defined by RIXML including market opening comments, accounting and tax policy, and earnings surprise. If these do not fully represent the subject, the publisher may use a publisher defined Subject value.</xsd:documentation>
<xsd:documentation>If the Subject.Value = PublisherDefined, then the publisher can indicate a subject not in the SubjectEnum list.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="AssetClass">
<xsd:annotation>
<xsd:documentation>When attached to a Context element, indicates the asset class that the research product focuses on. When attached to a Security element, indicates the asset class of the security. Typically used in conjunction with AssetType and SecurityType. One of the following: equity, fixed income, commodity or currency.</xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing the weighting of the asset class. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="AssetType">
<xsd:annotation>
<xsd:documentation>Indicates the asset type. Typically used in conjunction with AssetClass and SecurityType. Can be attached to a Context element or to a Security element. For equities, examples include stocks, convertibles, warrants and preferred stocks. For bonds, examples include the major fixed income sectors typically used in major fixed income index benchmarks. These include U.S. Treasuries, Corporate High Yield and Municipals, among others.</xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing the weighting of the asset type. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="SecurityType">
<xsd:annotation>
<xsd:documentation>Indicates the type of security. Typically used in conjunction with AssetClass and AssetType. Can be attached to a Context element or to a Security element. Example values include stock, convertible, high yield credit, investment grade credit.</xsd:documentation>
<xsd:documentation>Used when SecurityType.Value = PublisherDefined to indicate a type of security not in the SecurityTypeEnum list.</xsd:documentation>
<xsd:documentation>Highlights an action taken by the publisher. Indicates that the publisher is changing the weighting of the security type. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="Index">
<xsd:annotation>
<xsd:documentation>Indicates an index mentioned in the product.</xsd:documentation>
<xsd:documentation>Used to indicate the index name, when the name attribute is PublisherDefined. This is for cases where the relevant index is not already on the enumeration list. </xsd:documentation>
<xsd:documentation>The proprietary name of the product as defined by the research provider. This can be used to express a brand name. Examples of product names are "ABC Investment Bank's Tech Weekly", or "From the Floor in Asia".</xsd:documentation>
<xsd:documentation>Indicates the date and time at which the product was officially published. This is the date and time that would appear on the product itself, or be displayed to a reader. 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 Zulu time or Z-time (GMT +/- n hours:minute:seconds). All times are absolute and easier to compute, rather than using a relative (i.e. 08:30 +5) time. </xsd:documentation>
<xsd:documentation>Indicates the venue -- can by physical (one-on-one meeting) or virtual (conference call or webcast). Strongly recommended for a location-based event. Required when Product.eventIndicator=Yes or Product.Context.ProductDetails.ProductCategory.productCategory=Event. </xsd:documentation>
<xsd:documentation>Describes the organization hosting the event. Multiple hosts of one event are possible. However, there can be only one primary host, which is captured by the Organizatoin primaryIndicator. </xsd:documentation>
<xsd:documentation>Describes a date/time relevant to the event, and relative to the type attribute. 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 Zulu time or Z-time (GMT +/- n hours:minute:seconds). All times are absolute and easier to compute, rather than using a relative (i.e. 08:30 +5) time. </xsd:documentation>
<xsd:documentation>Describes the relevance of the date/time to the event. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="Weighting">
<xsd:annotation>
<xsd:documentation>This is information regarding weightings. These can be about the country, region, asset type, or other entities.</xsd:documentation>
<xsd:documentation>This is the period for which the rating is relevant. This may be short-term (less than 270 days), or long-term (greater than 270 days). </xsd:documentation>
<xsd:documentation>Used to indicate whether the weighting is current or prior (current is the default). Prior is only used to give reference for a change from a prior weighting. Prior is used to indicate what the prior figure was for the period specified in order to give context to the current figure, not to provide the figure for a prior time period.</xsd:documentation>
<xsd:documentation>The actual weighting. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="RatingAgency">
<xsd:annotation>
<xsd:documentation>The independent rating agency featured in the research item. This may be the agency whose rating the publisher is questioning. </xsd:documentation>
<xsd:documentation>Indicates whether the audience described by the audienceType attribute is internal to the publisher's organization or external. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="SectorIndustryEntitlement">
<xsd:annotation>
<xsd:documentation>An entitlement based on the industry classification of the research consumer. </xsd:documentation>
<xsd:documentation>The date and time after which the product should be read. It is optional because using only an endDateTime is also a meaningful use-case for products that are immediately readable, but expire at a certain time. The startDateTime must be later on the time scale than the value of Product.publicationDateTime. </xsd:documentation>
<xsd:documentation>The date and time after which the product should not be read. It is optional because using only a startDateTime is also a meaningful use-case for products that are only readable after a time embargo, but never expire. The endDateTime must be later on the time scale than the value of Product.publicationDateTime. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="EntitlementGroup">
<xsd:annotation>
<xsd:documentation>A composite restriction on the use of the product. Each individual entitlement specification inside a single EntitlementGroup applies conjuctively with the others in the group -- i.e. they are AND-ed together. For example, you could limit readership to American press agencies by including a LocationEntitlement (containing a Country element with the U.S. country code) and an AudienceTypeEntitlement (containing the Media audience type code). Each EntitlementGroup applies disjunctively with the other EntitlementGroups -- i.e. they are OR-ed together. </xsd:documentation>
<xsd:documentation>Indicates the length of the product. For example, if the product were a PDF file, the length would be in pages. </xsd:documentation>
<xsd:documentation>Indicates the unit of length. For example pages, seconds, minutes.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="StatusInfo">
<xsd:annotation>
<xsd:documentation>Describes the status of the product. Multiple StatusInfo elements are permitted. Each time the product status changes, and the publisher adds a StatusInfo element, the statusDateTime must be set to reflect the point of change, and the currentStatusIndicator must be updated so that only one StatusInfo is marked as current. </xsd:documentation>
<xsd:documentation>Indicates the date and time at which the status was assigned. 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 Zulu time or Z-time (GMT +/- n hours:minute:seconds). All times are absolute and easier to compute, rather than using a relative (i.e. 08:30 +5) time. </xsd:documentation>
<xsd:documentation>Indicates whether or not the statusType is current -- i.e. the most recent. Note that while a product can have multiple statuses, only one of them can be current.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<!--Elements for Package 5-LegalPackage-->
<xsd:element name="Legal">
<xsd:annotation>
<xsd:documentation>The top-level element of the Legal section.</xsd:documentation>
<xsd:documentation>Disclaimer is the long generic legalese that automatically gets pasted into a note/report that 'disclaims' against liabilities for losses associated with buying/selling stocks etc. This could also include generic disclaimers when a report discusses MSCI indexes. This section changes infrequently.</xsd:documentation>
<xsd:documentation>Disclosure information from the publisher that is required to accompany a research product. Disclosure is 'proactive' in that it discloses current involvement and role in an offering or M&A. This would also include disclosures of analyst holdings in stock mentioned, etc. This section changes relatively frequently. </xsd:documentation>
<xsd:documentation>Indicates the publisher defined disclosure code for a specific disclosure. For example, a publisher may need to disclose a banking relationship with a company, and may call this disclosure code A.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="IssuerSecurityID">
<xsd:annotation>
<xsd:documentation>Links disclaimer information to specific issuers and securities. This allows consumers to determine the nature of disclosures and to which issuers and/or securities they apply.</xsd:documentation>
<xsd:documentation>An IssuerID that also appears elsewhere in the metadata of the product, enabling the consumer to uniquely identify the issuer that is being referred to.</xsd:documentation>
<xsd:documentation>A SecurityID that also appears elsewhere in the metadata of the product, enabling the consumer to uniquely identify the security that is being referred to.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="Hedge">
<xsd:annotation>
<xsd:documentation>Hedge is a clause that notes if firm acted as manager or co-manager of a public offering of a company within the past three years, or some other stock-specific clause. This section changes less frequently.</xsd:documentation>
<xsd:documentation>Indicates the publisher defined hedge code for a specific hedge. For example, a publisher may need to disclose a banking relationship with a company, and may call this hedge code A.</xsd:documentation>
