A FAIR data point is a lightweight metadata server that exposes structured, standardised descriptions of a dataset — its identifier, creator, licence and access route — through a REST API, so software (not just people) can discover and assess it automatically. Under the GO FAIR implementation network, FAIR Data Points are the working infrastructure that turns the FAIR principles from a policy statement into a queryable service.
In formal terms, a FAIR Data Point (FDP) is a metadata repository that follows the DCAT2 vocabulary and organises records in a fixed hierarchy — repository, catalogue, dataset, distribution — using Linked Data Platform containers, as set out in the peer-reviewed FDP specification (da Silva Santos et al., 2023, Data Intelligence, MIT Press).
- What Is a FAIR Data Point?
- How Does the GO FAIR Initiative Use FAIR Data Points?
- FAIR Data Point vs Machine-Actionable DMP: What Is the Difference?
- How Is FAIRness Measured? The F-UJI Evaluator
- Where Does DDI Fit Into the FAIR Data Point Stack?
- Frequently Asked Questions
- What This Means for Data Stewards and Developers
What Is a FAIR Data Point?
A FAIR Data Point separates metadata from data. It does not host the dataset itself; it hosts a machine-readable description of the dataset, reachable at a stable HTTP endpoint. This separation is what makes the metadata queryable independently of wherever the underlying files are actually stored.
The reference specification defines four nested layers, each exposed as its own resource:
- Repository — the top-level FDP instance, describing the organisation or project running it
- Catalogue — a themed grouping of related datasets
- Dataset — the described research object, with identifier, creator, licence and rights statement
- Distribution — the concrete access point (a download URL, an API, a query service)
Every layer is exposed via a REST API and encoded as RDF using the DCAT2 vocabulary, which is why an FDP can be crawled and indexed by external harvesters without bespoke integration work per institution.
How Does the GO FAIR Initiative Use FAIR Data Points?
GO FAIR is a grassroots, community-run implementation network for the FAIR principles, not a standards body with formal ownership of a single specification. It organises its work around three self-described pillars — GO CHANGE (policy and culture), GO TRAIN (skills) and GO BUILD (technical infrastructure) — coordinated through the GO FAIR Foundation.
FAIR Data Points sit inside the GO BUILD pillar. GO FAIR pairs FDPs with FAIR Implementation Profiles (FIPs): a documented set of choices a specific research community makes about identifiers, vocabularies, access protocols and licensing terms. The FIP tells an FDP deployment which controlled vocabularies to use at the dataset and distribution layers, so that metadata from two unrelated institutions in the same domain remains interoperable rather than merely similar.
The combined goal is what GO FAIR calls the “Internet of FAIR Data & Services” — a distributed network of FDPs that automated agents can traverse to locate relevant data without a central index. A working example already in production is the European Joint Programme on Rare Diseases (EJP RD) Virtual Platform, whose index runs on a federated network of FDPs contributed by member registries across Europe, funded through the EU Horizon research programme.
FAIR Data Point vs Machine-Actionable DMP: What Is the Difference?
The two are frequently conflated because both are described as “machine-actionable,” but they describe different objects at different points in the research lifecycle. A machine-actionable Data Management Plan (maDMP) — built on the Research Data Alliance’s DMP Common Standard and served by tools such as DMPTool or DMPonline — describes intentions: what data a project will produce, where it will deposit it and under what licence. An FDP describes an already-deployed dataset that a machine can query right now.
| Aspect | FAIR Data Point | Machine-Actionable DMP |
|---|---|---|
| Lifecycle stage | Post-deposit, dataset already exists | Pre-project, data not yet produced |
| Governing spec | GO FAIR / FDP specification (DCAT2, LDP) | RDA DMP Common Standard |
| Query interface | REST API over a live metadata service | JSON export or plan-management tool API |
| Granularity | Per dataset / per distribution | Per project or funding award |
| Typical operator | Data repository or institutional archive | Institution, funder, or research office |
Confusing the two leads institutions to procure the wrong tool: an maDMP platform will not make a finished dataset crawlable, and an FDP deployment will not help a project plan its future data management obligations.
How Is FAIRness Measured? The F-UJI Evaluator
F-UJI is an automated FAIR assessment tool developed under the Horizon 2020 FAIRsFAIR project. It scores a dataset’s exposed metadata — including metadata served by an FDP — against a fixed set of maturity indicators grouped under the four FAIR facets, returning a numeric FAIRness score rather than a binary pass/fail.
F-UJI can only evaluate what is machine-visible: it checks whether a licence, persistent identifier or access protocol is declared in the metadata, not whether the underlying data file is actually reusable in practice. This is precisely why the metadata layer an FDP provides matters — a well-structured FDP deployment is what allows a tool like F-UJI to detect FAIRness signals automatically, while a plain data-download page with no structured metadata will score poorly regardless of how well-organised the actual dataset is.
Where Does DDI Fit Into the FAIR Data Point Stack?
The Data Documentation Initiative (DDI) is an XML/RDF metadata standard maintained by the DDI Alliance for describing social, behavioural and economic science data at the variable level — survey questions, coding frames, sampling design. DCAT2, the vocabulary an FDP uses by default, describes a dataset at the catalogue-entry level; it was never designed to capture variable-level detail.
A research community whose FAIR Implementation Profile specifies DDI alongside DCAT2 gets both: FDP-level crawlability for discovery, and DDI-level granularity for reuse. Social-science archives affiliated with the Consortium of European Social Science Data Archives (CESSDA) and the UK Data Service already publish DDI metadata; wiring that metadata into an FDP endpoint is a genuine interoperability gain rather than duplicated effort.
Frequently Asked Questions
What is a FAIR data point?
A FAIR Data Point is a metadata repository that exposes a dataset’s identifier, licence, creator and access route through a REST API, structured according to the DCAT2 vocabulary. It publishes metadata about data, not the data itself, so automated tools can discover and evaluate the dataset without human involvement.
What does FAIR data mean?
FAIR data meets the 2016 principles of Findability, Accessibility, Interoperability and Reusability, first formally published by Wilkinson et al. in Scientific Data. The principles apply to metadata as much as to the underlying files, which is why machine-readable metadata infrastructure, such as an FDP, is required to satisfy them at scale.
What are the four pillars of the FAIR data principles?
The four pillars are Findable (a persistent identifier and rich metadata exist), Accessible (metadata is retrievable via an open protocol, even if the data itself is restricted), Interoperable (metadata uses a shared, formal vocabulary such as DCAT2), and Reusable (a clear licence and provenance are attached).
What This Means for Data Stewards and Developers
Deploying a FAIR Data Point is an infrastructure decision, not a documentation exercise. In practice it requires three steps: agreeing a FAIR Implementation Profile with the relevant research community, mapping local repository metadata onto DCAT2 at the dataset and distribution layers, and registering the resulting endpoint so external harvesters and tools such as F-UJI can find it.
- Pair persistent dataset identifiers from DataCite with the FDP’s dataset layer so citation and discovery metadata stay consistent
- Use ROR identifiers for the institutional agent fields rather than free-text organisation names
- Treat the FDP as complementary to, not a replacement for, an maDMP — one documents intent, the other serves the finished product
Funders are moving in this direction: the UNESCO Recommendation on Open Science (2021) names FAIR data as a foundational pillar, and Horizon Europe grant conditions increasingly expect data to be discoverable by machines, not just listed in a repository catalogue. For institutions building research-data infrastructure now, a standards-conformant FAIR Data Point is a defensible way to demonstrate machine-actionability rather than assert it in a data management plan.
For related definitions and terminology, see the CASRAI dictionary and the research administration pillar.
Leave a Reply