mzML
- Stage boundary
- No direct role is recorded for Plan, Harmonize.
- Known limitation
- Conversion can lose vendor-specific detail; XML is large, and mzML does not capture the full cross-sample design, identifications, or quantification results.
Decision support
Compare standards by the job they do
Place up to three profiles side by side. Focus on architectural role, evidence, and the first limitation to test—not on finding a single all-purpose standard.
Working set
Choose profiles
1 of 3 selected
mzMLStandard
Decision lens
Compare roles before you compare maturity.
The useful question is not “Which standard wins?” It is “Which job must this part of the architecture perform, and what remains uncovered?”
- Start with the job
Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.
- Map lifecycle reach
Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.
- Test the boundary
Read what each option leaves unresolved before judging maturity, confidence, or implementation fit.
Three-part assessment
See the reach, the gaps, and the evidence.
Read left to right. Lifecycle reach comes first; maturity remains an editorial roll-up, not certification.
01 · Lifecycle reach
Where each profile contributes directly
Coverage shows a recorded role at that readiness stage. It does not imply end-to-end implementation.
| Profile | Plan | Acquire | Harmonize | Exchange | Learn + reuse |
|---|---|---|---|---|---|
| mzMLStandard | HUPO-PSI mzML has no direct role recorded in Plan. | HUPO-PSI mzML has a direct role in Acquire. | HUPO-PSI mzML has no direct role recorded in Harmonize. | HUPO-PSI mzML has a direct role in Exchange. | HUPO-PSI mzML has a direct role in Learn + reuse. |
Direct role recordedNo direct role recorded
02 · Boundaries
What each option does not cover
These are design boundaries, not faults. Use them to identify the companion layers your architecture still needs.
03 · Detailed assessment
Check the fit and evidence behind the map
Use the source, status, and limitation together. A higher maturity label does not erase a scope mismatch.
| Assessment | mzMLHUPO-PSI mzML |
|---|---|
| Purpose & coverage | Vendor-neutral mass-spectrometry spectra plus acquisition, instrument, and processing metadata using controlled vocabulary terms. Best fitRaw-to-open conversion and exchange of MS spectra across proteomics and metabolomics toolchains. |
| Readiness stages | AcquireExchangeLearn + reuse |
| AI-ready contribution | Standardizes spectra and acquisition context, but feature extraction, batch correction, annotations, and split design require separate evidence. |
| First limitation to test | Conversion can lose vendor-specific detail; XML is large, and mzML does not capture the full cross-sample design, identifications, or quantification results. |
| Evidence | E1 + E2 High confidence Formal statusReleased domain specification ReviewSource-checked |
| Maturity | Established Mature domain format for mass spectrometry |
| Sources & links | HUPO-PSI mzML specification (opens in a new tab)Read full profile |