Re: Test suite output format

Thanks, Leroy. No need to hurry, what we have now is sufficient to discuss
the test suite format w3c internally.

Best,

Felix

2012/9/3 Leroy Finn <finnle@tcd.ie>

> Hey Yves,Felix,
>
> Thanks for your examples about this tab-delimited output.  This will take
> a few days to update the actually test suite and then to run all the test
> files so i don't think it is possible to get this all done by tomorrow.
>  But i can start working on it today and we could possibly aim for some
> stage next week to publish this output. But i will add in the output
> description on the ITS test suite page today based on this tab delimited
> output.
>
> Thanks,
> Leroy
>
>
> On 1 September 2012 13:59, Yves Savourel <ysavourel@enlaso.com> wrote:
>
>> Hi Felix, all,
>>
>> > One question: for some data categories we would have a
>> > lot of values for one node, e.g. loc quality issue in the
>> > standoff version. How would the output look like
>>
>> Maybe simply the list of the expected values, in a pre-defined order,
>> with an empty spot if the value is not present? See attached example. (I
>> have not verified the actual results, but the format should illustrate the
>> idea)
>>
>>
>> > Also, some data categories have XML fragments (elements with
>> > potentially attributes and (mixed) content inside). How to
>> > represent these, e.g. what to do about whitespace stripping
>> > for the XML fragments? I have no preference / idea, just asking.
>>
>> We should probably escape the line breaks to "\n" (and any tab to "\t")
>> and escape any XML constructs. For example if a localization note is:
>>
>> <elem>text  with<tag/>
>> And line-breaks</elem>
>>
>> We would output:
>>
>> its:locNote="text  with&lt;tag/>\nAnd line-breaks"
>>
>> cheers,
>> -yves
>>
>>
>


-- 
Felix Sasaki
DFKI / W3C Fellow