XML content can validate perfectly against a DTD or Schema and still be lousy with faults. With XMLProbe you can write the rules that DTDs and Schemas can't express and quality assure your XML to the maximum extent possible with a computer.
DTDs and schemas are just the start …
Bad data costs time and money. XMLProbe can be used to implement an automated content firewall to inspect data as it proceeds through your organisation's workflow. By catching data errors early you can significantly reduce the costs of downstream error correction, and enforce data contracts between partners in the data supply chain.
Use XMLProbe as a content firewall to stop
bad data crossing business process boundaries
Runs on the Java platform
XMLProbe is written in 100% Java and so runs on any JVM capable platform (e.g., Windows NT/2000/XP, Solaris or Linux).
XMLProbe exposes a Java API, so it can be integrated into whatever systems you want, seamlessly.
Use XML to express your business rules
With XMLProbe, rules are expressed in a language appropriate to the complexity of the problem. Sets of rules are XML documents and for most checks the XPath language is used. XMLProbe ships with a powerful library of XPath extension functions for tackling a wide variety of data quality problems.
For tougher problems (e.g. linking to external databases for cross-checking values), the full flexibility of the Java language is on tap for rule expression. If a computer can check it, XMLProbe can express it.
Combine sets of rules to customise your QA suites
As both the complexity and size of QA rules grow, you'll come to appreciate the modular design that XMLProbe allows for designing suites of QA tests. Using standard XInclude technology, XMLProbe allows you to assemble reusable libraries of QA rules than can be combined to form the suites you need.
Differentiate between types of fault
Not all faults are created equal. Some are critical and should 'stop the show', others can be logged and deferred, still others might need a 'judgement call' from a human operator.
XMLProbe has been designed to cope with the real-world complexity of data faults. Each rule can have its own unique ID, meaning rules can be grouped together or treated in special ways according to the context in which the fault occurs.
Pinpoint error locations
Identifying data faults is not enough. XMLProbe reports the line and column numbers as well as an XPath expression for all errors it has identified, allowing you to accurately track down the exact location of each.
Manage your QA reports
Performing quality assurance is only one aspect of a data quality policy - the results of performing such checks must be managed too.
XMLProbe produces QA reports that are themselves XML documents. Such documents are highly amenable to processing by human beings or computer systems. You can for example use the reports to:
- Produce expressive, easy-to-read QA reports as web pages
- Annotate the original XML to show errors 'in place'
- Trigger other automated processes (e.g. email alerting)
- Feed into data-cleansing software
