International organisation for standardisation

8Project planning

8.1WD drafting and software

8.1.1.1.1.1.1.1.1JCTVC-F333 The Art of Writing Standards: Some “Shalls” and “Shoulds” for Better Quality Interop Specs [G. J. Sullivan (Microsoft)]

This document provides informal comments and guidelines on writing standards for interoperability specifications. It was updated from a prior contribution of the previous meeting to include some additional guidance (esp. for spelling) from the higher levels of ITU-T and ISO/IEC.

8.1.1.1.1.1.1.1.2JCTVC-F634 HEVC Reference Software Manual [F. Bossen, D. Flynn, K. Sühring (AHG chairs)] [late reg. 07-04, upload 07-18]

This document is a user manual describing usage of reference software for the HEVC project. It applies to version 3.3 of the software.

No detailed presentation was suggested to be needed for this. The contribution was appreciated.

8.1.1.1.1.1.1.1.3JCTVC-F688 Revised HEVC Software Guidelines [K. Sühring, D. Flynn, F. Bossen (software coordinators)] [late reg. 07-08, upload 07-11]

This contribution provides guidelines for contributors to development of the reference software. It updates the prior JCTVC-C404. It includes updated information regarding the copyright declaration to be used, and provides some comments to help avoid some common problems that have been observed in the work. Some advice was included regarding common sources of bugs, such as improper use of unsigned variable types for loop counters. The excessive use of code duplication was particularly discouraged, as it creates significant problems for future maintenance of the software. Speed optimizations that harm software readability, such as loop unrolling, were discouraged. The use of company names and personal names in macro definitions and comments was discouraged.

It would be desirable if the software used in CEs was also written according to the guidelines.

This was endorsed by the group.

Agreed.

8.1.1.1.1.1.1.1.4General issues

It was noted that design adoptions are only made under condition that software and text delivery is made in a reasonably timely fashion. Also, testing should be performed after integration to ensure that the tool is really performing its intended purpose and not conflicting with other tools. This was Agreed by the JCT-VC.