Skip to content

Commit 0e2c41d

Browse files
annefouannefou
committed
draft mapping between FAIR principles and EarthCODE choices
1 parent 106d5cf commit 0e2c41d

File tree

1 file changed

+24
-67
lines changed

1 file changed

+24
-67
lines changed

‎pages/Community and Best Practices/FAIR and Open Science.md‎

Lines changed: 24 additions & 67 deletions
Original file line numberDiff line numberDiff line change
@@ -36,73 +36,30 @@ To move from principles to practice, communities must develop clear, domain-spec
3636

3737
## Interpreting the FAIR Principles for the Earth Observation Community
3838

39-
The FAIR principles provide high-level guidance for ensuring that data, software, and workflows are Findable, Accessible, Interoperable, and Reusable. However, their implementation requires concrete decisions on infrastructure, standards, and governance within specific communities. The Earth Observation (EO) community, including the EarthCODE initiative, follows a FAIR Implementation Profile (FIP) to ensure alignment with these principles.
40-
41-
### Findable
42-
- **F1. (Meta)data are assigned a globally unique and persistent identifier (PID)**
43-
- **EO Implementation**: DOI (Digital Object Identifier) for datasets, ORCID for researchers, and URIs for workflows and software components.
44-
- **EarthCODE Choice**: Uses DOI services such as DataCite for data, Zenodo for software, and ORCID for contributor identification.
45-
46-
- **F2. Data are described with rich metadata**
47-
- **EO Implementation**: INSPIRE metadata profiles, ISO 19115 for geospatial metadata, and STAC for spatiotemporal assets.
48-
- **EarthCODE Choice**: Uses ISO 19115 and STAC metadata to ensure compliance with international geospatial standards.
49-
50-
- **F3. Metadata include the identifier of the data they describe**
51-
- **EO Implementation**: Linking datasets with their DOIs and referencing metadata records through PIDs.
52-
- **EarthCODE Choice**: Ensures STAC and ISO metadata explicitly reference dataset DOIs.
53-
54-
- **F4. (Meta)data are registered or indexed in a searchable resource**
55-
- **EO Implementation**: Discovery through GEOSS, Copernicus Data Space, and Pangeo catalogs.
56-
- **EarthCODE Choice**: Registers datasets in the EarthCODE catalog with indexing via STAC and OGC API.
57-
58-
### Accessible
59-
- **A1. (Meta)data are retrievable using a standardized communications protocol**
60-
- **EO Implementation**: HTTP/HTTPS, OGC API - Features, STAC API.
61-
- **EarthCODE Choice**: Uses cloud-accessible endpoints, including OGC API and STAC-based search.
62-
63-
- **A1.1 The protocol is open, free, and universally implementable**
64-
- **EO Implementation**: Publicly available APIs and persistent data access points.
65-
- **EarthCODE Choice**: Supports open APIs and FAIR-compliant data repositories.
66-
67-
- **A1.2 The protocol allows for an authentication and authorization procedure where necessary**
68-
- **EO Implementation**: OpenID Connect for authentication, OAuth for access control.
69-
- **EarthCODE Choice**: Implements OpenID Connect authentication for secure access to protected data.
70-
71-
- **A2. Metadata remain accessible even when the data are no longer available**
72-
- **EO Implementation**: Persistent metadata records stored in repositories.
73-
- **EarthCODE Choice**: Ensures metadata is retained in DataCite and STAC even if the data is deprecated.
74-
75-
### Interoperable
76-
- **I1. (Meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation**
77-
- **EO Implementation**: JSON-LD, RDF for semantic interoperability.
78-
- **EarthCODE Choice**: Uses JSON-LD in STAC metadata to enhance machine-actionability.
79-
80-
- **I2. (Meta)data use vocabularies that follow FAIR principles**
81-
- **EO Implementation**: GCMD Science Keywords, CF Conventions, Climate and Forecast (CF) metadata.
82-
- **EarthCODE Choice**: Adopts CF Conventions and GCMD for semantic consistency.
83-
84-
- **I3. (Meta)data include qualified references to other (meta)data**
85-
- **EO Implementation**: Linking datasets via DOI, using provenance standards like PROV-O.
86-
- **EarthCODE Choice**: Uses PROV-O to link datasets, workflows, and computational steps.
87-
88-
### Reusable
89-
- **R1. (Meta)data are richly described with a plurality of accurate and relevant attributes**
90-
- **EO Implementation**: Compliance with domain-specific metadata standards (ISO 19115, STAC).
91-
- **EarthCODE Choice**: Ensures datasets include detailed provenance and descriptive metadata.
92-
93-
- **R1.1. (Meta)data are released with a clear and accessible data usage license**
94-
- **EO Implementation**: Creative Commons (CC-BY, CC0) for open data, specific licenses for proprietary data.
95-
- **EarthCODE Choice**: Requires explicit licensing for all datasets and software components.
96-
97-
- **R1.2. (Meta)data are associated with detailed provenance**
98-
- **EO Implementation**: PROV-O and W3C standards for workflow and data lineage tracking.
99-
- **EarthCODE Choice**: Uses PROV-O to ensure reproducibility in data processing.
100-
101-
- **R1.3. (Meta)data meet domain-relevant community standards**
102-
- **EO Implementation**: Compliance with Copernicus, GEO, and OGC standards.
103-
- **EarthCODE Choice**: Adopts OGC, ISO, and STAC standards for metadata and interoperability.
104-
105-
By adopting a FAIR Implementation Profile (FIP), the EarthCODE community ensures that its approach to FAIR is explicit, actionable, and aligned with best practices in Earth Observation data management and processing. This structured implementation enhances data discoverability, interoperability, and reuse while maintaining technical rigor and community consensus.
39+
The FAIR principles provide high-level guidance for ensuring that data, software, and workflows are Findable, Accessible, Interoperable, and Reusable. However, their implementation requires concrete decisions on infrastructure, standards, and governance within specific communities.
40+
41+
| **FAIR Principle** | **EarthCODE FAIR Implementation Profile (FIP) Decisions** |
42+
|-----------------|------------------------------------------------|
43+
| **[F1](https://open.spotify.com/episode/1k4FydzYW1Mx7t9vQN9KOz)** | Use of globally unique, persistent identifiers (e.g., DOIs) for datasets and workflows. |
44+
| **[F2](https://open.spotify.com/episode/2mEUUbAiEQYhMUZwEqgoTN)** | Metadata must comply with domain-specific standards such as ISO 19115, STAC, and DCAT. |
45+
| **[F3](https://open.spotify.com/episode/0WeoKjy8sUN6acOf4vxYyG)** | Metadata must explicitly include dataset identifiers using standardized references. |
46+
| **[F4](https://open.spotify.com/episode/2A1Zn6tOc3g8D7KZHZRygf)** | Data and metadata are indexed in community-recognized repositories (e.g., CMR, GeoNetwork). |
47+
| **[A1](https://open.spotify.com/episode/4kIC0yDgzADCZnxQTEl168)** | Data and metadata must be accessible via open, standardized web protocols such as HTTPS and OGC APIs. |
48+
| **[A1.1](https://open.spotify.com/episode/4cokyE6JL3KFJT5WykJNbE)** | Protocols used must be open, free, and universally implementable. |
49+
| **[A1.2](https://open.spotify.com/episode/0B9NKsy9iSf2g39bV9sKvd)** | Authentication and authorization frameworks (e.g., OpenID Connect) ensure controlled access where needed. |
50+
| **[A2](https://open.spotify.com/episode/1fYL1SNAmott55NxPtYYKd)** | Metadata must remain accessible even if data are no longer available. Persistent repositories ensure this. |
51+
| **[I1](https://open.spotify.com/episode/2nh22FG9i1zy7nbaRpPPWh)** | Use of formal, accessible, and community-adopted knowledge representation languages (e.g., JSON-LD, RDF). |
52+
| **[I2](https://open.spotify.com/episode/2ZOWq5ZHaD8y9xEAjoQk1i)** | Adoption of controlled vocabularies such as CF conventions, GCMD Keywords, and SWEET ontologies. |
53+
| **[I3](https://open.spotify.com/episode/5RLTk8HkOB4iotKVKJj3SL)** | Metadata includes qualified references to related datasets, models, and workflows. |
54+
| **[R1](https://open.spotify.com/episode/4nVoYz4cpPjjoAzKOQFw2D)** | Metadata includes detailed descriptions following domain-specific best practices. |
55+
| **[R1.1](https://open.spotify.com/episode/4jSIyFn2vxlD72meNTZ60i)** | Datasets are released with clear, standardized licenses (e.g., Creative Commons, ODbL). |
56+
| **[R1.2](https://open.spotify.com/episode/49kCkqLbe140FY7aCaYdJF)** | Provenance metadata is recorded using PROV-O or similar standards to ensure reproducibility. |
57+
| **[R1.3](https://open.spotify.com/episode/1rMIfin2bTyRDdBOHZa2PD)** | Data and metadata align with community standards like CEOS, INSPIRE, and OGC. |
58+
59+
60+
61+
By explicitly declaring its choices, the EarthCODE community ensures that its approach to FAIR is transparent, actionable, and aligned with best practices in Earth Observation data management and processing.
62+
This structured implementation enhances data discoverability, interoperability, and reuse while maintaining technical rigor and community consensus.
10663

10764
### References
10865

0 commit comments

Comments
 (0)