TIPP: Validator tool should ensure that rules in spec, but not XSD, are followed

[GoogleCodeExporter]

Describe the issue here:
- The XSD for TIPP 1.5 does not attempt to spell out every last behavioral 
expectation. Therefore, a tool can create a TIPP manifest that tests out 
against the XSD as valid, but violates many of the rules set out in the TIPP 
specification. For example, with the task type translate-strict-bitext, there 
must be 1 XLIFF:doc file, there cannot be 0 files, or 2+  XLIFF:doc files. 
- Request is to add something to the jtip sample code to check for these sort 
of more in-depth compliance requirements. 

Original issue reported on code.google.com by micah...@gmail.com on 17 May 2013 at 2:48