01
Where it fits and where it does not
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.
- Limits
- 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
- Omics and Laboratory teams working across Acquire → Exchange → Learn + reuse.
- Maturity
- EstablishedSuitable for production assessment. Pin the exact release and any implementation profile.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Omics and Laboratory source data, metadata, and local mappings
- mzMLWhat changes
Use mzML as a pinned standard across Acquire → Exchange → Learn + reuse
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
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.
- Metadata profileSDRF-Proteomics
Both support Omics and Laboratory work and meet around Acquire, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Data model / schemaAIRR · MiAIRR
Both support Omics and Laboratory work and meet around Acquire, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata profileExpmeta
Both support Omics and Laboratory work and meet around Acquire, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Quality vocabularyWGS QC
Both support Omics and Laboratory work and meet around Acquire, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Define one handoff, its 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
Test the main limitation
Conversion can lose vendor-specific detail; XML is large, and mzML does not capture the full cross-sample design, identifications, or quantification results.
Run one representative end-to-end pilot and record exactly where mzML loses context, needs an extension, or depends on another standard.
Machine-readable output may still be unfit for analysis or ML.
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
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
HUPO-PSI mzML specification
Official publisher or steward guidance for this standard profile.
- Publisher
- HUPO Proteomics Standards Initiative