VarioML is a flexible framework which can be used as a template for developing serialization formats for variation data focusing on the LSDB (Locus Specific Mutation Database) use cases. Several data formats come pre-defined, but VarioML elements function as building blocks that can be restructured to fit different implementations to build new data exchange formats - from patient-centered formats to aggregated variant data formats. Originally an XML/RelaxNG framework, VarioML has been rebuilt using JSON Schema.
VarioML was first developed in the GEN2PHEN program from 2011 - 2013 and it was based on an observation model developed there. A simplified UML model can be found here. VarioML has since been reimplemented in JSON, and we're currently working on improviding the documentation with more examples.
VarioML is a collaborative, community-driven specification in active development. If you'd like to collaborate with us, please let us know through admin at varioml.org, or feel free to create an issue.
When using or discussing VarioML, please refer to:
- All new implementations should use validation to ensure consistency with the core specification. When using Schematron, contact admin at varioml.org for help with generating validation scripts.
- Use standard ontologies for the content, such as the Sequence Ontology and VariO. Some LSDB specific terms are defined using SKOS vocabularies.
- Source attributes in database xrefs (such as
ref_seq) as well as ontology terms should use database abbreviations defined in the MIRIAM registry. For example, use
hgnc.symbolfor gene names,
refseqfor NCBI reference sequences, and
obo.sofor Sequence Ontology references.
The JSON implementation is a clean redesign from the VarioML XML format, and our current focus. A JSON schema is provided to validate your data files, to provide descriptions and examples, and as the template for the documentation.
- LOVD3 uses VarioML in all its recent APIs (both the submission API first released in 2016 and the new data retrieval API to be released in 2021). The new data retrieval API uses the GA4GH Table Discovery API wrapped around VarioML data objects.
- See an example implementation written for the LOVD3 submission API.
- For the basic JSON Schema, see either the LSDB object's JSON Schema example based on the XML implementation, or the clean reimplementation which is still work in progress.
A translation for EXI is supported using the Excificient library. XML validation is supported using Schematron.
- 2021-03-02: We'll be updating the documentation on the JSON implementation. Please bear with us.
- 2016-09-10: Libraries updated. NEMDB Examples added.
- 2012-08-19: Population changed to singleton in frequency. This does not have an impact in any existing XML implementations (the property is not used).
- 2012-08-08: Gene has changed to a list of genes. One variant may have impact on more than one gene.
- 2012-08-08: EXI binary XML support added. EXI can reduce the size of memory usage by 3-~10 times, already even without compression.
- 2012-02-09: JAXB / JSON (based on Jackson) API implementation is in org.varioml.jaxb folder. The code has not been fully tested. The SimpleXML implementation will be retired (support is possible though).
- Comments/feedback: admin <> varioml.org. Please send us an email if you are using VarioML so that we can accommodate your requirements!
VarioML has received funding from the European Community's Seventh Framework Programme (FP7/2007-2013) under grant agreement number 200754 - the GEN2PHEN project.