- From: Felix Sasaki <fsasaki@w3.org>
- Date: Fri, 31 Aug 2012 14:46:01 +0200
- To: Yves Savourel <ysavourel@enlaso.com>
- Cc: public-multilingualweb-lt-tests@w3.org
- Message-ID: <CAL58czpvgtt0z=nfOFvPciT7HCyrP0-ShTxt8n72BxVxMNi+PQ@mail.gmail.com>
Hi Yves, all, thanks for the feedback. 2012/8/31 Yves Savourel <ysavourel@enlaso.com> > Hi Felix, all, > > Yes, you assumed right. Your example is what I had in mind. > > I think a tab-delimited output would be easier to compare with simple diff > tools. It would allows implementers to use the same files for their unit > tests, making the validation enforced automatically at each build. > > We would also need to sort the entries of the attribute items I think. XML > parsers have no requirement to present attribute in a specific order and > they do it differently. We could sort alphabetically for example. > > When a data category has several pieces of information, we should always > output them in the same order, even when absent/empty. > > > > Some questions are: > > - would the output be written with ITS namespaces, e.g. > its:translate="yes" vs. "translate="yes" > then let's go for the version with the prefix. We just need to be sure that it has a prefix in each case, no matter if the information is created by a local "its:translate" attribute, a global "translateRule" which has "translate" attribute with no prefix, or by HTML "translate" which is again in no prefix. I think no matter what the information comes from, the output should always be the same. > > Either way would be fine. > > > > - do we need the other information in XML file, e.g. "new value global" > etc? I'd say no, just asking > > +100. I think not having outputType in that format would also help *a lot*. > I was going to post an email about it :) > That information is actually not useful in production. It may help > debugging, but production tools may be designed to optimize the tree > decoration to allow for larger documents, and not have this available. A fter all outputType doesn't test the result, but how you obtained the > result. > Good :) Leroy or others working on the test suite - is above description enough for you to change the test suite output? Could you also add a small description of how the result files look like to the test suite main page? Both items are not critical for the W3C staff Tuesday meeting on testing - if you just let me know whether there are any general issues, that's OK. Best, Felix > > Cheers, > -yves > > > > -- Felix Sasaki DFKI / W3C Fellow
Received on Friday, 31 August 2012 12:46:30 UTC