01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Detailed, tool-independent exchange of proteomics identification evidence for post-processing, validation, archiving, and repository submission.
- Limits
- The XML model is complex; older versions remain in operational use, and producer/consumer support varies by feature. It does not encode the full sample design or statistical analysis.
- Best for
- Omics and Laboratory teams working across Harmonize → 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
- mzIdentMLWhat changes
Use mzIdentML 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 search pipeline exports mzIdentML 1.3.0 with database and software versions, parameters, scores, thresholds, spectrum references, and validated peptide/protein identifications.
Why it matters: Provides structured labels and identification evidence, but confidence calibration, decoy strategy, sample grouping, and batch context must be evaluated separately.
04
What it fits with
References spectra from mzML or peak-list files, uses PSI controlled vocabularies, complements SDRF-Proteomics design metadata, and can feed lighter mzTab summaries.
- 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 - StandardmzTab
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 mzIdentML must support.
Pin the exact version and companion artifacts: 1.3.0 · June 2024 current; 1.2.0 and 1.1.0 still supported.
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 XML model is complex; older versions remain in operational use, and producer/consumer support varies by feature. It does not encode the full sample design or statistical analysis.
Run one representative end-to-end pilot and record exactly where mzIdentML 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. Provides structured labels and identification evidence, but confidence calibration, decoy strategy, sample grouping, and batch context must be evaluated separately.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
HUPO-PSI mzIdentML specification
Official publisher or steward guidance for this standard profile.
- Publisher
- HUPO Proteomics Standards Initiative