Skip to content

Reporting Standard S.L. has created an XBRL 2.1 validation module that satisfies 100% requisites in the XBRL 2.1 specification.

The validation engine can be installed in an Accelerated Validation mode. In this case, the validation engine can be installed as a software component integrated in an existing infrastructure. The component can be launched from a web page or can work as an application without a GUI. In this situation, the validation of instance documents can be accelerated even to report the result online (about 200 milliseconds for the validation of an instance with 300 elements and a taxonomy with 5000 elements) the taxonomy must be defined and it must be loaded in memory in order to launch the accelerated validation.

XBRL International has created this set of conformance suite test cases to check if XBRL processors satisfies the requirements stated in the specification. There are more than 300 different test cases covering all aspects and possible uses of XBRL.

This page shows how Reporting Standard validation engine satisfies all test cases. The page content is created automatically while each test case is executed. All test cases are executed one by one. The page shows that the XBRL 2.1 validation engine created by Reporting Standard manages all test cases according to the requirements in the documentation. All errors are detected and all valid test cases are processed accordingly.

You can test yourself how Reporting Standard processor satisfies all test cases in the XBRL conformance suite. If you are interested in doing so you need to download the set of test cases indicated abobe and download the samples.jar file from this web site. Then, review the source code of the Java class: com.ihr.xbrl.LaunchConformanceSuiteXHTML and launch a java virtual machine with parameters: -f {path to XBRL conformance suite}/conformance/xbrl.xml -m -o results.xhtml

Explanation:
The parameter -f must point to the xbrl.xml file that is the head of the XBRL conformance suite.
The parameter -m tells the tool to report memory usage.
The parameter -o tells the user about the file name for the output file to be generated. That page will be an XHTML page and you can open it in a browser.