Decision support

Compare standards by the job they do

Place up to three profiles side by side. Compare their architectural role, lifecycle reach, and first limitation to test. No single standard covers every layer.

Choose profiles

1 of 3 selected

PDBx/mmCIFData model / schema

Compare roles before choosing an implementation.

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 or implementation fit.

Review lifecycle coverage and practical fit.

Read left to right. Lifecycle reach comes first; a maturity label never overrides a scope mismatch.

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 PDBx/mmCIF Exchange Dictionary and Format
ProfilePlanAcquireHarmonizeExchangeLearn + reuse
PDBx/mmCIFData model / schemaPDBx/mmCIF Exchange Dictionary and Format has no direct role recorded in Plan.PDBx/mmCIF Exchange Dictionary and Format has a direct role in Acquire.PDBx/mmCIF Exchange Dictionary and Format has a direct role in Harmonize.PDBx/mmCIF Exchange Dictionary and Format has a direct role in Exchange.PDBx/mmCIF Exchange Dictionary and Format 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.

PDBx/mmCIF

Stage boundary
No direct role is recorded for Plan.
Known limitation
The living dictionary is large and revisions can affect parsers, extensions, and optional categories. Syntactic conformance does not establish model quality, biological relevance, or comparability.

Check the fit and source behind the map

Use the official source, version, and limitation together. A higher maturity label does not erase a scope mismatch.

Detailed comparison of PDBx/mmCIF Exchange Dictionary and Format
AssessmentPDBx/mmCIFPDBx/mmCIF Exchange Dictionary and Format
Purpose & coverage

Structured macromolecular coordinate data and related entities, sequences, assemblies, experimental methods, refinement, citations, software, and archive metadata.

Best fitDeposition, validation, exchange, parsing, and reuse of experimentally determined macromolecular structures across wwPDB and structural-biology toolchains.

Readiness stages
AcquireHarmonizeExchangeLearn + reuse
AI-ready contributionProvides typed atom-level structures and experimental context for feature generation, while structure quality, redundancy, biological assemblies, label construction, and train-test separation need independent controls.
First limitation to testThe living dictionary is large and revisions can affect parsers, extensions, and optional categories. Syntactic conformance does not establish model quality, biological relevance, or comparability.
Maturity

Established

Current exchange dictionary supporting the PDB archive; continuously revised under wwPDB stewardship

Sources & links