This is an ontology of the FAIR Implementation Profiles (FIP) for the FAIR principles.
FAIR Implementation Profile (FIP) Ontology
FIP Question
A question communities have to address when declaring their FAIR Implementation Profiles
FIP Data-related Question
A FIP question that is relevant for the actual data (as compared to just their metadata)
FIP Metadata-related Question
A FIP question that is relevant for metadata (as compared to the data themselves)
FAIR Declaration
The statement of a community on how it addresses a FAIR-related question.
FIP Declaration
The expression of a community on how they address a FIP question
FSR Declaration
The statement of a community on the usage of a FAIR Supporting Resource.
SIP Declaration
The statement of a community on how it addresses a SIP question.
FAIR interpretation
A theoretical and practical explanation of the FAIR Principle by a recognized expert authority.
FAIR Qualifcation Criteria
A proposition on which a qualification of FAIR Supporting Resources is based.
FAIR case study
A description of a real-life situation where FAIR requirements of digital objects play a central role.
FIP No-Choice Declaration
A declaration stating that no choice has been made (yet)
FAIR Implementation Community
A FAIR Implementation Community (FIC) is a self-identified collection of people and/or organizations with the aim to implement the FAIR Principles
Mature community
A well-established community interested to implement FAIR in their data and services.
Emerging community
An early-stage community committed to adopting and promoting FAIR principles for its data and services from the outset.
has data steward
Specifies the data steward for a FAIR implementation community
FAIR Supporting Resource
Any resource that supports FAIR Data Stewardship. FSRs are represented as FAIR Digital Objects (using the nanopublication framework) with Globally Unique, Persistent, Resolvable Identifiers (GUPRI) that resolve to machine-readable metadata about the resource.
Available FAIR Supporting Resource
A FAIR Supporting Resource that is available for use.
FAIR Supporting Resource to be developed
A FAIR Supporting Resource that is not yet available but still needs to be developed.
FAIR-Enabling Resource
A service, a specification or a data policy that is essential to the operationalization of the FAIR Principles, i.e., puts FAIR into action. A FAIR-Enabling Resource (FER) provides a function needed to achieve some aspect of FAIR behavior and is explicitly linked to one or more FAIR principles.
FAIR Implementation Profile
A FAIR Implementation Profile (FIP) is a list of declared technology choices intended to implement each of the FAIR Guiding Principles, made as a collective decision by the members of a particular community of practice.
Reference FAIR Implementation Profile
A list of recommended FAIR Enabling Resources intended to implement the FAIR Guiding Principles, made as a collective decision by the members of a particular community of practice.
Available FAIR-Enabling Resource
A FAIR-enabling resource that is available for use
FAIR-Enabling Resource to be Developed
A FAIR-enabling resource that is not yet available but still needs to be developed
FAIR Data Policy
A policy that specifies and guides FAIR data practices for a community.
FAIR data stewardship plan template
A template guiding data stewardship including how FAIR Principles should be implemented. The template must be completed with project-specific information in any given instance to outline how data are to be handled in preparation for the project, during the research project, and after the project is completed.
FAIR data steward professional profile
A document stating the accumulated training qualifications and FAIR outputs authored by or contributed to, by that person. The profile may be augmented with additional statements regarding professional roles and skills.
FAIR data stewardship event
A meeting specifically designed for current or aspiring data stewards to provide a rigorous understanding of the FAIR principles from theory to their concrete implementation.
FAIR training material
Any educational resource (such as the content or its published representation in text, presentation graphics, or video) that covers FAIR topics of interest.
FAIR practice
A method description detailing the use of a specific resource or a combination of resources as applied by a community to achieve FAIR processing of information.
FAIR specification
A precise description of features, requirements, constraints and recommendations for a specific implementation of a component, system or service supporting the implementation of the FAIR principles.
Crosswalk
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.
FAIR Supporting Technology
Any online accessible software system or component that supports the implementation of the FAIR Principles.
FAIR Supporting Software
Any set of machine-readable instructions that support the implementation of FAIR, that conform to a given syntax, that are interpretable by a given processor, and that instruct a computer's processor to perform specific tasks.
FAIR Representation Service
A transformation service that converts non-FAIR data into a FAIR representation using machine-readable knowledge representation languages.
Web-API
An Application Programming Interface (API) for the World Wide Web that allows different software applications to communicate with each other.
Editor
A service that provides a user-friendly interface for easy editing of metadata, vocabularies or crosswalks.
Validation service
A system that automatically verifies the accuracy, completeness, or compliance of data, code or processes against predefined criteria or standards.
Provenance tracking service
A system that systematically captures, stores and manages detailed information about the origin, history, and lifecycle of digital objects creating metadata based on a provenance model.
Semantic Interoperability Profile
A Semantic Interoperability Profil (SIP) is a list of FAIR Supporting Resources chosen by a community to support semantic interoperability of (meta)data.
Digital Object Type
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.
Identifier service
A service that provides for any digital object (1) algorithms guaranteeing global uniqueness, (2) policy document that guarantees persistent and (3) resolution of the identifier to machine-actionable metadata describing the object and its location.
Metadata schema
A specification that specifies the structured representation of metadata describing attributes of data or other digital objects in terms of semantics, syntax and optionality.
Metadata-data linking schema
A specification that provides a unique, persistent, (ideally) bi-directional, machine-actionable link between metadata and the data they describe.
Registry
A service that indexes metadata and data and provides search over that index.
Generalist registry
A registry designed to collect, provide access to, and enable searching of data without any restrictions on the domain.
Domain-specific registry
A registry designed to collect, provide access to, and enable searching of data within a particular domain or subject area
Communication protocol
A specification of how messages are structured and exchanged.
Authentication and authorization service
A service that mediates access to digital objects according to specifed conditions.
Metadata preservation policy
A data policy that describes the conditions under which metadata should be provided in the future.
Knowledge representation language
A language specification that enables knowledge to be processed by machines.
Structured vocabulary
A specification for a controlled list of uniquely identified and unambigous concepts with their definitions represented using web standards.
Semantic model
A specification that defines qualified relations between entities describing data or other digital objects according to the Linked Data principles. This can include semantic data models and ontologies.
Data usage license
A data policy that specifies legal restrictions on the reuse of the data.
Persistency Policy
A policy with respect to persistency of resources.
Provenance model
A specification that specifies metadata describing the origin and lineage of data or other digital objects.
refers to principle
Connects an entity (for example a FIP declaration) to a FAIR (sub)principle it refers to
refers to question
Connects a FIP declaration to the FIP question it is addressing
declared by
Connects a FIP declaration to the community that made the declaration
declares current use of
Connects a FIP declaration to the resource that the community thereby declares to currently use
declares planned use of
Connects a FIP declaration to the resource that the community thereby declares to plan to use in the future
declares planned replacement of
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).
declares planned development of
Connects a FIP declaration to the resource that the community thereby declares to plan to develop
declared for digital object type
Connects a FIP declaration to the digital object type it applies to
declared for case study
Connects a FIP declaration to the case study it refers to.
has declaration index
Connects a FAIR Implementation Profile or a Semantic Interoperability Profile to the index of their declarations.
has research domain
Connects a FAIR Implementation Community with research domains
enables
Connects a FAIR Enabling Resource class with the FAIR principles it enables
considerations
Considerations that led to a given FIP declaration
availability in years
Specifies how many years a resource is preserved according to a preservation policy
metadata availability in years
Specifies how many years metadata are preserved according to the metadata preservation policy
FIP Question F1-MD
What globally unique, persistent, resolvable identifiers do you use for metadata records?
FIP Question F1-D
What globally unique, persistent, resolvable identifiers do you use for datasets?
FIP Question F2
Which metadata schemas do you use for findability?
FIP Question F3
What is the technology that links the persistent identifiers of your data to the metadata description?
FIP Question F4-MD
In which search engines are your metadata records indexed?
FIP Question F4-D
In which search engines are your datasets indexed?
FIP Question A1.1-MD
Which standardized communication protocol do you use for metadata records?
FIP Question A1.1-D
Which standardized communication protocol do you use for datasets?
FIP Question A1.2-MD
Which authentication & authorisation technique do you use for metadata records?
FIP Question A1.2-D
Which authentication & authorisation technique do you use for datasets?
FIP Question A2
Which metadata longevity plan do you use?
FIP Question I1-MD
Which knowledge representation languages (allowing machine interoperation) do you use for metadata records?
FIP Question I1-D
Which knowledge representation languages (allowing machine interoperation) do you use for datasets?
FIP Question I2-MD
Which structured vocabularies do you use to annotate your metadata records?
FIP Question I2-D
Which structured vocabularies do you use to encode your datasets?
FIP Question I3-MD
Which models, schema(s) do you use for your metadata records?
FIP Question I3-D
Which models, schema(s) do you use for your datasets?
FIP Question R1.1-MD
Which usage license do you use for your metadata records?
FIP Question R1.1-D
Which usage license do you use for your datasets?
FIP Question R1.2-MD
Which metadata schemas do you use for describing the provenance of your metadata records?
FIP Question R1.2-D
Which metadata schemas do you use for describing the provenance of your datasets?
has description source
Denotes the source of the description that is asserted via dct:description
depends on
Connects a FAIR Enabling Resource with a FAIR Supporting Software.
implements
Connects a FAIR Enabling Resource with a FAIR Specification
has data usage license
Connects a FAIR Enabling Resource with a data usage license.
has metadata preservation policy
Connects a registry with a metadata preservation policy.
uses authentication and authorization service
Connects a registry with an authentication and authorization service
uses identifier service
Connects a registry with an identifier service.
targets
Specifies the type of digital object targeted by a FAIR Supporting Resources
has persistency policy
Connects a FAIR Supporting Resource with a persistency policy
is recommended by
Connects a FAIR Supporting Resource with a FAIR Implementation Community that recommends the resource