Day 2 · Keynote · 09:40–10:40

Building an open ecosystem for AI research

Joaquin Vanschoren · TU Eindhoven, AMORE

Tap a dashed word or a blue reference to open it below.

In one line

Open, trustworthy AI won't come from one breakthrough but from many shared parts built over years. The hard part isn't the model architecture; it's the data, evaluation and infrastructure, and that should be shared and open.

Connecting the dots

He opened with a decades-old vision of a book-sized computer that took about 25 years and a whole ecosystem to become today's laptop. Trustworthy, open AI is the same: build the individual parts now, so the ingredients exist in ten years. He told four stories.

1. OpenML

lets anyone share a dataset with one line of code, with machine-readable tasks and results that upload automatically, so experiments are comparable and reproducible. Lessons from ten years: in-person hackathons built the community, simple APIs and a shared vocabulary mattered, and open platforms struggle to fund engineers and upkeep.

2. Rewarding good data

He co-founded the NeurIPS Datasets and Benchmarks track because people won't build good datasets unless it counts for their careers. The track judges data papers on documentation, accessibility, maintenance and ethics rather than on novelty, and now requires data to be hosted with proper metadata. His lesson: reward people in the currency they value.

3. Croissant

is a shared standard for ML datasets, built with the major dataset platforms. It describes a dataset in layers (basic details, files, record structure, meaning), so any tool can find and load it. Communities have added extensions for responsible-AI documentation, Earth observation and biomedical data. Lesson: build bridges, not another platform.

4. Fully open models

Many "open" models share their weights but not their training data or recipes. is building fully open models for all EU languages, publishing data and methods as it goes. Some practical points:

  • Train in phases and save the best data for the end ().
  • Predict performance before spending big compute, by fitting a on a ladder of small training runs:

(, ) = + +

What each symbol means
L
the model's loss (lower is better)
N
number of model parameters
D
number of training tokens
E
the loss you can't get rid of, however big you go
A / Nα
the penalty for a model that is too small
B / Dβ
the penalty for too little data
  • Build safety in at every step: respect opt-outs, scrub toxic and personal data, limit memorisation, test, then red-team.

From his slide: "The hard part isn't the architecture. It's engineering, data cleaning, and knowing exactly what data went in and exactly how you measured what came out."

What's next

He's building infrastructure to find any dataset and link it to evaluations and papers, including an that lets AI agents search for and load datasets. In his words: "What we need now is more people."

Unofficial notes by Rai Vaheed, written up after the talk. The ideas are the speaker's; any mistakes are mine. Corrections: vaheed.raihan@gmail.com · View the source of these notes