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

mzTabStandard

Add a profile

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.

Readiness-stage coverage for HUPO-PSI mzTab + mzTab-M
Profile	Plan	Acquire	Harmonize	Exchange	Learn + reuse
mzTabStandard	HUPO-PSI mzTab + mzTab-M has no direct role recorded in Plan.	HUPO-PSI mzTab + mzTab-M has no direct role recorded in Acquire.	HUPO-PSI mzTab + mzTab-M has a direct role in Harmonize.	HUPO-PSI mzTab + mzTab-M has a direct role in Exchange.	HUPO-PSI mzTab + mzTab-M 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.

mzTab

Stage boundary: No direct role is recorded for Plan, Acquire.
Known 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.

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.

Detailed comparison of HUPO-PSI mzTab + mzTab-M
Assessment	mzTabHUPO-PSI mzTab + mzTab-M
Purpose & coverage	Tab-delimited summaries of mass-spectrometry-derived proteins, peptides, spectra, small molecules, features, identifications, and quantitative values. Best fitAccessible, computational result exchange when consumers need a concise table rather than the complete identification or quantification evidence model.
Readiness stages	HarmonizeExchangeLearn + reuse
AI-ready contribution	Tabular outputs are convenient for feature loading, but missing evidence, confidence semantics, batch design, and preprocessing provenance can make naive reuse unsafe.
First limitation to test	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.
Evidence	E1 + E2 High confidence Formal statusReleased mzTab 1.0.0 and non-backward-compatible mzTab-M 2.0.0 ReviewSource-checked · watch
Maturity	Scaling Released tabular formats with operational support; proteomics and metabolomics branches differ
Sources & links	HUPO-PSI mzTab specifications (opens in a new tab)Read full profile