[Implementers] testsuite change + good news about conformance testing

Hi all,

I made a change to the testsuite. testsuiteMaster.xml now contains on 
each inputfile element a conformance-class attribute, e.g.
<inputfile location="inputdata/translate/xml/translate1xml.xml" 
conformance-class="xml-global">
the attribute can have four values: xml-global, xml-local, html-global, 
html-local
These values reflect the four ways to use ITS. (Note that some test 
files contain both local and global rules - these are then categorized 
as xml-global or html-global, since a "local only" implementation is not 
required to process the global rules.)

The testsuite dashboard now contains now this section

http://htmlpreview.github.com/?https://raw.github.com/finnle/ITS-2.0-Testsuite/master/its2.0/testSuiteDashboard.html#conformance-classes-overview

that summarized the state with regards to the types of ITS processing 
implementations.

The good news is that except these four data categories and 
directionality / ruby
  external resource, target pointer, id value, storage size
we already have for each data category at least two tests - that is 
enough to pass the formal testing phase (candidate recommendation).

There is of course still things to do, e.g. "text analysis" update and 
getting from 73% to 80% by the Luxembourg review (=M5). But I'm very 
happy that very likely we can have a rather short conformance testing 
phase: excluding two summer months we had expected 5 testing months, but 
I don't think we will need that and can take more time to finalize also 
explanatory parts of the ITS2 spec. Thanks a lot to all for your 
contributions!

*Not related to the above, but FYI:*

I removed ]init[ from the test suite. This influences Translate, 
Localization Note, Terminology and Locale Filter: these now have 10 
implementers files less (which is not critical for the conformance 
testing). I did that after discussion with ]init[: ITS conformance 
testing in odt files really doesn't make sense - the XML in odt is non 
hierarchial, and the ]init[ implementation does not apply inheritance 
etc. directly to the odt XML. ]init[ will contribute odt example files 
and generated XLIFF output files that reflect the inheritance + defaults 
- that is, "real life" test files.

Best,

Felix