Personal Views on the Test Plan

1. Personal Views on the Test Plan Jan. 29, 2013 Masahiro Wada

2. contents • Introduction of KDDI and myself 2. My Position on the Testing Plan

3. KDDI’s convergence strategy FTTH CATV

4. Seamless Service Concept • anytime, anywhere When we are going for journey by car….

5. Background • The Open Web Platform has been highly expected as a HW/OS-independent new platform. • The Open Web Platform is planned to be used in various appliances. • The requirements have become advanced in functionality, quality, interoperability and performance. • The Open Web Platform has become very complicated application platform.

6. Is HTML5 perfect ? • Implementation difference exists among the browsers/ OS • In some cases, processing performance of HTML5 is slower than the native apps or flash media. • Difficulty of porting from other platforms (Android Java, Objective-C, C/C++) • Lack of Security functions (DRM, exposure of source code,) • Expect the update of W3C spec. • Proprietary security key management between server and client.

7. Voice of Content Providers in Japan ■Technology Issues ・Most of CPs wait until HTML5 and the products become more stable. ・ Same service level provided by the native application cannot be achieved by the current mobile phone capability. ・ They don’t think to be able to provide satisfactory services to customers yet. ・Security issues (illegal access, DRM, …) ■Business Issues ・ No incentive to move from native application-based to HTML5-based because they are successful now! ・Very doubtful whether Web-based services become real business. ・Some “conducting wire” is necessary for HTML5-based service to become real business.

8. Goal of the Tests • To obtain trust from Industry* that the Open Web Platform is reliable for their products. *non-PC manufacturers like TV and mobile devices, TV broadcasters and telecom operators • Any application /content runs exactly in the same manner as the author intends on any OS on any hardware.

9. Necessary Tests • Specification-based Test To verify the specification and check the conformance of the software products. Performed mainly by W3C. To focus on critical points of the specification • User-viewpoint Test To verify the functionality, quality, reliability, inter-operability and performance of the software products. Carried out mainly by the industries. To test a use case that the specification designers have not thought of.

10. Specification-based Test • Carried out by W3C members? On schedule? • Outsourcing? Tests properly defined in detail? Who analyze and feed back the results? Management? • Sufficient tests? Duplication? Who will examine?

11. User-viewpoint Test • Test content/application approach • Crowd-sourcing is essential • Test Platform is mandatory test guidelines, database of test content/application guidance for authoring, reporting format mechanism for gathering and utilizing the test results process of analysis and feedback of the results • Close relationship to outside parties is beneficial.

12. Development of Test Platform • To write and run tests on the platform and obtain expected test results. • Various stakeholders inside and outside W3C • Various purposes such as implementation and functional or interoperability verification. • Applicable for “both Tests”

13. Test Platform • Concentrated and equipped with all the necessary means of tests • Open for stakeholders outside W3C • Steady operation of the platform • Mechanism for utilizing the test results to improve quality and interoperability • User support such as Q&A • Continual improvement of the platform

14. Way of proceeding • Dedicated Test Lab is necessary for Carrying out the Specification-based Test Hosting and managing the User-viewpoint Test Developing and operating the Test Platform • Important points *On schedule *Appeal of the test successfully ongoing with evidence *Demonstration and exhibition on an appropriate occasion (such as CES)