Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Mechanisms

These Mechanisms are under active development

M1.: API-based LDT Resource Access

R1.1, R1.3, R1.4, R2.1, R2.2, R2.3, R2.5, R2.6

Use standard APIs and service interfaces, including where relevant:

  • OGC API Features;

  • OGC API Processes;

  • OGC 3D Tiles;

  • REST APIs;

  • NGSI-LD APIs;

  • IoT transmission protocols;

  • database connectors.

Expose, where relevant:

  • datasets;

  • transformed data;

  • simulation outputs;

  • model inputs;

  • model services.

This mechanism should reference MIM0 for data access and MIM7 for geospatial access. The MIM8-specific point is that these resources must be accessible for orchestration inside LDT workflows.

M2: Standardised Data and Output Formats

R2.2, R3.3, R5.1, R6.1, R6.2, R6.3, R6.4, R6.5, R6.6, R6.7

Use standard or widely adopted formats, including where relevant:

  • geospatial data: GeoJSON, CityJSON, CityGML, GeoTIFF;

  • 3D and visualisation data: 3D Tiles, CityJSON, pixel streaming.

  • simulation data: NetCDF, HDF5;

  • semantic data: RDF, OWL, JSON-LD;

  • IoT/context data: NGSI-LD, FIWARE Smart Data Models.

  • cloud-optimised formats: COG (Cloud Optimised GeoTIFF), Parquet

Note

MIM2 is relevant for representation and semantics, while MIM7 is relevant for geospatial formats, and MIM8 is concerned with whether these formats can support model execution, simulation outputs, and visualisation.

M3: Model-as-a-Service

R3.1, R3.2, R3.3, R3.4, R3.6, R3.7

Expose deterministic, simulation, AI or analytical models through service interfaces, including where relevant:

  • OGC API Processes;

  • REST APIs;

  • containerised model services;

  • model registries;

  • MCP-style tool interfaces for LLM or agentic AI interaction.

Enable:

  • local or remote model execution;

  • reuse of models across workflows, domains or LDTs;

  • clear description of required input data;

  • clear description of generated outputs;

  • versioning and provenance.

This mechanism is the core of MIM8 by promoting the reuse of models across domains, communities, use cases, and LDTs.

M4: LDT Workflow Orchestration

R1.5, R2.4, R3.5, R3.8, R4.1, R4.2, R4.3, R4.4, R4.5, R4.6

Use an orchestration layer or workflow mechanism that can:

  • connect data sources to models;

  • pass outputs from one step to another;

  • validate required inputs before model execution;

  • monitor workflow execution;

  • record provenance; for instance through Distributed Ledger Technologies (DLTs) or Non-Fungible Tokens (NFT)

  • support scenario comparison.

Possible implementations include:

  • workflow engines;

  • LDT orchestration platforms;

  • dataflow tools;

  • scenario managers;

  • controlled agent-based orchestration.

M5: Multi-view Output and Visualisation Access

R5.1, R5.2, R5.3, R5.4

Expose outputs through formats or services that can be consumed by different visualisation tools, including:

  • 2D maps;

  • GIS;

  • 3D scenes;

  • dashboards;

  • reports;

  • VR/AR environments;

  • natural-language interfaces.

Use, where relevant:

  • OGC 3D Tiles;

  • CityJSON;

  • GeoJSON;

  • raster/vector layers;

  • dashboard APIs;

  • scenario-output packages.

PreviousCapabilities and RequirementsNextUse Cases

Last updated