cta-wave / technical-working-group

7 stars 0 forks source link

Issues to be addressed at the WAVE meeting at NAB 2017 #2

Closed wilaw closed 3 years ago

wilaw commented 7 years ago

WAVE will hold a one-day face-to-face joint workshop for all task forces on Thursday, 4/27, from 9am to 4pm. Lunch will be provided during a 12pm-1pm lunch break.

The format of this workshop will be optimized to discuss issues. which are best debated face-to-face. Issues can be of specific interest to a single TF, or of general interest. We’ll organize breakouts as seem to be appropriate once we have the issues assembled.

This tracker is the means by which these issues are submitted for discussion. To submit a new issue, reply with a new COMMENT on this issue. In the comment, please be sure to add the following information:

  1. Your name as the topic submitter
  2. A brief title to describe the issue
  3. A paragraph describing the issue to be addressed and debated. This will be shown on screen during the NAB workshop while the issue is addressed.
johnsim commented 7 years ago
  1. Title: Regionalization and the content specification Description: What are the regionalized WAVE use cases and how might they impact the content specification? Our discussion about whether 50 vs. 60 Hz. framerate regionalization is necessary has resulted in the need to discuss regionalization use cases which can impact each of our specifications. Elements of this discussion thus far: the assertion that TVs can handle 50 and 60 Hz framerates, that many 50 Hz TVs might not have been adequately tested with 60 Hz content, a TV may handle 50 and 60 Hz framerates fine, but not the dynamic switching of framerates, and that this issue can be even more challenging over HDMI. From this we agreed that we must start by identifying the required use cases and document the requirements these use cases place on our specifications, in this case the content spec.
johnsim commented 7 years ago
  1. Title: Splice conditioning and the content specification Description: Are their splice conditioning requirements that should be including in the content specification? Normative? Informative? Splice Conditioning: There is a need to support single decoder devices and therefore splice conditioning needs to be addressed in the content spec. It was noted that the problem is more complicated that splice conditioning. There will be content that is not conditioned. This needs to be addressed at the DPCTF – what to do when content splices are not conditioned.
johnsim commented 7 years ago
  1. Title: Presentation Profile Requirements Description: What are the requirements for including a Presentation Profile in the content specification? (TBD – already agreed to include but without language on requirements. Here is the draft MSFT proposal from January - 1. Consists of already published WAVE Media Profiles, 2. Unlike media profile, Follows rather than leads industry – at least one service and one device commercially using this presentation profile, 3) Support from six WAVE member companies – OR, Perhaps require that presentation profiles must consist of media profiles which meet 3.2.2.1 market relevance?
bobcampbell-resillion commented 7 years ago

Title: TCTF present overview of their agreed testing approach Description: I can present the slides we have agreed WAVE-Test-Approach-Outline.pptx. There's several specific discussion points that should lead from this that I will list below...

bobcampbell-resillion commented 7 years ago

Title: Who should be able to access a WAVE test suite? Description: Only WAVE members, only customers of testing companies, general public ? Or are all available, but with different levels of usefulness?

bobcampbell-resillion commented 7 years ago

Title: How will WAVE compliance testing be conducted? Description: The TCTF is planning to ensure that its work allows for a WAVE compliance program. Its so far not been resolved whether that might be operated by WAVE itself, and how that testing will be conducted. Could involve aspects of self-test, 3rd party managed, commercial qualification program, even a logo program...

bobcampbell-resillion commented 7 years ago

Title: What are the set of test areas in scope for WAVE testing? Description: TCTF is proposing 3 levels of breakdown

  1. test area – see suggested breakdown slide 8 of test approach deck.
  2. test group – groups of related tests E.g. closed caption test playback, seamless switching playback, tests for JS object X, roughly corresponds to rows in the current Google doc.
  3. test case – most atomic test case that tests a single clause in the spec. Test case maps 1-to-1 with test assertion. Does the high level test area set match expectations?
bobcampbell-resillion commented 7 years ago

Title: How will the work to define a high level test plan be allocated between TFs? Description: A test plan gives you an idea of what full coverage would be, but does not incur the costs of development (yet). It will allow WAVE to identify which test case(s) are covered by member contributions and where there are gaps. To create this test plan there are a number of steps and it requires expertise from the "subject matter expert" TFs as well as the TCTF. See slide 9 of test approach deck. Does the allocation match expectations, and if so, do the TFs have capacity to do the work in a timeframe that meets the overall schedule?

bobcampbell-resillion commented 7 years ago

Title: What are the requirements of the WAVE test environment? Description: The TCTF has proposed a number of test tools (see test approach deck slides 12-17) and has agreed a number of use cases in https://standards.cta.tech/apps/org/workgroup/tctf/download.php/19752/tctf-00013-v003-WAVE%20Test%20Approach.docx)

What are the high priority/key requirements for the test environment?