FERIN - Framework for Extensible Registration of Information

Renamed Terms

These terms have been renamed but represent the same or similar concepts. Update your documentation and user interfaces accordingly.

2015 Term	2026 Term	Notes
`Register item series`	`Concept`	Fundamental shift: series now have explicit concept representation
`Technical standard`	`Register specification`	Broader scope, not limited to technical content
`Registry`	`Register system` (preferred)	"Registry" still admitted but "register system" preferred
`RE_Register`	`Register`	Simplified naming without RE_ prefix in conceptual model
`RE_RegisterItem`	`Register item`	Same concept, simplified naming
`RE_ItemStatus`	`Status dimensions`	Fundamentally changed—see Status Model Migration
`deprecated`	removed	Term completely removed; use "invalid" instead

These terms are new in the 2026 edition and represent concepts that didn't exist or weren't explicitly defined in 2015.

Concept plane: Layer for organizing concepts, their versions, statuses, and relations
Content plane: Layer where register items and their changes are stored

Concept: Unit of knowledge created by unique combination of characteristics
Concept version: Representation of a concept at a particular point in time
Concept definition: Concept that describes information requirements and properties
Realised concept: Instance of a concept materialized into concrete information
General concept: Concept corresponding to potentially unlimited number of objects

Object identifier: Non-redirectable identifier permanently assigned to specific object
Functional identifier: Redirectable identifier that always reflects original intent

Managed content: Information in a register item that is governed by the register
Unmanaged content: Information associated with register item NOT governed by register

Commitments: Set of promises made by a register to its users
Register specification: Document describing register purpose, scope, governance, and commitments

Content register: Basic register type with content management capabilities
Concept register: Register with concept plane capabilities
Governed content register: Content register with governance capabilities
Governed concept register: Concept register with governance capabilities
Comprehensive concept register: Full-featured register with all capabilities

These terms from 2015 have been removed in 2026 and should no longer be used.

Removed Term	Reason	Replacement / Notes
`submitted` status	Conceptual change	Proposals are now separate from register items; an item doesn't exist until approved
`deprecated`	Terminology cleanup	Use `invalid` for content that is no longer suitable
XML schema	Technology neutrality	No normative schema; any encoding technology is acceptable
`grg:` XML namespace	Technology neutrality	Implementation-specific; no longer defined by standard

These terms exist in both editions but their meaning or scope has changed.

Term	2015 Meaning	2026 Meaning
Status	Single enumerated value from a fixed set (submitted, valid, invalid, retired, superseded)	Multiple independent dimensions (validity, publication, redaction, deletion) that can be combined
Version	Simple version attribute on register	Multi-layer version model supporting major/minor/patch with semantic versioning options
Relations	Predecessor/successor between items only	Rich relation model with 10+ relation types between concepts and versions
Identifier	Single identifier per item	Object identifier (required) + functional identifier (optional)
Governance	Defined roles and processes	Defined roles, processes, AND commitments framework
Conformance	Three hierarchical classes (Core, Extended, Hierarchical)	Five capability-based register types with modular requirements

Role names remain largely the same but some responsibilities have shifted.

Role	2015	2026	Changes
Register Owner	✓	✓	Now defines commitments
Register Manager	✓	✓	Broader responsibilities for commitments
Control Body	✓	✓	Mostly unchanged
Submitting Organization	✓	→ Proposer	Renamed to "Proposer"; same function
Registry Manager	✓	→ System Manager	Renamed to "System Manager"
Register User	✓	✓	Unchanged

☐ Update all references to "register item series" → "concept"
☐ Update all references to "technical standard" → "register specification"
☐ Update "submitting organization" → "proposer" in documentation
☐ Update "registry manager" → "system manager" in documentation
☐ Remove all uses of "submitted" status
☐ Replace "deprecated" with "invalid" where used
☐ Add new terminology to glossary (concept plane, content plane, commitments, etc.)
☐ Update user-facing documentation with new register type names
☐ Update training materials with new terminology
☐ Review API documentation for terminology changes