Custom MIM integration development
Appfront builds integrations with MIM, the Metamodel Informatiemodellering (Information Modelling Metamodel) from Geonovum. Many government bodies record their registers and data in an information model based on MIM. We make sure that model is not just documentation: we read the model in, turn it into schemas, APIs and validation, and check whether the software and the data still match the model when it changes.
What is a MIM integration?
The Metamodel Informatiemodellering, MIM, is a Geonovum standard for how information models are drawn up. It is mainly used for government registers, such as the base registrations, but can be applied more widely. An information model based on MIM describes which objects exist, what data they have, how they relate to each other and what they mean. It can be elaborated in UML or as Linked Data.
Often the model remains documentation. It sits in a modelling tool, and the developers build the database and the API by hand with the model alongside. When the model changes, the software falls behind. A value list in the model has different values than in the database. And anyone who wants to know whether the data in the register matches the model has to work that out themselves.
We build custom because every model and every organisation is different: which modelling tool you use, at what level the model is worked out, which software needs to connect to it, and how often the model changes. MIM is maintained by Geonovum; we make sure your software follows the model rather than running alongside it.
Model as source
The information model, read in from the modelling tool or as Linked Data, as the source for the software.
Schemas and APIs
Database schemas, API specifications and validation rules derived from the model, not copied by hand.
Differences at a glance
An overview of what changes between versions of the model, and where software or data deviate.
How we build your MIM integration
We start with your model: which tool it lives in, at what level of detail, which software needs to connect to it, and where the two currently diverge.
Your information model, modelling tool, level of detail and the software that connects to it.
Object types, attributes, relationships and value lists from the model.
Schemas, API specifications and validation derived from the model, and checks of software and data.
Differences between versions at a glance, plus maintenance when new versions of the model or MIM are released.
What a MIM integration actually does
The components below appear in almost every MIM integration. Which ones you need depends on your model.
Reading in the model
From the modelling tool or as Linked Data.
Schemas
Database schemas derived from the model.
API specifications
API specifications that follow the model.
Validation
Rules for checking data against the model.
Documentation
Readable documentation of objects and definitions.
Versions
Differences between versions of the model.
Who we build a MIM integration for
The integration is intended for organisations where the information model and the software have drifted apart.
Registry administrators
A registry with its own model. Software that follows the model is the core.
Contractors
Many systems holding the same data. Consistent definitions matter most.
Architects and modellers
Models that need to be usable. Deriving schemas from them is what's required.
Software suppliers
Building on a client's model. Checking for deviations is the core.
Technology and integrations
This page is about using information models based on MIM in software. For an Omgevingswet (Environment and Planning Act) information model, see our page on an IMOW integration; for a basic registry, our page on a BAG API integration; and for architecture, our page on microservices architecture. You can read about our approach on building software.
For concept frameworks published and used according to SKOS and NL-SBB, see our page on a SKOS integration.
Why Appfront for your MIM integration?
A model that is only documentation falls behind the software. That's what we build against: the model as the source, schemas and APIs that follow from it, and differences that are visible.
One source
The model drives the software, not the other way round.
Less manual work
Schemas and specifications are derived.
Deviations made visible
Where software or data don't match, it stands out.
Security and privacy in a MIM integration
The integration works with models and sometimes with data from registries, which may contain personal data. Where necessary, data checks run within your own environment, and access is set up per role.
The integration runs in a European data centre or in your own environment, with encrypted storage and daily backups.
Frequently asked questions about a MIM integration
Questions that information architects and suppliers ask before they get started.
The Metamodel Informatiemodellering (Information Modelling Metamodel) is a Geonovum standard for how information models are drawn up. It is mainly used for government registries, and can be worked out in UML or as Linked Data.
It reads in an information model based on MIM, derives schemas, API specifications, validation rules and documentation from it, and checks whether software and data still match the model. That way the model stays the source, even when it changes.
From the tool you use, if it can export the model, or as Linked Data. We'll look at which route suits your tool in the first step.
It can derive an API specification, following the conventions you use for that. We build the API itself from that specification, so that it follows the model. Names and definitions in the API then match those in the model, which helps consumers.
The integration shows what changes between versions, and which schemas, specifications and software need to be adjusted as a result. That way your software doesn't quietly fall behind. A change that affects existing data, such as an attribute becoming mandatory, is highlighted, so you know what needs to be filled in.
Yes. Data in a registry or database is checked against the rules in the model, such as mandatory fields and code lists. Deviations are listed in an overview, by object type and by rule, so the registry's administrator knows where to start.
For organisations with an information model that changes often or that several systems connect to, and for suppliers who build software on a model owned by their client.
Software that follows the information model?
Tell us which model you have, which tool it lives in and which software connects to it. We'll show you what the integration looks like.