This is a REST service that validates an HML file according to a MIRING checklist, and returns a XML report specifying any encountered MIRING or HML infractions.
You can import this project into eclipse (Import as a Maven Project), or use the text editor of your choice. I recommend you use java 1.8 and MAVEN to build.
Build MiringValidator.war file using MAVEN:
$ mvn clean install
Deploy /target/MiringValidator.war to your Tomcat 8.0 server, or run within MAVEN:
$ mvn clean install tomcat7:run-war
Once your tomcat server is running, you should find the web interface at:
http://localhost:8080/MiringValidator
MIRING stands for Minimum Information for Reporting Next Generation Sequence Genotyping, and represents a minimum checklist of data to be included in a NGS report.
MIRING is independant of data platform, but this validator is based on HML 1.0.1.
See a MIRING Compliant HML sample at http://schemas.nmdp.org
MIRING: http://biorxiv.org/content/early/2015/02/16/015230
HML: http://biorxiv.org/content/early/2015/02/06/014951
MIRING rules are based on 8 general elements:
Message Generator Contact Information & Document Identification
The validator further divides these elements into rules. For more information on MIRING elements and a rule ID reference, see http://miring.b12x.org/MoreInfo.html or the local github wiki HERE.
This validator engine is powered by SAX Parser and Probatron4j, an excellent implementation of Schematron
- The Jersey REST endpoint for MIRING validation is:
http://localhost:8080/MiringValidator/validator/ValidateMiring - This is based on:
- WAR deployed as
MiringValidator.war(context path:/MiringValidator) - Servlet mapping:
/validator/* - Jersey resource:
@Path("/ValidateMiring")
- WAR deployed as
- The REST service expects a form parameter named
xml(notxml[]). - The XML payload should be sent as the value of this parameter.
curl -X POST --data-urlencode "xml=$(cat WebContent/hml/hml_1_0_1_example_miring.xml)" \
http://localhost:8080/MiringValidator/validator/ValidateMiring- This will POST the contents of your HML XML file to the correct endpoint and parameter.
- 404 errors usually mean the context path, servlet mapping, or resource path is incorrect.
- Always check WAR name, web.xml servlet mapping, and Jersey
@Pathannotations.
_Last updated: 2026-01-16 by Jason Brelsford
~