- From: Tatiana Gornostay <tatiana.gornostay@tilde.lv>
- Date: Fri, 5 Oct 2012 16:54:08 +0300
- To: Felix Sasaki <fsasaki@w3.org>, "public-multilingualweb-lt@w3.org" <public-multilingualweb-lt@w3.org>
- Message-ID: <AC6FD4BB9BB02540AC7322091A6C3B5472B00D6EBE@postal.Tilde.lv>
Dear Felix, Dear All, It's done for Tilde terminology use case. With best wishes, Tatiana From: Felix Sasaki [mailto:fsasaki@w3.org] Sent: Friday, October 05, 2012 10:12 AM To: public-multilingualweb-lt@w3.org Subject: [All] testing - reminder (due TODAY) and "how to": please fill in testing table Dear all, this is a reminder to fill in the test suite table at https://docs.google.com/spreadsheet/ccc?key=0AgIk0-aoSKOadG5HQmJDT2EybWVvVC1VbnF5alN2S3c#gid=0 by today. Also, a clarification: ITS 2.0 has conformance statements: if you implement a data category, you must do it 1) globally or locally, in each case taking overriding, inheritance and defaults into account (if applicable) 2} in HTML or XML Combinations of 1) and 2) are fine too, e.g. HTML locally, XML globally. Now, how does this relate to the test suite? If you implement a data category globally, just MUST do testing for all tests that are available for global (for XML or HTML or both - that's your choice). An example: for nearly all data categories you have global embedded or linked rules, at least for XML. It is not possible to do cherry picking, that is do only embedded or linked rules testing. Why is that? See this from the point of view of a user: if you claim conformance to implement a data category, globally, the user wants to see if you implement all aspects of global. Above explanation is specific to global, but the same is true if you implement something locally. I hope that this clarifies things - let me know otherwise. Please be prepared for a sanity check of the test suite current state on Monday. Best, Felix -- Felix Sasaki DFKI / W3C Fellow
Received on Friday, 5 October 2012 13:54:40 UTC