| Data INRAE (dataverse) | BMP - ODAM | |||
| descriptive metadata | Structural metadata + Data | |||
| Findable | ||||
| F1 | (meta)data are assigned a globally unique and eternally persistent identifier. | assignment of a DOI + Repository supported by a national research institute | NA | |
| F2 | data are described with rich metadata. | descriptive metadata | Structural metadata | |
| F3 | (meta)data are registered or indexed in a searchable resource. | Metadata records are visible through multiple catalogues | NA | |
| F4 | metadata specify the data identifier. | Yes | NA | |
| Accessible | ||||
| A1 | (meta)data are retrievable by their identifier using a standardized communications protocol. | Yes (RESTful web service ) | Yes (RESTful web service + OpenAPI/Swagger) | |
| A1.1 | the protocol is open, free, and universally implementable. | Yes (http) | Yes (http) | |
| A1.2 | the protocol allows for an authentication and authorization procedure, where necessary. | Yes | Yes | |
| A2 | metadata are accessible, even when the data are no longer available. | Yes (institutional repository) | No | |
| Interoperable | ||||
| I1 | (meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation. | Yes (JSON) - Explicite schema | Yes (TSV for Data, Explicit JSON Schema for Structural metadata) | |
| I2 | (meta)data use vocabularies that follow FAIR principles. | Yes (Darwin Core, schema.org, JSON-LD) | Yes (JSON Schema + ontologies) | |
| I3 | (meta)data include qualified references to other (meta)data. | Yes | ||
| Re-usable | ||||
| R1 | meta(data) have a plurality of accurate and relevant attributes. | Yes | Yes (dictionnary of structural metadata) | |
| R1.1 | (meta)data are released with a clear and accessible data usage license. | Yes | Yes | |
| R1.1 | (meta)data are associated with their provenance. | No | NA | |
| R1.3 | (meta)data meet domain-relevant community standards. | Yes | Yes | |