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. 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). 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. 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. 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. The description of the relationship between the current product and the other product to which it is related. The unique productID of the product to which this product is related (as stored in Product.productID of the related document) Indicates the type of relationship between this product and another product. Research is the root tag for bundling research products. 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). 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. 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. Strongly Recommended. Describes the street address. Indicates the first line of the street address. Indicates the second line of the street address. Indicates the third line of the street address. Indicates the city where the street address is located. Indicates the State/Province/Canton/County information of the address. Indicates the Postal code, quadrant, zone or Zip code. This field indicates the country, as it should be displayed. Strongly Recommended. Indicates the email address. Strongly Recommended. Describes the telephone, fax or pager numbers. Telephone country code for the phone number. Phone number including area code. Used for extension number for a phone or a PIN. PINs are sometimes associated with pagers. Phone numbers can be one of the following types - voice, fax, or pager. Describes the location of the phone at this number -- i.e. office, home, moblie. Strongly Recommended. Provides a URI reference for a web site. Web address associated with the person or organization. Describes an Instant Messenger address. Indicates the Instant Messenger protocol type -- i.e. AIM, ICQ, MSN, SMS, Yahoo, etc. For specifying other IM systems. The top-level element of the ContactInfo section. 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. Used to indicate the nature of the contact information - business or personal. Describes the intended purpose of the contact information. Gives the reader an idea of what to expect on the far side. 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. 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. 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. If the role attribute has the value PublisherDefined, this element is used to hold the publisher's own description of the role. Some unique label used to reference a particular group of people. 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. Indicates the primary PersonGroup, when more than one are specified. 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. 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. If the role attribute has value PublisherDefined, then the publisher indicates the role in this element. 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. Indicates which member is primary relative to the product. A person group can have more than one primary member. The role of this individual person relative to this research item. Describes an individual involved in the product in some capacity. Indicates the functional role played by the person relative to his/her job in the organization, for example, analyst, strategist, economist, etc. Indicates the family name of the person. Indicates the given name of the person. Indicates the middle name of the person. Strongly Recommended. Indicates how the publisher or person wants the name to be presented, for example: Dr. John Doe Sr. CPA, CFA. Indicates the official title of the person within an organization -- e.g. Managing Director, Vice President, etc. Indicates the division that the person officially works for within an organization. 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. 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. 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. 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). Indicates the type of ID used. Examples: CUSIP, VendorCode. 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. Indicates the URL location of the logo of the organization. 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. Optional description of the organization. Used to include any additional information about the organization. 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. 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). The type of the organization. The top-level element of the Content section. This is the primary title of the product. This is the sub title of the product. 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. 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. 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). Indicates the protocol (rules determining format and transmission). This eliminates the need for parsing this information from the URL. 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. 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. 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? Indicates the URL at which the resource can be found. Used when the content (data) of the research product needs to be included within the RIXML document. The data must be base64-encoded. 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. 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. Indicates the size of the resource in bytes. Could be used by the end user to estimate the download time and storage needs. Indicates the primary Resource. At least one Resource must be set to Primary. 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. The top-level element of the Context section. Allows the publisher to 'highlight' a specific product, i.e. identify a product as a high priority item. Indicates whether the content is for internal or external consumption. Describes the high level content classification of a research product based on its intellectual and analytical approach. Indicates the high level discipline of the research product. Indicates the analytical technique used to create the content of the research product. Required when disciplineType is Strategy or Investment. Used for publications issued as a series / periodical. Indicates the name of the publication series. The series name should appear in the same way for all items in the series. Volume number. Publication number in a volume. 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 ProductFocus.focus = Issuer ProductFocus.primaryIndicator = Yes Context.SectorIndustry.sectorIndustryCode = 4010 Context. SectorIndustry.Name = Banks Context. SectorIndustry.primaryIndicator = Yes Context.SectorIndustry.sectorIndustryCode = 4040 Context. SectorIndustry.Name = Real Estate Context. SectorIndustry.primaryIndicator = No. 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. Used to indicate which of various focus attributes in the product is the primary topic of the product. 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. 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. The name of the Security. Optional short name commonly used to identify the Security. 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. Highlights an action taken by the publisher. Indicates that the publisher is changing the weighting of the security. Highlights an action taken by the publisher. Indicates that the publisher is changing their rating on a Security. Example: a publisher downgrades Security ABC. 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. 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. 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. 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. This is information regarding ratings. These can be about the issuer of a security or a security itself, an industry, a country, or other entities. Used when the rating value is PublisherDefined. A description of the rating. May include time horizon. This is the period for which the rating is relevant, as of the date it was established by the authoring entity. Used to indicate whether the rating is current or prior (current is the default). Prior is only used to give reference for a change from a prior rating. 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. Provides a context for the rating. Indicates the volatility of the rated entity. An indication of the potential price fluctuation of the rated entity. The actual rating as issued by the authoring entity. Stores a specific financial data item for an issuer or a security. Indicates whether a financial figure is actual or estimated. Used together with periodYear and periodEnd to indicate the applicable period for a financial value. Example: Q4 2000 ending 31 December. Used together with period and periodYear to indicate the applicable period for a financial value. Example: Q4 2000 ending 31 December. 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. Time duration that is being addressed. 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. Financial data related to the issuer of a security. Indicates the currency of the issuer financials. Represented by the three letter alpha code defined by ISO 4217. Free-text tag to indicate the source of the numbers. Example: the name of the company that provides the consensus figures. Generally Accepted Accounting Principles. To state in a new form a company's financial statements, perhaps to reflect a current period item back through prior periods. A hypothetical financial model based on a set of assumptions. Used to indicate what type of financial metrics are being represented here. Indicates whether the year specified is a fiscal year or calendar year 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. Describes the Issuer of a security. Indicates the URL where the Issuer's logo may be found. A text description (name) of the Issuer. Strongly Recommended element. Indicates the type of Issuer. For example, can be agency, government or corporate. Indicates the country where the Issuer is domiciled, represented by the ISO 3166-1 country code. Combination of Day and Month that indicates the fiscal year end of the Issuer. 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. Highlights an action taken by the publisher. Indicates that the publisher is changing the weighting of the issuer. Highlights an action taken by the publisher. Indicates that the publisher is changing their rating on an Issuer. Example: a publisher downgrades Company XYZ. 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. 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. Strongly recommended. Indicates the country or countries that are discussed in a research product. The ISO 3166-1 code for the country. Indicates whether the publisher defines this country as an emerging market. 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. 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. Highlights an action taken by the publisher. Indicates that the publisher is changing their rating on an Country. Example: a publisher downgrades country A. 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. 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. 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. A short name for the sector. Example: Pharma may be used for Major Pharmaceuticals. Indicates the name of the sector. A textual description of the sector. 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. 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. Name of the classification method used. Options are GICS or PublisherDefined. 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. 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. Highlights an action taken by the publisher. Indicates that the publisher is changing their rating on an SectorIndustry. Example: a publisher downgrades the Technology sector. 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. 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. 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. 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". Used to uniquely identify the security Exchange on which the security is traded. Indicates the organization or company's protocol used for the security identifier (i.e. the Security classification scheme). Examples include CUSIP, RIC, BloombergCode, etc. If the SecurityID.idType = PublisherDefined, then the publisher can indicate a type of security identifier not in the IssuerSecurityIDTypeEnum list. The actual unique identifier for this security. Example: MSFT.O is correct idValue for Microsoft Common Shares using the Reuters RIC scheme. The ISO 3166-1 Country code for the country in which the exchange operates. Used to uniquely identify the issuer. 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). If the IssuerID.idType = PublisherDefined, then the publisher can indicate what type of identifier has been used. The actual identifier for this issuer. This is the name of the issuer related to the IssuerID.idValue. If the IssuerName.NameType = PublisherDefined, then the publisher can indicate what type of name has been used. The name that is associated with the IssuerID.idValue above. 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. Describes the financials associated with a security. Indicates the currency of the security financials. Represented by the three letter alpha code defined by ISO 4217. Free-text tag to indicate the source of the numbers. Example: the name of the company that provides the consensus figures. Indicates whether the financials are basic, primary, or diluted. Generally Accepted Accounting Principles. To state in a new form a company's financial statements, perhaps to reflect a current period item back through prior periods. A hypothetical financial model based on a set of assumptions. Used to indicate what type of financial metrics are being represented here. Actual value as provided by the Publisher. Indicates whether the year specified is a fiscal year or calendar year 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. Indicates a region discussed in the product. Indicates whether this Region is defined by the publisher as an emerging market. 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. 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. Highlights an action taken by the publisher. Indicates that the publisher is changing their rating on an Country. Example: a publisher downgrades country A. 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. 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. Relevant dates related to Issuer and/or Security financial data. Used together with lastReportedYear to indicate the period when the financials were last reported. For example, Q1 2000. Used together with lastReportedPeriod to indicate the period when the financials were last reported. For example, Q1 2000. 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. A container for more specific entitlement types. Mostly used as a convenient receptacle for attributes that apply to all lower entitlement types. 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. If necessary, indicates which entitlement is primary. Indicates the frequency with which the publication is published or the event occurs. This is the frequency with which this product is published or this event is held. If Periodicity.Value = PublisherDefined, then the publisher can indicate a frequency not in the PeriodicityEnum list. Describes the manner or format that information is presented within the product. Product categories include Comment, Report, Model, Chart, etc. The category that the product fits into. If productCategory is PublisherDefined, then the publisher can indicate what type of product this is. 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. The main topic covered in the product. If the Subject.Value = PublisherDefined, then the publisher can indicate a subject not in the SubjectEnum list. 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. Indicates the asset class. Highlights an action taken by the publisher. Indicates that the publisher is changing the weighting of the asset class. 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. Indicates the asset type. Used when AssetType.Value = PublisherDefined to indicate a type of asset not in the AssetTypeEnum list. Highlights an action taken by the publisher. Indicates that the publisher is changing the weighting of the asset type. 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. Indicates the security type. Used when SecurityType.Value = PublisherDefined to indicate a type of security not in the SecurityTypeEnum list. Highlights an action taken by the publisher. Indicates that the publisher is changing the weighting of the security type. Indicates an index mentioned in the product. 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. An indication of the type of index. Typically market, industry or country. This is the index name. KeywordClassifications grouping element that groups or bounds multiple keyword elements. This is the container class for all the tags available for use when describing any research product. 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". 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. Indicates whether or not the content is a periodical. This is the container class for all the tags available for use when classifying the research product. This is the container class for all the tags available for use when describing an Security. This is the container class for all the tags available for use when describing an Issuer. Provides the necessary information when the Product is actually about an event. Indicates the type of the event. 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. 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. Registration information relating to an event. 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. Describes the relevance of the date/time to the event. This is information regarding weightings. These can be about the country, region, asset type, or other entities. Used when the weighting value is PublisherDefined. A description of the weighting. May include time horizon. This is the period for which the weighting is relevant, as of the date it was established by the authoring entity. 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. The actual weighting as issued by the authoring entity. The rating entity featured in the research item. This may be a publisher or an independent agency. Used when the ratingEntity value is PublisherDefined. An entitlement based on the country in which the research consumer is located. An entitlement based on the type of audience. Indicates the audience type that the author intended to address with the product. Indicates whether the audience described by the audienceType attribute is internal to the publisher's organization or external. An entitlement based on the industry classification of the research consumer. Indicates the time during which this product should be read. 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. 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. 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. An entitlement based on the region in which the research consumer is located. Indicates the length of the product. For example, if the product were a PDF file, the length would be in pages. Indicates the unit of length. For example pages, seconds, minutes. 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. Support for internal versioning of a given product. Indicates the status of the product or resource. 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. 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. The top-level element of the Legal section. Copyright information relating to the product. 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. 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. A description of the disclosure. 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. 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. 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. 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. 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. A description of the hedge. 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.