Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DPC Test Suite and a Self-Certification Idea #19

Open
haudiobe opened this issue Oct 20, 2021 · 1 comment
Open

DPC Test Suite and a Self-Certification Idea #19

haudiobe opened this issue Oct 20, 2021 · 1 comment

Comments

@haudiobe
Copy link
Member

  • I learned from some colleagues, how Khronos does a self-certification program.
  • Here is the github on this: https://github.com/KhronosGroup/OpenXR-CTS
  • The basic idea around this is:
    • Khronos provides the test environment (see above)
    • Companies run the tests for themselves and dump the results into a well-defined format
    • Companies can submit the test results to Khronos and Khronos looks at the results and if they are correct (all tests fulfilled) according to their report, then the companies get an OpenXR logo
    • The costs for a company are 25 kUSD to submit the tests and those to be verified and obtain a logo permission
  • At the minimum, I believe we should make sure that CTA WAVE remains sufficient ownership of the assets in order to setup this self-certified logo program.
  • If we get there and this establishes value for both, device manufacturers and content providers, I believe we would have achieved our mission in CTA WAVE. 
  • Comments welcome
@bobcampbell-resillion
Copy link

Currently HbbTV and ATSC would like to refer to the HATF test suite and can't. See #16 for more detail. So, before WAVE tries to build its own Self Cert program, perhaps it should make sure those referencing entities, with linked Certification Logo programs (e.g. Freeeview Play in UK and CTA's NEXTGEN TV logo) in use today, can make use of what its already produced.

There's nothing wrong with setting up a self cert scheme, and indeed we considered it in the early days of WAVE when I chaired the Test and Compliance Task Force, before it was merged into the other groups. But today, outside HbbTV and ATSC's use cases, there is no imperative to get certified - when no regime, or service provider requires it. Therefore its better in my view to focus WAVE's efforts on understanding how to ensure OTT service providers would make use of the specifications in their conformance programs. If that happens then those OTT platforms might be interested in a WAVE certification report as evidence of compliance to a set of requirements that removes a testing need they have to check today. Unless it removes some testing from a platform test program a manufacturer has to do today, they won't bother.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants