The solution
Research data packages often need context: who made the files, what software generated them, what license applies, and how the pieces relate. Repositories could store files, but portable, machine-readable context was the hard part.
RO-Crate's elegant move was minimal packaging. Put `ro-crate-metadata.json` beside the data and the directory becomes a crate. The metadata is JSON-LD, but ordinary JSON examples are enough for most tool authors to follow.
That kept the standard lightweight while still linked-data capable. A crate can describe files, web resources, workflows, people, organizations, instruments and provenance without imposing a new archive format.
What it achieved
Describe the folder, not a platform
Why it worked
It works with an existing directory, so adoption does not require repacking the data.
JSON-LD gives global identifiers and schema.org terms while staying readable to JSON tooling.
Cross-references by `@id` let one flat graph describe many related entities.
Profiles let communities specialize the standard without forking the core idea.
What can be applied
Metadata standards spread when they improve an existing folder instead of asking every repository to become the same platform.
Aftermath
RO-Crate reached a long-term 1.3 specification and is used by research-data and workflow communities to package data for distribution, reuse, publishing, preservation and archiving. Its current spec keeps backwards-compatible versioning and an open-source governance model.
FOLLOW THE EVIDENCE
The sources
- Introduction researchobject.org
- RO-Crate Specification researchobject.org