wiki:s0
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| wiki:s0 [2025/08/01 12:57] – [Contributors] esoeding | wiki:s0 [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | **Recommendation S0 ** | ||
| - | |||
| - | ======Recommendation for implementing harmonized semantic concepts in data infrastructures and products====== | ||
| - | |||
| - | =====Description===== | ||
| - | |||
| - | Status: Under development, | ||
| - | |||
| - | =====Motivation for this Recommendation ===== | ||
| - | The use of shared, community-endorsed vocabularies for metadata annotation is key to ensuring unambiguous and standardized descriptions of data. This not only supports the alignment and integration of heterogeneous datasets but also enhances data discovery and reuse. Crucially, such practices form the foundation for machine-readability of metadata, which is essential for achieving semantic interoperability. | ||
| - | |||
| - | Within the Helmholtz research field Earth and Environment, | ||
| - | |||
| - | =====Recommendation summary ==== | ||
| - | Data infrastructures and data hosts—such as data repositories, | ||
| - | |||
| - | /*Kommentar Doro: eigentlich sprechen wir auch die Entwickler oder " | ||
| - | =====Binding Convention ===== | ||
| - | |||
| - | |||
| - | ^ ^ mandatory | ||
| - | ^ Helmholtz FAIR Principle| | ||
| - | |||
| - | =====Precondition for Implementation ===== | ||
| - | The basis for a comprehensive metadata annotation is that the data is provided with sufficient and structured metadata and that there is agreement about which metadata is considered essential in communities. Standardized metadata categories and structures enable the annotation with identifiable terms from recognized controlled vocabularies, | ||
| - | |||
| - | Metadata annotation with semantic ressources is only effective if there is consensus within a research community about which controlled vocabularies or other semantic resources best meet the community' | ||
| - | =====Contributors===== | ||
| - | |||
| - | Dorothee Kottmeier (Lead) | ||
| - | |||
| - | =====Content===== | ||
| - | |||
| - | ====1. Explanation of the Background and Benefits of the Recommendation ==== | ||
| - | |||
| - | Consistent implementation of semantic concepts across a research community is essential for advancing the FAIR principles—particularly Findability, | ||
| - | |||
| - | In the current German research landscape, where environmental data are fragmented, inconsistent in quality, and lack standard formats, consistent semantic annotation is key to improving interoperability. Community agreement on essential metadata elements ensures data are well-described, | ||
| - | |||
| - | **What is meant with „controlled vocabulary“ in these recommendations? | ||
| - | |||
| - | There are different types of structured terminologies used in semantic data annotation, each offering varying levels of complexity and expressiveness. According to Le Franc et al. (2019), these can be understood as part of a spectrum of controlled vocabularies, | ||
| - | |||
| - | • A **glossary** is a simple, alphabetically ordered list of terms from a specific domain, each accompanied by a definition. It supports a shared understanding of terminology within a community. | ||
| - | |||
| - | • A **taxonomy** is a controlled vocabulary with a hierarchical structure. Terms are related via broader–narrower (parent–child) relationships, | ||
| - | |||
| - | • A **thesaurus** builds upon a taxonomy by incorporating not only hierarchical but also associative (e.g., related terms) and equivalence relationships (e.g., synonyms or preferred terms). Thesauri are useful for enhancing semantic navigation and improving information retrieval. | ||
| - | |||
| - | • An **ontology** represents the most expressive and formal type of controlled vocabulary. While it may include terms and structures from glossaries, taxonomies, or thesauri, it adds formal semantics through logical relationships defined in machine-readable languages (e.g., OWL, Description Logic). Ontologies enable reasoning, inference, and advanced semantic interoperability across systems. | ||
| - | |||
| - | In line with Le Franc et al. (2019), we explicitly consider ontologies to be part of the family of controlled vocabularies addressed in this recommendation. Depending on the use case and required level of formality, different types of controlled vocabularies may be appropriate for metadata annotation and semantic integration. | ||
| - | |||
| - | ====2. Possible alternative solutions==== | ||
| - | |||
| - | - | ||
| - | ====3. Consideration of the advantages and disadvantages of implementing the recommendation==== | ||
| - | |||
| - | | **Aspect** | ||
| - | |--------------------------|--------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| | ||
| - | | **Quality of content** | ||
| - | | **Interoperability** | ||
| - | | **Sustainability** | ||
| - | | **Technical availability** | Supports automation, validation, and FAIR-aligned workflows. | ||
| - | | **Community fit** | Encourages reuse of existing vocabularies and avoids duplication of effort. | ||
| - | | **Funding and effort** | ||
| - | |||
| - | > **Note:** While the benefits of standardized semantic practices are clear, their successful implementation depends on collective coordination, | ||
| - | ====4. The Recommendation==== | ||
| - | |||
| - | Data stewards, archivists, and tool developers—including those responsible for systems used at various stages of the data lifecycle, such as data acquisition, | ||
| - | |||
| - | Developers of data portals, knowledge graphs, and discovery tools should incorporate these controlled vocabularies and ontologies into their software environments. This enhances machine-readability, | ||
| - | |||
| - | To enable seamless semantic annotation from the start, data producers need to be supported through targeted training and awareness initiatives that emphasize the use of community-endorsed vocabularies, | ||
| - | |||
| - | ====5. Naming of communities that have already implemented the recommendation==== | ||
| - | |||
| - | ====6. Documentation of the test to validate correct implementation==== | ||
| - | |||
| - | |||
| - | |||
| - | ====7. Examples of Instances==== | ||
| - | |||
| - | ====8. Further Information==== | ||
| - | |||
| - | ===References=== | ||
| - | |||
| - | - Wilkinson, M. D., Dumontier, M., Aalbersberg, | ||
| - | |||
| - | - Le Franc, Y., Hettne, K., & Ó Carragáin, E. (2019). *D2.5 FAIR Semantics Recommendations Second Iteration*. Zenodo. https:// | ||
| - | |||
| - | |||
| - | ===Relevant Community Recommendations=== | ||
| - | |||
| - | ====9. History of this document==== | ||
wiki/s0.1754053024.txt.gz · Last modified: by esoeding
