Data Readiness Knowledge Base

01

Where it fits—and where it doesn’t

Use these four checks before committing implementation time.

Use it when: Raw-to-open conversion and exchange of MS spectra across proteomics and metabolomics toolchains.
Do not use it as: Do not treat mzML as a complete solution on its own. Conversion can lose vendor-specific detail; XML is large, and mzML does not capture the full cross-sample design, identifications, or quantification results.
Best for: Teams working with Omics and Laboratory data across Acquire → Exchange → Learn + reuse.
Maturity: EstablishedEstablished enough for serious use; still pin the exact release and any implementation profile.

02

See it in the workflow

A standard creates value by changing a handoff, not by existing in a catalog.

InputWhat starts
Omics and Laboratory data, metadata, and the local decisions around them
mzMLWhat changes
mzML applies a shared standard across Acquire → Exchange → Learn + reuse
OutputWhat becomes possible
A more consistent, reviewable handoff for the next system or team

Readiness gateBefore scaling: Conversion can lose vendor-specific detail; XML is large, and mzML does not capture the full cross-sample design, identifications, or quantification results.

03

A concrete example

A proteomics pipeline converts frozen vendor raw files to mzML, records converter/version/parameters, validates output, and retains source files and checksums.

Why it matters: Standardizes spectra and acquisition context, but feature extraction, batch correction, annotations, and split design require separate evidence.

04

What it fits with

Pairs with ISA for study/assay context and SDRF-Proteomics for sample-to-file design; PSI-MS controlled vocabulary supplies semantics.

05

Implementation starter

Start with one bounded handoff. Pin, test, and review it before scaling.

Name an accountable owner and the decision mzML must support.
Pin the exact version and companion artifacts: 1.1.0.
Map one representative input to the required standard artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.

06

Limitation to test first—and the tests that catch it

Risk

Conversion can lose vendor-specific detail; XML is large, and mzML does not capture the full cross-sample design, identifications, or quantification results.

Test

Run one representative end-to-end pilot and record exactly where mzML loses context, needs an extension, or depends on another standard.

Risk

A structured or machine-readable result can still be unfit for analysis or AI.

Test

Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Standardizes spectra and acquisition context, but feature extraction, batch correction, annotations, and split design require separate evidence.

07

Why we believe this

Checked against the canonical source plus independent operational evidence from an adopter, regulator, or implementation report.

Evidence notation: E1 + E2. The code is shorthand; the plain-language statement above is the claim.

Formal status: Released domain specification
Confidence: High
Review state: Source-checked
Reviewed by: Mass-spectrometry standards reviewer
Last verified: 13 July 2026
Review again when: Specification, controlled vocabulary, or converter update

How the evidence method works

08

Source shelf

Official diagrams, examples, specifications, and explainers. Nothing external loads until you choose to open it.

Primary source1.1.0
HUPO-PSI mzML specification
The canonical publisher or steward source used to verify this standard profile.
Publisher
HUPO Proteomics Standards Initiative
Rights
Rights remain with the publisher; this knowledge base links to the source rather than copying it.
Access
Opens the publisher's source in a new tab; no external media loads on this page.
Verified
2026-07-13
Open at source