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.

Choose profiles

1 of 3 selected

SDRF-ProteomicsMetadata profile

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?”

  1. Start with the job

    Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.

  2. Map lifecycle reach

    Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.

  3. Test the boundary

    Read what each option leaves unresolved before judging maturity, confidence, or implementation fit.

See the reach, the gaps, and the evidence.

Read left to right. Lifecycle reach comes first; maturity remains an editorial roll-up, not certification.

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 SDRF-Proteomics
ProfilePlanAcquireHarmonizeExchangeLearn + reuse
SDRF-ProteomicsMetadata profileSDRF-Proteomics has a direct role in Plan.SDRF-Proteomics has a direct role in Acquire.SDRF-Proteomics has a direct role in Harmonize.SDRF-Proteomics has a direct role in Exchange.SDRF-Proteomics has a direct role in Learn + reuse.
Direct role recordedNo direct role recorded

What each option does not cover

These are design boundaries, not faults. Use them to identify the companion layers your architecture still needs.

SDRF-Proteomics

Stage boundary
No direct stage gap is recorded. Lifecycle reach still does not make this an end-to-end implementation.
Known limitation
It does not encode downstream statistical-analysis parameters or results. Working-branch templates and rules can move ahead of the final PSI specification, so release and validator versions must be pinned.

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 SDRF-Proteomics
AssessmentSDRF-ProteomicsSDRF-Proteomics
Purpose & coverage

Tabular sample-to-data relationships, biological and technical factors, replicates, instruments, acquisition context, and proteomics experimental design.

Best fitProteomics studies that need an explicit, machine-readable mapping from biosamples and factors to raw and processed mass-spectrometry files.

Readiness stages
PlanAcquireHarmonizeExchangeLearn + reuse
AI-ready contributionMakes sample grouping, factor assignment, replicate structure, and file joins explicit for reusable training and evaluation datasets.
First limitation to testIt does not encode downstream statistical-analysis parameters or results. Working-branch templates and rules can move ahead of the final PSI specification, so release and validator versions must be pinned.
Evidence

E1 + E2 High confidence

Formal statusHUPO-PSI final 1.0.0; 1.1.0 working changes unreleased

ReviewSource-checked · watch

Maturity

Scaling

Final HUPO-PSI specification with validators and repository use

Sources & links