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.

Working set

Choose profiles

1 of 3 selected

AnnData ecosystemReference architecture

Add a profile

Decision lens

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

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

Assessment

Review lifecycle coverage and practical fit.

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

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 Single-cell and Spatial Data Ecosystem
Profile	Plan	Acquire	Harmonize	Exchange	Learn + reuse
AnnData ecosystemReference architecture	Single-cell and Spatial Data Ecosystem has no direct role recorded in Plan.	Single-cell and Spatial Data Ecosystem has a direct role in Acquire.	Single-cell and Spatial Data Ecosystem has a direct role in Harmonize.	Single-cell and Spatial Data Ecosystem has a direct role in Exchange.	Single-cell and Spatial Data Ecosystem 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.

AnnData ecosystem

Stage boundary: No direct role is recorded for Plan.
Known limitation: This is a fast-moving software ecosystem rather than a single governed standard. Container validity does not guarantee consistent preprocessing, cell annotation, biological comparability, or lossless conversion to Seurat or other ecosystems.

03 · Detailed assessment

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 Single-cell and Spatial Data Ecosystem
Assessment	AnnData ecosystemSingle-cell and Spatial Data Ecosystem
Purpose & coverage	Annotated single-cell matrices, multimodal containers, repository metadata requirements, ontology-bound annotations, and spatial images, labels, points, shapes, tables, and coordinate systems. Best fitAn implementable analysis and publication stack for single-cell, multi-omic, and spatial-omics data when the exact component, encoding, schema, and ontology releases can be pinned.
Readiness stages	AcquireHarmonizeExchangeLearn + reuse
AI-ready contribution	Common matrices, annotations, spatial coordinates, and loaders support scalable model development, but raw-count provenance, reference builds, QC, batch effects, label uncertainty, privacy, leakage, and split policy remain separate evidence.
First limitation to test	This is a fast-moving software ecosystem rather than a single governed standard. Container validity does not guarantee consistent preprocessing, cell annotation, biological comparability, or lossless conversion to Seurat or other ecosystems.
Maturity	Scaling Widely used software ecosystem, not one formal consensus standard; components version independently and SpatialData remains under active development
Sources & links	scverse foundational data structures (opens in a new tab)Read full profile