Glossary

An operation that changes the state or content of a register.

Interpretation: FERIN defines required actions (add, invalidate, supersede, etc.) and optional actions (redaction, deletion, etc.).

The action of including a new concept or register item in a register.

Interpretation: Requires governance approval in governed registers. Creates change history.

A formal request to reconsider a decision made by the Control Body.

Interpretation: Appeals should be documented with their outcome.

An abstract idea or category that can be defined and that exists in the concept plane.

Interpretation: Concepts represent "what something means" independent of any specific representation.

A statement that describes the meaning of a concept.

Interpretation: Can evolve over time through concept versions.

The abstract layer where concepts and their meanings exist.

Interpretation: Separate from the content plane where data is stored.

A structured set of concepts related to each other.

Interpretation: Common patterns: generalization-specialization, whole-part, sequential.

A specific version of a concept definition at a point in time.

Interpretation: Created when a definition changes significantly.

The layer where concrete register items and their data exist.

Interpretation: Content is versioned, has status, and can be referenced.

The entity responsible for reviewing and deciding on proposals.

Interpretation: Should be separate from the Manager role in high-risk registers. For low-risk registers, combining roles may be acceptable. See Risk Management for guidance.

A change that corrects an error in existing content.

Interpretation: May or may not require a new version depending on significance.

The action of permanently removing content from a register.

Interpretation: Use carefully—breaks references. Consider invalidation instead.

An identifier that always retains its original intent by enabling its association to be redirectable and change over time.

Interpretation: Must support hierarchical specification (URI, URN, URL). Used for semantic addressing. Required for concepts, concept versions, register items, register item classes, and changes.

The system of rules, practices, and processes for managing a register.

Interpretation: Includes roles, responsibilities, and decision-making processes.

The action of marking content as no longer valid for use.

Interpretation: Content remains accessible for history but should not be used.

Content that is subject to governance and change management.

Interpretation: Distinct from administrative information about the register itself.

An identifier that identifies an object where the association is non-redirectable and does not change over time.

Interpretation: Permanently assigned to a specific object. Only concerned with uniqueness. Required for concepts, concept versions, register items, register item classes, and changes.

A formal request to add, change, or remove content in a register.

Interpretation: Requires justification and goes through governance approval.

The entity that submits a proposal for changes to the register.

Interpretation: Can be any authorized stakeholder in governed registers.

The status of content that is visible and available to users.

Interpretation: Content can be valid but unpublished (e.g., during review).

A concept that is linked to specific register item content.

Interpretation: The bridge between concept plane and content plane.

The action of hiding or removing sensitive content.

Interpretation: Can be soft delete, hard delete, or access control based.

A managed collection of information with defined governance.

Interpretation: Has an owner, follows a specification, implements FERIN framework.

A concrete piece of content in a register.

Interpretation: Has identifier, status, attributes, and is managed through actions.

A category of register items with common attributes.

Interpretation: Defines the schema for a type of content.

The entity responsible for day-to-day register operations.

Interpretation: Coordinates proposals, maintains documentation, reports to Owner.

The entity accountable for the register's existence and direction.

Interpretation: Approves specification, assigns Manager, makes final decisions.

A document defining a register's scope, governance, and commitments.

Interpretation: Required for all FERIN-compliant registers.

The technical infrastructure that implements the register.

Interpretation: Database, API, user interface, etc.

A defined relationship between concepts or register items.

Interpretation: Types: has concept, instance of, has definition, supersedes, inherits, has part.

The state of a concept or register item.

Interpretation: Primary statuses: valid/invalid, published/unpublished, superseded.

A change that has major impact on the use of content.

Interpretation: Requires a new version. Contrast with non-substantive change.

The transfer of responsibility for a register to another entity.

Interpretation: Part of decommissioning or organizational change.

The action of replacing content with a newer version.

Interpretation: Creates link from superseded to superseding item.

The entity responsible for technical operation of the register system.

Interpretation: Maintains infrastructure, ensures availability, implements changes.

Content not subject to governance processes.

Interpretation: May transition to managed if it becomes subject to governance.

The action of removing content from public visibility.

Interpretation: Content still exists but is hidden from normal queries.

The status of content that is approved and appropriate for use.

Interpretation: Contrast with invalid—content should not be used.

A specific snapshot of content at a point in time.

Interpretation: Versions enable history, comparison, and rollback understanding.