As a “simple list” of objects (individuals, businesses) with stable attributes, a register does not seem impressive at first glance, compared to other components of an information system.

However, as a central reference for operational processes, particularly administrative processes, a register raises multiple issues. Firstly, it often has numerous users who do not necessarily share the same objectives and agenda. Its expected level of service is high, as it combines data quality and interoperability needs. Reaching this level despite heterogeneity of uses requires specific properties, and a strong organization to ensure developments and day-to-day activities. Finally, a register can be seen as a powerful and dynamic system that relies on rigorous semantics, a legal architecture and a solid technical infrastructure. Its lifecycle is based on standardized data flows, a wide range of services, and quality control supported by a dedicated team. Managing such a system implies multi-level decision making, in other words a governance of the register. All this is very far from the “simple list”...