Here you can see a list of the most recent versions of FDO specifications documents.

Note: Click on the (+) to see more information about the Authors and Editors.

*These documents 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.

CategoryDocument TitleVersionEditorsAuthorsDOI (all versions)Description
CorePR Requirement SpecificationPR-3.0G. Strawn, P. WittenburgI. Anders, Ch. Blanchi, Daan Broeder, M. Hellström, Sh. Islam, Th. Jejkal, L. Lannom, K. Peters, R. Quick, A. Schlemmer, U. Schwardmann, St. Soiland-Reyes, G. Strawn, D. van Uytvanck, C. Weiland, P. Wittenburg, C. Zwölfhttps://doi.org/10.5281/zenodo.7781925This 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.
CoreImplementation of Attributes, Types,Profiles and RegistriesWD-0.4U. Schwardmann, C. Blanchi, P. WittenburgC. Blanchi, M. Hellström, L. Lannom, A. Pfeil, U. Schwardmann, P. Wittenburghttps://doi.org/10.5281/zenodo.7825572This document describes the details that are implied by the working draft on typing from an implementation standpoint. It highlights the roles of FDOs, their PIDs, their attributes and services and registries for FDOs, that need to be established and that operate on objects. It therefore is the core document for building FDO infrastructures.
CoreFDO OverviewPEN-2.0Larry Lannom, Ulrich Schwardmann, Peter Wittenburg, Christophe Blanchi, Ivonne Anders, Claus WeilandI. Anders, Ch. Blanchi, Daan Broeder, M. Hellström, Sh. Islam, Th. Jejkal, L. Lannom, K. Peters, R. Quick, A. Schlemmer, U. Schwardmann, Stian Soiland-Reyes, G. Strawn, D. van Uytvanck, C. Weiland, P. Wittenburg, Carlo Zwölfhttps://doi.org/10.5281/zenodo.7824713This 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.
DetailDOIP EndorsementPEP-1.1U. Schwardmann, G. Strawn, R. Quick, P. Wittenburghttps://doi.org/10.5281/zenodo.7824795The 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.
DetailUpload of FDOPEN-1.1Daan Broeder, Islam Sharif, Peter WittenburgChristophe Blanchi, Daan Broeder, Thomas Jejkal, Islam Sharif, Alexander Schlemmer, Dieter van Uytvanck, Peter Wittenburghttps://doi.org/10.5281/zenodo.7825548This 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.
DetailTyping FDOsPR-2.0Larry Lannom, U. SchwardmannLarry Lannom, Ulrich Schwardmann, Christophe Blanchi, Peter Wittenburghttps://doi.org/10.5281/zenodo.7825598FAIR 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.
DetailFDO PID Profile & AttributesPR-2.1Maggie Hellström, Sharif Islam, Peter WittenburgIvonne Anders, Maggie Hellström, Sharif Islam, Thomas Jejkal, Larry Lannom, Ulrich Schwardmann, Peter Wittenburghttps://doi.org/10.5281/zenodo.7825629The 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.
DetailFDO Machine Actionability PR-2.2Claus Weiland, Peter WittenburgClaus Weiland, Sharif Islam, Daan Broder, Ivonne Anders, Peter Wittenburghttps://doi.org/10.5281/zenodo.7825649For 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
DetailFDO GranularityPR-2.2Maggie Hellström, Carlo Zwölf, Peter Wittenburghttps://doi.org/10.5281/zenodo.7825685Since 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.
DetailFDO Kernel Attributes and MetadataPR-2.1Daan Broeder, Peter Wittenburg, Ivonne Anders, Karsten Peters-von Gehlenhttps://doi.org/10.5281/zenodo.7825692Since 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.
DetailFDO Configuration TypesPR-2.1Ivonne Anders, Andreas Pfeil, Peter WittenburgLarry Lannom, Karsten Peters-von Gehlen, Ivonne Anders, Andreas Pfeil, Alexander Schlemmer, Zach Trautt, Peter Wittenburghttps://doi.org/10.5281/zenodo.7825702Intensive 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.
GeneralFAIR Digital Objects RoadmapPEN-5Larry Lannom, Ulrich Schwardmann, Christophe Blanchi, Ivonne Anders, Claus Weiland, Peter Wittenburghttps://doi.org/10.5281/zenodo.7824672This 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 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.
https://fairdo.org/specifications/
fairdo.org
CC-MAIN-2024-26
180442
application/http; msgtype=response
sha1:3LKFYBV4CZWYWTGY6Y7AYFT7C7GBML7Q
<urn:uuid:c0f9ea43-e14c-4267-9050-ea3e95e9f130>
2024-06-19T08:32:11Z
85.10.159.114
text/html
sha1:KQEMAJA6W7YVPB5A2L2FFL3GPE4ARZNP
<urn:uuid:8f041583-defb-401a-b904-e3a02f059f6e>
https://fairdo.org/specifications/
response
<urn:uuid:daa60577-7a2b-40d6-ad01-9e934823d282>
isPartOf: CC-MAIN-2024-26
publisher: Common Crawl
description: Wide crawl of the web for June 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-207
software: Apache Nutch 1.20 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/