SectorIndustryEntitlement
RIXML 2.5 Element
Entitlement restriction based on the industry classification focus of research consumers, enabling access control aligned with industry expertise and regulatory permissions for specific sectors.
Usage
Used within Entitlement elements to restrict access by industry classification. Requires one or more SectorIndustry child elements to define which industry sectors are covered by the entitlement restriction.
Business Context
Supports specialized research services and compliance requirements that align content distribution with consumer industry expertise. Enables targeted distribution to appropriate industry specialists while maintaining regulatory boundaries.
Specification Guide
Overview
SectorIndustryEntitlement is an access-control element that restricts a research product's availability based on the sector or industry classification of the research consumer. It is one of several specialised entitlement restrictions that may appear inside an Entitlement within an EntitlementGroup, enabling publishers to align distribution with industry expertise, competitive considerations, and regulatory boundaries.
Usage
Use SectorIndustryEntitlement when access to a product needs to be granted or denied to consumers based on their industry classification. It is placed inside an Entitlement element, and its include/exclude semantics are governed by the parent's includeExcludeIndicator. The element requires one or more SectorIndustry child elements that identify the relevant industry sectors; multiple children allow compound industry-based access patterns. Typical use cases include directing sector-specific research to industry specialists and managing potential conflicts of interest with competitors in the same industry (sources: data-dictionary-2.4 p.55, data-dictionary-2.5.1 p.58, user-guide-2.2 p.39, user-guide-2.3.1 p.40).
Rules
- MUSTSectorIndustryEntitlement must contain one or more SectorIndustry child elements defining the industry scope of the restriction.[RIXML Research Data Dictionary v2.4 p.55] [RIXML Research Data Dictionary v2.5.1 p.58] [RIXML User Guide v2.3.1 p.40]
- INFORMATIVESectorIndustryEntitlement is not required by the Level One compliance subset, which limits entitlement options to region, audience type, and time-based entitlements. Documents targeting Level One typically omit it, although it remains valid in the full schema.[RIXML Level One Addendum v2.2 p.27] [RIXML Level One Addendum v2.3 p.22] [RIXML Level One Addendum v2.5 p.22]
Relationships
- child-ofEntitlement — SectorIndustryEntitlement appears as a child of Entitlement and inherits its include/exclude semantics via includeExcludeIndicator.
- requiresSectorIndustry — Requires one or more SectorIndustry children to identify the industry classifications in scope.
- contained-inEntitlementGroup — Operates within the broader EntitlementGroup structure that aggregates entitlement rules for a product.
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
SectorIndustrySectorIndustryType1..unbounded |
requiredSince 2.1 |
Example
<SectorIndustryEntitlement>
<SectorIndustry> ... </SectorIndustry>
</SectorIndustryEntitlement>Version History
Unchanged since introduction in RIXML 2.1
SectorIndustryEntitlement is present in RIXML 2.2 through 2.5 with stable semantics: an entitlement restriction keyed on industry classification, requiring one or more SectorIndustry children (sources: user-guide-2.2 p.39, user-guide-2.3.1 p.40, data-dictionary-2.4 p.55, data-dictionary-2.5.1 p.58). Across these versions the Level One compliance subset consistently omits the element from its permitted Entitlement children, keeping that subset focused on region, audience-type, and time-based entitlements (sources: level-one-2.2 p.27, level-one-2.3 p.22, level-one-2.5 p.22).
Design Decisions
SectorIndustryEntitlement child elements are not allowed in Entitlement elements for Level One
To simplify entitlement handling and reduce implementation complexity
RIXML Level One Addendum v2.5, p.22
Semantic Relationships
Blocks Action1 relationship
Level One does not allow SectorIndustryEntitlement elements as children of Entitlement
RIXML Level One Addendum v2.5, p.22— Research.Product.Context.ProductDetails.EntitlementGroup.Entitlement