ProductCategoryEntitlement
RIXML 2.5 Element
Entitlement restriction based on the category or format of research products, such as reports, comments, models, or presentations. Enables differentiated access control based on content type and format.
Usage
Used within Entitlement elements to restrict access by product category. Requires one or more ProductCategory child elements to specify which categories are covered by the entitlement restriction.
Business Context
Allows publishers to offer tiered service levels where different subscriber categories have access to different types of research products. Supports business models that differentiate premium content from basic research access.
Specification Guide
Overview
ProductCategoryEntitlement is an optional entitlement sub-element that restricts access to research content based on the product category of the material — for example, Comment, Report, Model, Compilation, Event, or Primer. Introduced in RIXML 2.5, it allows publishers and distributors to differentiate entitlements by content type or format, supporting tiered service models and enhanced distribution controls (sources: release-notes-2.5 p.8, data-dictionary-2.5.1 p.58).
Usage
Use ProductCategoryEntitlement as an optional child of Entitlement (within an EntitlementGroup) when access rights need to be limited to specific research product categories. It contains one or more ProductCategory child elements (maxOccurs="unbounded"), each naming an allowed category drawn from ProductCategoryEnum (e.g. Comment, Report, Model, Compilation, Event, Primer). Within a single EntitlementGroup, ProductCategoryEntitlement combines conjunctively (AND) with sibling entitlement restrictions such as AssetClassEntitlement, OrganizationTypeEntitlement, ActionEntitlement, RegionEntitlement, SectorIndustryEntitlement, CountryEntitlement, AudienceTypeEntitlement, and TimeEntitlement. This enables fine-grained, layered access control aligned with content licensing agreements and audience segmentation strategies (sources: release-notes-2.5 pp.8–9, data-dictionary-2.5.1 p.58).
Rules
- MUSTProductCategoryEntitlement must contain one or more ProductCategory child elements to identify the categories covered by the restriction.[RIXML Release Notes v2.5 p.8] [RIXML Research Data Dictionary v2.5.1 p.58]
- INFORMATIVEProductCategoryEntitlement is an optional sub-element of Entitlement in RIXML v2.5, alongside the other new entitlement sub-elements AssetClassEntitlement, OrganizationTypeEntitlement, and ActionEntitlement.[RIXML Quarterly Update 2017 Q2 p.8]↗ [RIXML Release Notes v2.5 p.8]
- INFORMATIVEWhen multiple entitlement restrictions appear together within the same EntitlementGroup, ProductCategoryEntitlement combines with them using conjunctive (AND) logic.[RIXML Release Notes v2.5 p.8] [RIXML Release Notes v2.5 p.9]
Relationships
- child-ofEntitlement — ProductCategoryEntitlement appears as an optional child of Entitlement, narrowing the broader entitlement framework with product-category-level granularity.
- containsProductCategory — ProductCategoryEntitlement contains one or more ProductCategory elements identifying the categories (e.g. Comment, Report, Model, Compilation, Event, Primer) to which access is constrained.
- scoped-byEntitlementGroup — ProductCategoryEntitlement sits within an EntitlementGroup, where it composes conjunctively with peer entitlement restrictions.
- peer-ofAssetClassEntitlement — ProductCategoryEntitlement is a sibling of AssetClassEntitlement, OrganizationTypeEntitlement, and ActionEntitlement — all introduced together in v2.5 to broaden entitlement support.
- usesProductCategoryEnum — The permitted values for the contained ProductCategory elements are drawn from ProductCategoryEnum (e.g. Comment, Report, Model, Compilation, Event, Primer).
Where It Fits
Canonical Path
Children
Definition
| Type | |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
Attributes
No attributes defined for this element
Children
ProductCategorystring1..unbounded |
requiredSince 2.5 |
Example
<ProductCategoryEntitlement>
<ProductCategory> ... </ProductCategory>
</ProductCategoryEntitlement>Version History
Unchanged since introduction in RIXML 2.5
Introduced in RIXML 2.5. ProductCategoryEntitlement was added as a new optional sub-element of Entitlement, together with AssetClassEntitlement, OrganizationTypeEntitlement, and ActionEntitlement. The addition responded to change requests received from members and non-members following the v2.4 release, and was positioned as supporting enhanced distribution controls relevant to MiFID II compliance by enabling finer-grained, content-type-aware entitlements (sources: quarterly-2017-q2 p.8, quarterly-2017-q3 p.8, release-notes-2.5 p.8). The element has no prior history in earlier versions.
Design Decisions
Added ProductCategoryEntitlement element to broaden entitlement support for limiting content by product category
Expands entitlement capabilities to restrict content access based on product categories like Comment, Report, Model, Compilation, Event, and Primer
RIXML Release Notes v2.5, p.8
Semantic Relationships
Constrains1 relationship
Product category entitlement limits content access to specific product categories like Comment, Report, Model
RIXML Release Notes v2.5, p.8— Broadening support for different types of entitlements