Register federation tool

The ELISE action is still improving the Re3gistry software and has supported the preparation of the study and the implementation of the “Federation of registries”, a missing item in the software market.

 Register federation tool The Register federation tool allow registering extensions and other externally governed references codes so that they can be traced and reused by a bigger audience. 

The tool is technologically neutral as it allows reference codes deployed by any system been retrievable in the system .

The only requirement for the extensions to be in the system is to comply with the RoR specifications.

Register federation pictogram


  • It is fully compatible with the Re3gistry (v2 onwards) that provides on-demand RoR descriptor formats.
  • Descriptors files provide metadata and data about the registries and registers and their relationships to be included in the federation in an RDF/XML document.
  • The tool allows searching in the different registers and the items contained in them.
  • The RoR can be accessed using the graphical user interface and/or API.
  • This tool helps to put together information from reference code systems without impacting their technical setting. Only a common descriptor file is needed to be exchanged.
  • The upcoming European Data ecosystems could benefit from this type of cross-cutting technologies to connect them at a semantical level.

RoR descriptor file

RoR stands for Register of Registers.

This specification is based on:

  • The W3C Data Catalog vocabulary (DCAT) is used to model entity registry (dcat:Catalog).
  • The W3C Simple Knowledge Organization System (SKOS) is used to model entity register (skos:ConceptScheme) and item (skos:Concept).

More info on the RoR can be found here.


The Register Federation tool was born as a testbed to put together national extensions of INSPIRE data models in a single place to assure the sharing of codes for a better understanding of the semantics when using data

The testbed comprises:

  • the tool,
  • best practice document and,
  • conformance classes for the RoR Descriptor files.

You can play with the tesbed supporting the INSPIRE implementations that require code list extensions:

Screenshot from  the INSPIRE Register Federation tool