HMC
Earth and Environment
Community Wiki

User Tools

Site Tools

Trace: • f1.0 • m3.0
wiki:basic_recommendations

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
wiki:basic_recommendations [2025/08/05 10:39] – esoedingwiki:basic_recommendations [2025/08/31 18:00] (current) – esoeding
Line 9: Line 9:
   * Common and agreed procedures to refer to shared entities and metadata values, particularly through the use of **metadata of persistent identifiers** (PID), to reduce redundancy and improve consistency in referencing key entities such as people, organizations, instruments, and datasets (**K**) //(AP: suggestion for key)//.   * Common and agreed procedures to refer to shared entities and metadata values, particularly through the use of **metadata of persistent identifiers** (PID), to reduce redundancy and improve consistency in referencing key entities such as people, organizations, instruments, and datasets (**K**) //(AP: suggestion for key)//.
   * Harmonized use of **semantic resources**, including controlled vocabularies and mapping tables, to standardize metadata element names and their meanings, reduce ambiguity, and ensure consistent interpretation across disciplines and systems (**S**). //[I would still recommend to merge semantics with mandatory and optional metadata elements, because these are closely related. Mingeling woth semantics only makes sense with very important information, which should be defined beforehand and applied accordingly.]//   * Harmonized use of **semantic resources**, including controlled vocabularies and mapping tables, to standardize metadata element names and their meanings, reduce ambiguity, and ensure consistent interpretation across disciplines and systems (**S**). //[I would still recommend to merge semantics with mandatory and optional metadata elements, because these are closely related. Mingeling woth semantics only makes sense with very important information, which should be defined beforehand and applied accordingly.]//
-  * Agreements on **mandatory and optional metadata elements**, covering both domain-independent and domain-specific needs, to support accurate description, discovery, exchange, and reuse of data across infrastructures, user communities, and tools (**M**?). +  * Agreements on **mandatory and optional metadata elements**, covering both domain-independent and domain-specific needs, to support accurate description, discovery, exchange, and reuse of data across infrastructures, user communities, and tools (**M**?). //[I don't think this is possible. If the PIDs are managed well, these are the mandatory information. Everything else is domain specific, can not be mandatory, and but must be dealt on a disciplinary case by case basis.]//
   * Common metadata or **exchange formats**, such as DataCite, DCAT, or ISO 19115, to ensure consistent structuring and exchange of metadata across systems (**E**) //[I still recommend to merge fromats witrh interfaces as the topic interface. This should indeed cover formats and protocols, that we need agreements about]//   * Common metadata or **exchange formats**, such as DataCite, DCAT, or ISO 19115, to ensure consistent structuring and exchange of metadata across systems (**E**) //[I still recommend to merge fromats witrh interfaces as the topic interface. This should indeed cover formats and protocols, that we need agreements about]//
   * Common data **exchange containers**, such as FAIR Digital Objects or DataCrates, to enable machine-actionable reuse and portability (**C**).   * Common data **exchange containers**, such as FAIR Digital Objects or DataCrates, to enable machine-actionable reuse and portability (**C**).
wiki/basic_recommendations.txt · Last modified: by esoeding