International organisation for standardisation organisation internationale de normalisation

2.2Output documents related to MPEG-7 Visual

No.	Title	TBP	Available
	15938-3 Visual
10708	Text of ISO/IEC 15938-3/PDAM 4 Video Signature Tools	N	09/07/10
10709	MPEG-7 Visual XM 36	N	09/07/10
10710	Description of Core Experiments in Video Signature Description development	N	09/07/03
10711	Disposition of Comments on ISO/IEC 23000-3/PDAM 2	N	09/07/03
10712	Text of ISO/IEC 23000-3/FPDAM 2 Conformance Testing for Photo Player MAF	N	09/08/03

3Reconfigurable Video Coding (RVC)

3.1General status of work

The two parts related to RVC (ISO/IEC 23001-4 Codec Configuration Representation in MPEG-B and ISO/IEC FCD 23002-4 Video Tool Library in MPEG-C) were progressed into FDIS status in Lausanne, but some final editing work had been done in Maui, in particular to guarantee a 1:1 matching between the textual description in the FDIS and the software implementation in Amd.1, which together with the conformance testing specification gives the “anchor” reference of normative functional unit (FU) input/output behavior. Some more editing was afterwards that was necessary to achieve better alignment of the texts and definitions in 23001-4 and 23002-4, such that the final texts for publication could only be delivered by the beginning of the London meeting.

Regarding conformance definitions in PDAM1, the previous round of Core Experiments was rather efficient and led to a large degree of clarification about what RVC conformance means both at the FU level and the codec level. This has led to significant improvement of the FPDAM1 text relative to the PDAM text, and was the major topic of work of the RVC breakout group during the London meeting. Further achievements were made towards Amendment 2 (tools for AVC High Profile intra coding). Further activities towards promotion of RVC were another important achievement, particularly including updating of the “RVC Vision” document and preparation of an “RVC tutorial” that gives more illustrative introduction and links to software playgrounds.
It is still the understanding that RVC is still in "phase 1", which is re-implementation of existing decoder conformance points as follows:

• 
  MPEG-4 SP and MPEG-4 AVC CBP in FDIS
  
• 
  MPEG-2 MP, MPEG-4 ASP, AVC HP and SVC to follow in Amd.2.
  

Due to ongoing investigation about best way of defining CABAC related parsers in the RVC/BSDL context, as well as due to the time that needed to be spent on the finalization of text and software/conformance issues, the progress on Amd.2 has been slower than expected, such that issuing the PDAM will be delayed by at least one more meeting cycle.

"Phase 2" could open up more of the options that were previously discussed in the RVC context, particularly including

• 
  Possible simplification of standards development by adding new FUs. Whereas this approach sounds attractive, it appears clear that a real simplification (by adding / exchanging single FU modules) would only be given for cases where a preceding standard is fully implemented in RVC schema – it needs to be clarified whether RVC-based encoders are necessary in this context as well. First investigations on this were reported and will be continued in Core Experiments.
  
• 
  downloadable (on the fly) decoder solutions
  

It should be noted that some of these aspects would already be possible for “phase 1”, as long as no complete new tool definitions are required, as would e.g. be the case for definition of a new profile.