01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Open analytical-instrument exchange and archival where a supported AnIML technique definition captures the required method and result semantics.
- Limits
- The official schema remains Draft 0.90. Technique coverage, current conformance tooling, vendor support, and independent production adoption are unverified and must not be implied.
- Best for
- Laboratory and Discovery teams working across Acquire → Harmonize → Exchange.
- Maturity
- EmergingUse only in a bounded pilot and expect the specification or tooling to change.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Laboratory and Discovery source data, metadata, and local mappings
- AnIMLWhat changes
Use AnIML as a pinned standard across Acquire → Harmonize → Exchange
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
03
A concrete example
A laboratory validates an AnIML 0.90 document against the exact core, technique schema, and named technique definition while retaining the original vendor file and conversion provenance.
Why it matters: Potentially preserves method, sample, result, and audit context, but draft status and uncertain ecosystem support make conversion validation and source retention mandatory.
04
What it fits with
Overlaps the analytical-data problem addressed by Allotrope but uses public XML schemas and technique definitions. It does not replace ISA-level study design or domain result standards such as mzML.
- Data model / schemaAllotrope
Both support Laboratory and Discovery work and meet around Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - Data model / schemaUDM
Both support Discovery and Laboratory work and meet around Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - StandardInChI
Both support Discovery and Laboratory work and meet around Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata profileREMBI
Both support Laboratory and Discovery work and meet around Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Define one handoff, its accountable owner, and the decision AnIML must support.
Pin the exact version and companion artifacts: Schema 0.90 · Draft.
Map one representative input to the required standard artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Test the main limitation
The official schema remains Draft 0.90. Technique coverage, current conformance tooling, vendor support, and independent production adoption are unverified and must not be implied.
Run one representative end-to-end pilot and record exactly where AnIML loses context, needs an extension, or depends on another standard.
Machine-readable output may still be unfit for analysis or ML.
Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Potentially preserves method, sample, result, and audit context, but draft status and uncertain ecosystem support make conversion validation and source retention mandatory.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
Official AnIML schema repository
Official publisher or steward guidance for this standard profile.
- Publisher
- AnIML Working Group · ASTM E13.15