HMC
Earth and Environment
Community Wiki

This is an old revision of the document!

---

Introduction

HMC Vision and Mission

FAIR building blocks

• K0 Use PID Metadata (K)
• S0 Use Semantic (S) Resources
  • S1.0 Decompose compolex semantic metadata according to community-recognized frameworks
    • S1.1 Measurable quantities
    • S1.2 Measurement devices
  • S2.0 Annotate your metadata with terms from community-recognized controlled vocabularies
    • S2.1 Define your needs and derive requirements for controlled vocabularies
    • S2.2 Reuse existing controlled vocabularies wherever possible
    • S2.3 Evaluate the suitability of controlled vocabularies based on defined criteria and available tools
    • S2.4 Adopt recommended controlled vocabularies
    • S2.5 Adopt recommended terminology services
    • S2.6 Carefully consider how to deal with missing terms
  • S3.0 Use metadata schemata that are semantically usable
    • S3.1 Use Schema.org compliant code with datasets
    • S3.2 Repos should implement Schema.org compliant code
    • S3.3 ETC
  • S4.0 Ensure to address essential criteria when building a vocabulary
• I0 Provision of Interfaces (I) and Exchange Formats
• B0 Which data do we want to harmonize
• C0 Define Data Containers
• F0 Implementation of Data Formats
  • F1.0 NETCDF Guidelines
• L0 Use Licenses
• Q0 Implement Quality Information
• P0 Track Provenance
• R0 Define Stakeholder Roles
• V0 Value Data Publications

---

Implementation examples

---

Stakeholder Instructions

* Instructions for Re-using data

---

* Glossary

---

* Template for recommendations

Introduction

HMC Vision and Mission

Implementation examples

FAIR building blocks

• K0 Use PID Metadata (K)
• S0 Use Semantic (S) Resources
  • S1.0 Decompose compolex semantic metadata according to community-recognized frameworks
    • S1.1 Measurable quantities
    • S1.2 Measurement devices
  • S2.0 Annotate your metadata with terms from community-recognized controlled vocabularies
    • S2.1 Define your needs and derive requirements for controlled vocabularies
    • S2.2 Reuse existing controlled vocabularies wherever possible
    • S2.3 Evaluate the suitability of controlled vocabularies based on defined criteria and available tools
    • S2.4 Adopt recommended controlled vocabularies
    • S2.5 Adopt recommended terminology services
    • S2.6 Carefully consider how to deal with missing terms
  • S3.0 Use metadata schemata that are semantically usable
    • S3.1 Use Schema.org compliant code with datasets
    • S3.2 Repos should implement Schema.org compliant code
    • S3.3 ETC
  • S4.0 Ensure to address essential criteria when building a vocabulary
• I0 Provision of Interfaces (I) and Exchange Formats
• B0 Which data do we want to harmonize
• C0 Define Data Containers
• F0 Implementation of Data Formats
• L0 Use Licenses
• Q0 Implement Quality Information
• P0 Track Provenance
• R0 Define Stakeholder Roles
• V0 Value Data Publications

---

Stakeholder Instructions

* Instructions for Re-using data

Schema.org

---

* Glossary

---

* Template for recommendations