CountryEntitlement
RIXML 2.5 Element
Geographic entitlement restriction based on the country location of research consumers. Enables compliance with jurisdictional regulations and licensing agreements by controlling content distribution geographically.
Usage
Used within Entitlement elements to specify geographic access restrictions. Requires one or more Country child elements to define the geographic scope. Works with include/exclude logic from parent Entitlement element.
Business Context
Critical for compliance with international securities regulations and licensing agreements that restrict research distribution to specific jurisdictions. Essential for global research providers managing complex regulatory requirements.
Specification Guide
Overview
CountryEntitlement is a geographic access-control element that restricts or permits research distribution based on the country location of the research consumer. It exists to support compliance with jurisdictional regulations, licensing agreements, export controls and cross-border research-distribution rules, and appears as one of the geographic scoping choices within an Entitlement container.
Usage
Place CountryEntitlement inside an Entitlement (which itself sits within an EntitlementGroup under ProductDetails). It must contain one or more Country child elements identifying the in-scope jurisdictions. The semantics of the country list — whether the listed countries are permitted or denied access — are governed by the parent Entitlement's includeExcludeIndicator (sources: user-guide-2.2 p.39, user-guide-2.3.1 p.39). Multiple Country children may be listed to build regional inclusion sets or country exclusion lists, and several CountryEntitlement elements can be combined with other entitlement types (e.g. RegionEntitlement, AudienceTypeEntitlement) to express layered access logic.
Rules
- MUSTCountryEntitlement must contain at least one Country child element specifying the geographic scope.[RIXML Research Data Dictionary v2.4 p.54] [RIXML Research Data Dictionary v2.5.1 p.57] [RIXML User Guide v2.3.1 p.39]
- INFORMATIVECountryEntitlement is not required by Level One compliance; Level One restricts entitlement expression to region, audience-type and time entitlements, so CountryEntitlement is typically omitted in Level One documents (it MAY still appear at higher compliance levels).[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
- requiresCountry — CountryEntitlement requires one or more Country child elements to define its geographic scope.
- contained-byEntitlement — CountryEntitlement appears as a child of Entitlement, whose includeExcludeIndicator determines whether the listed countries are included or excluded.
- ancestorEntitlementGroup — Sits within the broader EntitlementGroup framework used to express bundled access 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
Country(complex)1..unbounded |
requiredSince 2.1 |
Example
<CountryEntitlement>
<Country> ... </Country>
</CountryEntitlement>Version History
Unchanged since introduction in RIXML 2.1
CountryEntitlement has been present throughout the RIXML 2.x lifecycle (documented in versions 2.2 through 2.5) with stable semantics: a container for one or more Country elements used within Entitlement. Across all versions surveyed, the Level One conformance subset omits CountryEntitlement from its allowed entitlement children in favour of a simpler region/audience/time model (sources: level-one-2.2 p.27, level-one-2.3 p.22, level-one-2.5 p.22).
Design Decisions
CountryEntitlement 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 CountryEntitlement elements as children of Entitlement
RIXML Level One Addendum v2.5, p.22— Research.Product.Context.ProductDetails.EntitlementGroup.Entitlement