The Problem FERIN Solves

Organizations need to manage collections of information—code lists, taxonomies, specifications, reference data—that must remain accessible and usable over time. Traditional approaches often fail because:

  • Information changes but references break
  • There's no clear governance over who can make changes
  • History is lost when updates occur
  • Systems can't agree on what something "means"

FERIN addresses these challenges through a standardized approach to registration that separates meaning from data.

Two Planes: Concept and Content

The fundamental insight of FERIN is that information exists in two planes:

Concept Plane

Where meaning lives. A concept represents an abstract idea or category that can be defined and refined over time. Concepts have definitions, but the definitions can evolve.

Example: The concept of "meter" as a unit of length.

Content Plane

Where data persists. Content represents the concrete representation of concepts at a point in time. Content is versioned, has status, and can be referenced reliably.

Example: "m" as the symbol for meter, valid from 1960 to present.

This separation allows concepts to evolve (e.g., refining the definition of "meter") while preserving the integrity of content that references them (e.g., datasets that use "m" as a unit).

When to Use FERIN

FERIN is appropriate when you need:

NeedFERIN Helps
Persistent identificationReferences that don't break when content changes
Change historyComplete audit trail of all modifications
GovernanceClear roles and processes for managing changes
InteroperabilityStandard framework understood across organizations
ComplianceVerifiable conformance to international standard

FERIN may be overkill for simple lookup tables, configuration data, or information that changes rarely and has no external dependencies.

Real-World Analogy

Think of FERIN like a library catalog system:

  • Concepts are like the abstract idea of a book (title, author, subject)—the metadata that gives it meaning
  • Content is like the physical copy on the shelf—with a specific barcode, location, and status (available, checked out, withdrawn)
  • Governance is the library policy for adding, updating, and removing books from the collection
  • History is the circulation record showing who borrowed what, when, and when it was returned

Key Benefits

Reliable References

Content can be cited with confidence that the reference remains meaningful.

Controlled Evolution

Changes happen through defined processes with clear accountability.

Complete History

Every change is recorded, enabling forensics and rollback understanding.

Standards Compliance

Alignment with ISO 19135 enables interoperability and trust.

Next Steps