I-ADOPT

FAIR Data Integration Semantic interoperability

I-ADOPT Case Study Infobox

Author: Barbara Magagna (@mabablue)
Last updated: 2025-03-01
Mapping Type:
Status of this case study:

Express which specification was used when mapping in general, but this case study is to be able to express that a mapping has been done based on I-ADOPT

Domain¶

Potentially any domain, but with an initinal focus on environmental domain

Purpose of the mapping¶

Semantic interoperability, Data integration.

Other purpose of the mapping¶

None given.

Type of mapped resources¶

SKOS concepts about variables (observable properties) mapped based on the I-ADOPT Framework ontology. This case study has different user stories:

Use case 1: direct mappings of description components

I-ADOPT use case 1

Use case 2: Indirect mappings of description components

2a: related mappings of description components: I-ADOPT use case 2a

2b: description components mapped to the same reference semantic artefacts I-ADOPT use case 2b

2 c: no explicit mappings existing, but automatic mappings based on term matches I-ADOPT use case 2c

Use case 3: Description components mapped between a variable and a blank node

I-ADOPT use case 3

Links to an existing mappings¶

https://vocab.nerc.ac.uk/mapping/I/1740186/

Tools used for creating the mapping¶

Manual procedure. We are about developing SQPARQL queries to perform mappings. Alexandra Kokkinaki will provide those.

Type of mapping relations¶

Entity mappings based on the I-ADOPT Framework.

Examples (samples) of different types of mapping implementations¶

--