Test case data has 3 main areas:
1. Test case identification
- identifying and categorizing a test case within a catalogue within a suite of catalogues
2. Test case documentation
- documenting a test case and how it is relevant - for some cases, providing data that allows the test to be applied only against those processors that behave the way it anticipates
3. Operational parameters
- identifying the file path of the base location from which the test is executed - identifying the inputs - specifying names for outputs - specifying (abstractly) the style of invocation - specifying (abstractly) how actual and reference outputs are compared
ii) Certain information items are inspired by the Dublin Core names for similar concepts, though no attempt is made to preserve the case of letters used in any names described therein. ref: http://purl.org/DC/documents/rec-dces-19990702.htm
iii) Most values will be interpreted as strings. Values can be interpreted numerically, specifically in inequality relations, when they refer to versions and dates.