📜 Introduction
About
This is an ontology of the FAIR Implementation Profiles (FIP) for the FAIR principles. This diagram shows the general structure of this model:
FSR Typology
This diagram shows the typology of FAIR Supporting Resources (FSRs):
🏷 Classes
| class | description | np |
|---|---|---|
|
A service that mediates access to digital objects according to specifed conditions.
| ||
|
A FAIR Supporting Resource that is available for use.
| ||
|
A FAIR-enabling resource that is available for use
| ||
|
A specification of how messages are structured and exchanged.
| ||
|
A specification consisting of a set of rules that define how (meta)data elements or attributes from one schema can be aligned and mapped to (meta)data elements or attributes in another schema that share the same constraints and thus share the same semantic role.
| ||
|
A data policy that specifies legal restrictions on the reuse of the data.
| ||
|
A digital object type is a classification of digital objects with respect to their informational functions to specify the nature of the digital object and the operations that can be performed on it.
| ||
|
A registry designed to collect, provide access to, and enable searching of data within a particular domain or subject area
| ||
|
A service that provides a user-friendly interface for easy editing of metadata, vocabularies or crosswalks.
| ||
|
An early-stage community committed to adopting and promoting FAIR principles for its data and services from the outset.
| ||
➡ Properties
| property | description | np |
|---|---|---|
|
Specifies how many years a resource is preserved according to a preservation policy
| ||
|
Considerations that led to a given FIP declaration
| ||
|
Connects a FIP declaration to the community that made the declaration
| ||
|
Connects a FIP declaration to the case study it refers to.
| ||
|
Connects a FIP declaration to the digital object type it applies to
| ||
|
Connects a FIP declaration to the resource that the community thereby declares to currently use
| ||
|
Connects a FIP declaration to the resource that the community thereby declares to plan to develop
| ||
|
Connects a FIP declaration to the resource that the community thereby declares to plan to replace in the future. The same declaration should also state a resource that the community declares to plan to use instead (with fip:declares-planned-use-of).
| ||
|
Connects a FIP declaration to the resource that the community thereby declares to plan to use in the future
| ||
|
Connects a FAIR Enabling Resource with a FAIR Supporting Software.
| ||
🫧 Named individuals
| individual | class | description | np |
|---|---|---|---|
|
Which standardized communication protocol do you use for datasets?
| |||
|
Which standardized communication protocol do you use for metadata records?
| |||
|
Which authentication & authorisation technique do you use for datasets?
| |||
|
Which authentication & authorisation technique do you use for metadata records?
| |||
|
Which metadata longevity plan do you use?
| |||
|
What globally unique, persistent, resolvable identifiers do you use for datasets?
| |||
|
What globally unique, persistent, resolvable identifiers do you use for metadata records?
| |||
|
Which metadata schemas do you use for findability?
| |||
|
What is the technology that links the persistent identifiers of your data to the metadata description?
| |||
|
In which search engines are your datasets indexed?
| |||