> For the complete documentation index, see [llms.txt](https://oasc.gitbook.io/mims-specification-8/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oasc.gitbook.io/mims-specification-8/mim1-interlinking-data.md).

# MIM1: Interlinking Data

OASC MIM1: Interlinking Data

## Introduction

This MIM helps cities and communities address the challenges of disconnected data sources spread across diverse systems and contexts.

## Objectives

This MIM supports interlinking datapoints across domains, departments or use cases. It aims to realise semantic interoperability\* across potentially different data models and ontologies, by providing mappings, translations, linking databases, etc. 

It also includes a consistent set of identifiers of individual instances of each entity, so that data about any entity can be combined with other data referring to that entity, and every instance of that entity, with the certainty that they point to the same thing.

\*Note: semantic interoperability is also covered by other MIMs, in particular MIM2.

## Capabilities and Requirements

C1: Entities are identified using unique identifiers

| C1 Requirements                                                                                                                                                                               |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| R1.1: Every entity within the system has a  unique identifier                                                                                                                                 |
| R1.2: There exists a way to retrieve information about an entity by looking up the identifier within a system                                                                                 |
| R1.3: if a unique identifier points to the same entity within multiple systems that adhere to MIM1, it is possible to derive the way to look up information about it in each of these systems |
| R1.4: if a multiple unique identifiers point to the same entity, it is possible to map them                                                                                                   |

C2: It is possible to create identifiers that are persistent over time

| C2 Requirements                                           |
| --------------------------------------------------------- |
| No requirements have been defined yet for this capability |

C3: When retrieving information about an entity, it should be possible to retrieve the semantics describing that information (Typing)

<table><thead><tr><th valign="top">C3 Requirements</th></tr></thead><tbody><tr><td valign="top">No requirements have been defined yet for this capability</td></tr><tr><td valign="top"></td></tr></tbody></table>

{% hint style="info" %}
This MIM is currently still under heavy development and information is therefore limited. Members that are interested in further developing this MIM are invited to subscribe to this Working Group using the form on <https://oascities.org/minimal-interoperability-mechanisms/>
{% endhint %}