Back to Search Document details
17th Meeting: Brussels, January 2020 2020-01-07 09:04
JVET AHG report: High-level syntax (AHG9)
Abstract
This AHG report summarizes the activities of the AHG on High-level syntax (HLS) between the 16th JVET meeting in Geneva, CH (1-11 October 2019) and the 17th JVET meeting in Brussels, BE (7-17 January 2020).
JVET-Q0009 JVET AHG report: High-level syntax (AHG9) [R. Sjöberg, J. Boyce, B. Choi, S. Deshpande, M. M. Hannuksela, R. Skupin, A. Tourapis, Y.-K. Wang, W. Wan]

This AHG report was discussed Tuesday 7 January 2020 at 1020 (chaired by GJS).

This AHG report summarizes the activities of the AHG on High-level syntax (HLS) between the 16th JVET meeting in Geneva, CH (1–11 October 2019) and the 17th JVET meeting in Brussels, BE (7–17 January 2020).

It is reported that the estimated number of input contributions related to high-level syntax has increased from 137 at the 16th JVET meeting to 188 at this 17th meeting.

It is noted that the first day of the 17th meeting in Brussels was announced on the reflector on November 6 to be devoted to high-level syntax related topics.

An e-mail reflector discussion on HLS planning took place. The discussion was summarized by the AHG as the following lists of suggested actions:

Suggested actions to handle HLS input contributions at this meeting:

  • Encourage joint contributions to reduce the number of documents
  • Allocate more meeting time for HLS compared to low-level work
  • Let software availability impact the presentation times of HLS proposals

Suggested actions for future meetings:

  • Require that software is provided with HLS contributions, preferably also require cross-checks
  • Prioritize missing HLS adoptions for VTM-8 integration
  • Allocate much earlier time slots for the HLS-related implementation work
  • Define test conditions for HLS aspects (e.g. scalability, RPR, subpictures) to ensure that the software works as expected

It was commented that we need greater clarity on who is responsible for providing software for contributions that merge proposals from different organizations.

It was also commented that when we have some part of the design that has not yet been adequately implemented in the software, the focus should be on getting that problem fixed rather than making additional refinements of the non-implemented feature.

Decisions
It was also commented that when we have some part of the design that has not yet been adequately implemented in the software, the focus should be on getting that problem fixed rather than making additional refinements of the non-implemented feature.
Citation