CACrown ArchivesThe cinema collection
Menu
Research dossier · General Reference

Model-driven interoperability

approach to achieve interoperability between systems and enterprises by using model-driven development

Cross-disciplinary reference desk with index cards, atlas, dictionary and catalogue
General referenceInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionDec 13, 2025
Entity authorityQ6888235
Source-derived summary

Model-driven interoperability (MDI) is a methodological framework, which provides a conceptual and technical support to make interoperable enterprises using ontologies and semantic annotations, following model driven development (MDD) principles.

Overview

The initial idea of works on MDI, was the application of model-driven methods and techniques for solving interoperability problems from business level down to data level.

The three main ideas of model driven interoperability (MDI) approach are:

Interoperability should be achieved at different levels: Business, knowledge, application and data.

The main idea is to follow a model driven engineering (MDE) approach. Therefore, it is promoted a systematic use of models as primary engineering artefacts throughout the engineering life cycle combined with both domain-specific modelling languages and transformation engines and generators.

The use of ontologies and semantic annotations is needed in order to perform model transformation from enterprise level to code level.

History

MDI was initiated in 2004 with the beginning of two important research projects:

INTEROP NoE (Interoperability Research for Networked Enterprises Applications and Software Network of Excellence, FP6-IST 508011).

ATHENA IP (Advanced Technologies for interoperability of Heterogeneous Enterprise Networks and their Applications Integrated Project) (FP6-IST-507849).

Both projects were supported by the European Commission. These two projects worked on both the definition of a methodological framework and the application of MDI on concrete cases.

Editorial summary

Begin with the source’s own compact description: “Model-driven interoperability” is approach to achieve interoperability between systems and enterprises by using model-driven development. The dossier treats that line as a proposition to test through Model-driven, interoperability and approach, not as a finished interpretation.

Editorial reviewA practical starting point whose main value is the path it opens into stronger specialist and primary sources. The current lead gives the account dated anchors—2004—that can be checked directly. The selected authority fields contribute no independent date. For this dossier, Model-driven, interoperability and approach is the immediate research focus.
Editorial analysis

Why this record matters

The phrase “approach to achieve interoperability between systems and enterprises by using model-driven development” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.

Evidence profile

Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Dec 13, 2025. The linked authority identifier is Q6888235. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2004.

Critical limits

A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.

Best used for
  • Subject orientation
  • Search vocabulary
  • Locating named sources
Verify next

The closest primary source, responsible institution and strongest cited specialist reference.

Three-step research path

  1. Establish the record: confirm the title “Model-driven interoperability”, its source revision and the description used here.
  2. Expand the search: follow Model-driven interoperability primary sources, Model-driven interoperability archive and Model-driven research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Model-driven interoperability”?
  2. What terminology or title could unlock a more precise catalogue search?
  3. Which cited source is closest to the event, object or claim?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from Model-driven interoperability” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.