YesNoEnum
RIXML 2.5 Enumeration
A simple boolean enumeration providing standardized Yes/No values used throughout the RIXML schema for binary attribute values. This enumeration ensures consistent representation of true/false, enabled/disabled, and similar binary states across all schema elements requiring boolean classification.
Usage
Applied as attribute values across numerous RIXML elements requiring binary classification, including primaryIndicator, external, emergingIndicator, and many other boolean attributes throughout the schema structure.
Business Context
Fundamental for data consistency and processing automation in research distribution systems. Enables reliable boolean logic implementation and ensures standardized binary value representation across diverse research content types.
Where It Fits
Definition
| Base Type | string |
Enumeration Values
No |
| No |
Negative confirmation or denial response to a boolean question or condition Use to indicate a false, negative, or denial state for any yes/no field in the schema [RIXML Research Data Dictionary v2.5.1 p.14] ActiveSince 2.1 |
Yes |
| Yes |
Positive confirmation or affirmative response to a boolean question or condition Use to indicate a true, positive, or affirmative state for any yes/no field in the schema [RIXML Research Data Dictionary v2.5.1 p.14] ActiveSince 2.1 |
Examples
<!-- Example usage of YesNoEnum enumeration -->
<element type="YesNoEnum">No</element>Version History
Unchanged since introduction in RIXML 2.1
Business Rules
When a required tag has enumerated choices, one of the acceptable values must be selected even if no value is desired
Semantic Relationships
Requires4 relationships
At least one Resource within a product must have primaryIndicator set to Yes to identify the primary resource
RIXML Research Data Dictionary v2.5.1, p.40— primaryIndicator (Required, YesNoEnum)
For Level One compliance, the Organization primaryIndicator attribute must be present and set to Yes
RIXML Level One Addendum v2.5, p.6— Research.Product.Source.Organization
Though the primaryIndicator attribute is optional in the full schema, Level One compliance requires it for PersonGroupMember
RIXML Level One Addendum v2.5, p.7— Research.Product.Source.Organization.PersonGroupMember
If this particular RIXML Research instance document is reaching an organization outside the publisher, the external value should be Yes
RIXML Level One Addendum v2.5, p.11— Research.Product.Context
Mutually Exclusive With1 relationship
In primaryIndicator attributes, Yes and No values are mutually exclusive - an element cannot be both primary and non-primary simultaneously
RIXML Implementation Guide v2.5.1, p.26— Primary vs. non-primary
Constrains2 relationships
Level One restricts ProductFocus primaryIndicator to Yes because only one ProductFocus is allowed
RIXML Level One Addendum v2.5, p.21— Research.Product.Context.ProductDetails.ProductFocus
Only one StatusInfo element may have currentStatusIndicator set to Yes at any time
RIXML Level One Addendum v2.5, p.24— Research.Product.StatusInfo