We are opening all specifications* to everyone who is interested and invite you to have a look and comment.

On the specification buttons below, click once on the title for its description. Click a 2nd time on the description to go to the actual specification (browser). Leave a comment on a specific part of the specification by highlighting it in your browser window, then click the ‘Add a comment’ icon (square speech bubble with ‘+’) in the upper right corner.

*Documents are still in the commenting phase and may be subsequently updated. If you would like to participate in FDOF’s internal commenting, please register to be on the FDOF’s Mailing List.

FAIR Digital Objects Roadmap v5-22-11-19

This paper is not a specification but is a living roadmap document provided by the BIG & TSIG co-chairs based on the discussions on FDO specification so far and focussing on technological aspects.

FDO Glossary November 2022

This living glossary is not a specification but contains the consolidated list of terms extracted from the FDO specification documents as they are being used by the FDO Forum.

Full FDO Spec Doc PR-1.2

This document is the first comprehensive overview of FAIR Digital Object specifications. It addresses a variety of aspects that have been discussed in the FDO Forum during its first two years but contains only the essentials.

PED DOIP Endorsement 1.1-20221017

The DOIP Version 2.0 as released by the DONA Foundation is endorsed as an important contribution to the FDO Forum specification stack. The DOIP interfacing protocol specifies how clients can interact with DOs independent of the technology used by a DOIP server and independent of the data organization chosen.

PEN FDO Upload 1.1-20221017

This document illustrates the type of operations and checks that need to be done when an FDOs are being uploaded to the domain of FDOs. It also describes the type of services that can be thought of, and the scope of checks that can be carried out at different FDO levels.

PR Configuration Types 2.1-20221017

Intensive discussions within the FDO Forum revealed that there are many different ways to organize FAIR Digital Objects and many of them listed in this document are being used in daily practice.

PR FDO Kernel Attributes and Metadata 2.0-20221017

Since the start of FDO concept development there has been a discussion on what attributes are needed for proper working FDOs in different contexts and what would be the difference and overlaps with object metadata such as currently used in research data-management. This document draws on previous discussions with respect to attributes stored with Handle type PIDs to facilitate easy data-management and discussions to derive a core-metadata schema for interdisciplinary work.

PR Granularity 2.2-20221017

The FDO Forum needs a comprehensive definition of what a FAIR Digital Object (FDO) is and what it is not. This requires understanding the various aspects of FDOs, of which aspects of granularity and versioning are highly important.

PR Machine Actionability Definition 2.2-20221119

For FDO work we need a clear definition of what is meant with the term “machine actionability”. This document includes a description of relevant terms and draws conclusions in the form of a definition for use in the FDO Forum.

PR PID Profile Attributes 2.1-20221017

The FDO Forum needs a comprehensive definition of what a FAIR Digital Object (FDO) is and what its relevant components are. The PID Profiles and the set of kernel attributes that can be used in PID Profiles are such key pillars. The purpose of this paper is to specify these two aspects in order to incorporate them in the comprehensive FDO specification paper to be written.

PR Requirement Specification 2.1

This FDO Requirement Specification document specifies the criteria which digital entities need to fulfill to be accepted as FAIR Digital Objects, and need to be adhered to by all implementations that claim to be FDO compliant. The requirements are written at a level that allows for different implementations.

PR Typing FDOs 2.0-20220608

FAIR Digital Objects promote machine-actionability by requiring that each digital object be characterized using signals that will clearly hint at the potential processing steps any machine accessing it may perform. We call those signals types and this document describes the need for types and the principles that the FDO community is following in the
development of a framework for creating and applying those types.

FDO Forum Document Process

For all official documents of FDOF we follow a strict process which has been adopted from IVOA/W3C (see diagram). This implies that there are essentially 3 basic steps to be taken:

-discuss documents as Working Drafts in the FDO working groups and resolve all comments

-discuss documents as Proposed Recommendations within the FDO and RDA FDODF community and resolve all comments

-decide about an FDO Recommendation by the FDO Steering Committee

We have now modified the process slightly by also opening the Proposed Recommendations to everyone interested via the website before coming to a final recommendation decision. All of these iterations cost time, since at each step a commenting phase is opened and the iterations need to go on until all comments are resolved. For a community based on voluntary work, adhering to this process for all the documents was and is a challenge.

Relationships between specifications

The diagram to the right illustrates relationships between the current (Nov 2022) 12 documents. Those marked with a red outline (FDO Specification, FDO Implementation and FDO Glossary) are important because they summarise all the work that has been done. These summaries reflect our strategic approach to address the large complex subject of FDOs by first breaking it down into manageable parts and then summarising the results. It was important that the intermediate specification and illustrating documents were written in an elaborative way to make the topics understandable for all people in the FDO Forum, and these documents were written at different moments in time. It has already been agreed that the Forum will update all documents based on the converging glossary of terms in 2023.