Turn any GitHub repository into a machine-readable metadata endpoint — no server, no database, no infrastructure cost.
A standardised, machine-readable metadata endpoint — based on the W3C DCAT vocabulary — that makes datasets Findable, Accessible, Interoperable, and Reusable.
Persistent identifiers and rich metadata let search engines, data portals, and other FDPs discover your data automatically.
Open HTTP(S) endpoints anyone can query — no proprietary API keys, no sign-up, no institutional subscription.
RDF Turtle + JSON-LD. Link directly to ontology terms (ORDO, OMIM, HPO, ICD…) using shared, open vocabularies.
DCAT-3 structured metadata, clear provenance, and explicit licences let others build on your work with confidence.
GitHub as the canonical store — pull requests for peer review, Actions for validation, Pages for serving.
Metadata lives as RDF Turtle files in a GitHub repository. Human-readable, version-controlled, diffable.
GitHub Actions runs ShEx validation on every pull request. Invalid metadata is blocked before it merges.
GitHub Pages serves the files at a stable URL with correct content-type headers — no backend needed.
Register your FDP root URL and the FDP Index crawls it daily, making your datasets visible to the community.
A daily-crawled registry of all registered StaticFDPs. Each entry shows datasets, catalogues, and metadata freshness. The index itself is a FAIR Data Point.
Open the FDP Index → View on GitHubFAIR Data Points indexed by this platform — a mix of StaticFDP-hosted and external servers.
See StaticFDP in action — two concrete examples of what you can query and build once your metadata is FAIR.
Query all registered FDPs at once
Because every FDP publishes RDF, you can federate a SPARQL query across the entire index to find, for example, all datasets related to a given ORDO disease term.
Visualise community-contributed data
Community members submitted disease case data through the GA4GH BYOD forms. This demo reads those GitHub Issues as structured data and renders a comparative timeline of symptom onset across rare diseases.
Four steps from zero to a fully indexed, validated FAIR Data Point.
Click Use this template on github.com/StaticFDP/staticfdp-template to create your own repository with the right folder structure and workflows pre-configured.
Open fdp/catalog.ttl and fill in your dataset details. Use standard prefixes: dcat:, dcterms:, ordo:, hpo:. Every save triggers ShEx validation.
Go to Settings → Pages → Source: main branch / docs folder. Your FDP will be live at https://<org>.github.io/<repo>/ within minutes.
Open a pull request adding your URL to registry.yaml. Once merged, the daily crawl picks you up automatically — or ping the index immediately with a repository_dispatch event.
Standards StaticFDP builds on.
| Standard / tool | Role | Link |
|---|---|---|
| FAIR Data Point specification | Defines the HTTP API and metadata model | specs.fairdatapoint.org |
| DCAT-3 | Core vocabulary for datasets, catalogues, distributions | w3.org |
| RDF Turtle | Human-friendly RDF serialisation | w3.org |
| ShEx | Primary schema validation language | shex.io |
| Cloudflare Workers | OAuth-authenticated form submission without GitHub accounts | workers.cloudflare.com |