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
01
NWBData model / schema
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?”
01
Start with the job
Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.
02
Map lifecycle reach
Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.
03
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 Neurodata Without Borders
Extensions and optional fields can fragment interoperability; storage and API compatibility must be tested, and schema validity does not establish signal quality or biological correctness.
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.
Neurophysiology acquisition and processed data, time series, events, stimuli, behavior, electrophysiology, optical physiology, devices, and experimental metadata.
Best fitSession-level packaging and reuse of complex neurophysiology experiments where synchronized signals and experiment context must remain together.
Readiness stages
AcquireHarmonizeExchangeLearn + reuse
AI-ready contribution
Standardized time series, events, trials, and device context enable reusable feature pipelines, while annotation quality, sampling bias, and split design remain project responsibilities.
First limitation to test
Extensions and optional fields can fragment interoperability; storage and API compatibility must be tested, and schema validity does not establish signal quality or biological correctness.
Maturity
Established
Current released schema with maintained APIs, validation, extensions, and DANDI use