AudienceTypeEntitlement
RIXML 2.5 Element
Specifies client category restrictions for research access through a mandatory audienceType attribute drawn from AudienceTypeEnum values, defining which client segments can access the content.
Usage
Include at most one AudienceTypeEntitlement element within an Entitlement when client-type restrictions apply. Select appropriate audience categories like Institutional, Retail, or Corporate based on intended recipient characteristics.
Business Context
Enables business model differentiation and regulatory compliance by controlling research distribution based on client sophistication levels, registration status, and service tier arrangements.
Where It Fits
Canonical Path
Definition
| Type | |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
| Content Model | Text content (string) |
Attributes
audienceTypeAudienceTypeEnum |
Indicates the audience type that the author intended to address with the product. requiredSince 2.1 |
externalYesNoEnum |
Indicates whether the audience described by the audienceType attribute is internal to the publisher's organization or external. optional |
entitlementContextstring |
Indicates the context in which the entitlement applies -- typically given as a mnemonic for an individual vendor platform. Here, a vendor is defined as an organization outside the buy-side and sell-side community of financial services firms which provides platforms or tools used by participants in the investment research economy. optionalSince 2.3 |
Children
Contains text content (type: string)
This element's value is its text content. Attributes provide additional context.
Example
<AudienceTypeEntitlement audienceType="Value">ABC-123</AudienceTypeEntitlement>Version History
entitlementContextBusiness Rules
Each vendor-specific entitlement code must appear in its own distinct AudienceTypeEntitlement element within separate Entitlement and EntitlementGroup elements
Design Decisions
Each vendor-specific entitlement code should appear in its own distinct AudienceTypeEntitlement element within separate Entitlement and EntitlementGroup elements
This structure ensures proper isolation and processing of different vendor entitlement systems while maintaining clear separation of access controls
RIXML Research Data Dictionary v2.5.1, p.20
Semantic Relationships
Requires1 relationship
Vendor-specific entitlement codes should each appear within their own distinct AudienceTypeEntitlement element within separate Entitlement and EntitlementGroup elements
RIXML Research Data Dictionary v2.5.1, p.20— How to Code Vendor-Specific Entitlement Codes