01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Accessible, computational result exchange when consumers need a concise table rather than the complete identification or quantification evidence model.
- Limits
- The two branches are not interchangeable, and a summary cannot reconstruct the full processing history or detailed evidence. Tool support must be checked against the exact flavor and version.
- Best for
- Omics and Laboratory teams working across Harmonize → Exchange → Learn + reuse.
- Maturity
- ScalingUsable now, but adoption or tooling is still developing. Pilot the exact stack first.
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
- mzTabWhat changes
Use mzTab as a pinned standard across Harmonize → Exchange → Learn + reuse
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
03
A concrete example
A release publishes a validated mzTab result summary for proteomics or mzTab-M 2.0 for metabolomics, with raw-file, assay, database, software, and controlled-vocabulary references.
Why it matters: Tabular outputs are convenient for feature loading, but missing evidence, confidence semantics, batch design, and preprocessing provenance can make naive reuse unsafe.
04
What it fits with
mzTab 1.0 summarizes proteomics results and links to detailed mzIdentML or mzQuantML evidence; mzTab-M 2.0 is a non-backward-compatible metabolomics-focused specification.
- Metadata profileSDRF-Proteomics
Both support Omics and Laboratory work and meet around Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - StandardmzIdentML
Both support Omics and Laboratory work and meet around Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Data model / schemaGA4GH VRS
Both support Omics and Laboratory work and meet around Harmonize, 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 Harmonize, 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 mzTab must support.
Pin the exact version and companion artifacts: mzTab 1.0.0 (proteomics) · mzTab-M 2.0.0 (metabolomics).
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
The two branches are not interchangeable, and a summary cannot reconstruct the full processing history or detailed evidence. Tool support must be checked against the exact flavor and version.
Run one representative end-to-end pilot and record exactly where mzTab 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. Tabular outputs are convenient for feature loading, but missing evidence, confidence semantics, batch design, and preprocessing provenance can make naive reuse unsafe.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
HUPO-PSI mzTab specifications
Official publisher or steward guidance for this standard profile.
- Publisher
- HUPO Proteomics Standards Initiative