XML-based applications often require the use of an XSLT engine for performing transformations, an XQuery engine for executing queries, and/or an XML parser for well-formedness checking and validation. Altova makes the same engines that drive its award-winning XMLSpy, MapForce, and StyleVision XML development tools available for use in your custom applications. That means you can use the very engines that have helped make Altova software the industry’s leading XML development toolset in your own applications – free of charge!

o XML validating parser
o XSLT 1.0 engine
o XSLT 2.0 engine (schema-aware)
o XQuery 1.0 engine (schema-aware)
o XBRL validation engine

AltovaXML  2010 includes COM, Java, and .NET interfaces so that it can be used from a variety of different applications. You can also call its functionality from the command line. There is no license key code required to activate AltovaXML  2010, and you may use it in your applications royalty-free.

Features are:

o Well-formedness checking
o Validation based on DTD or XML Schema
o XML transformations via XSLT 1.0
o Schema-aware XML transformations via XSLT 2.0
o XML queries and transformations via XQuery
o Validation of XBRL 2.1 and XBRL Dimensions 1.0
o Ability to execute XSLT and XQuery transformations on OOXML data in Microsoft  Office 2007 documents
o Ability to execute XSLT and XQuery transformations on XML files stored in ZIP archives
o Support for processing Java, C#, JavaScript, and VBScript in XSLT stylesheets
o Support for XInclude and XPointer
o Command line operations
o COM interface
o Java interface
o .NET interface

XML and XBRL Validation

· Validates the supplied XML document, returning valid or invalid.
· Validation can be done against the DTD or XML Schema referenced within the XML file, or against an external DTD or XML Schema supplied by a command line parameter or a COM interface property.

· Checks well-formedness of the supplied XML document, separately from validation.
· Validates XBRL documents. The XBRL document is validated against an XBRL taxonomy (which is a .xsd file) according to the rules of XBRL.

XSLT Transformations

· Transforms supplied XML document using supplied XSLT 1.0 or XSLT 2.0 document.
· XML document can be provided as a file via the input of a URL. In the case of usage via the COM interface, the XML document can alternatively be supplied as a text string.
· XSLT document can be provided as a file via the input of a URL. In the case of usage via the COM interface, the XSLT document can alternatively be supplied as a text string.
· Returns output documents at the named location. When called via COM interface can also return output documents as a string.
· XSLT parameters can be supplied via the command line and via the COM interface.

XQuery Execution

· Executes the supplied XQuery 1.0 document, optionally against an XML document named in a command line parameter or a COM interface property.

· XQuery document can be provided as a file via the input of a URL. In the case of usage via the COM interface, the XQuery document can alternatively be supplied as a text string.

· XML document can be provided as a file via the input of a URL. In the case of usage via the COM interface, the XML document can alternatively be supplied as a text string.

· Returns output documents at the named location. When called via COM interface can also return output documents as a string.
· External XQuery variables can be supplied via the command line and via the COM interface.
· Serialization options include: output encoding, output method (that is, whether the output is XML, XHTML, HTML, or Text), omitting the XML declaration, and indentation.