- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Wed, 24 Oct 2007 14:33:49 +0200
- To: Dmitri Silaev <Dmitri.Silaev@Sun.COM>
- Cc: public-mwts@w3.org
Hi Dmitri, As we discussed during the call today, here are more details on the SVG Tiny 1.2 work item: * the SVG Working Group released a beta version of its test suite early September, available at: http://www.w3.org/Graphics/SVG/Test/ * the OMA IOP browsing group would like to integrate that test suite as part of their work; to that end, they need to understand better how much of the SVG Tiny 1.2 Specification [1] is actually covered; more precisely, they would like to know how many of the requirements documented in their "Test Enabler" document are covered by the test suite * the Enabler document is available at: http://lists.w3.org/Archives/Member/member-mwts/2007Oct/att-0006/OMA-ETR-SVG_Mobile_Domain-V1_0-20070424-D.zip So, the goal of this project is to look at the list of requirements (section 5 of the Enabler document), and identify which are tested in the beta test suite. There are several aspects to it: * it should be made in cooperation with the SVG Working Group; * the SVG Working Group may be able to do most of the work quickly (e.g. if they know their test suite well enough to identify what is and is not covered), or ask us to do it for them if they don't have enough resources * if they don't have the resources, we need at least a detailed plan on how to proceed for the coverage analysis - depending on the amount of work, we may need to split the work among us, or maybe a single person can do it A first good step would be to draft/send a message to the SVG Working Group. Let me know if this clarifies what needs to be done, Dom 1. http://www.w3.org/TR/2006/CR-SVGMobile12-20060810/
Received on Wednesday, 24 October 2007 12:34:22 UTC