[ISO/IEC] ISO/IEC JTC 1/SC 29 N 2913
DATE: 1999-01-06
REPLACES: --

ISO/IEC JTC 1/SC 29

Coding of Audio, Picture, Multimedia and Hypermedia Information

Secretariat: Japan (JISC)

DOC. TYPESummary of Voting
TITLESummary of Voting on Combined CD Registration and CD Consideration Ballot on ISO/IEC CD 13522-7: Information technology -- Coding of multimedia and hypermedia information -- Part 7: Interoperability and conformance testing for ISO/IEC 13522-5
SOURCESecretariat, ISO/IEC JTC 1/SC 29
PROJECT NO.JTC 1.29.06.07 (13522-7)
STATUSBallot result to be reviewed by WG 12
REFERENCES SC 29 N 2743: CD
ACTION ID.ACT
REQUESTED ACT.WG 12 is requested to prepare a disposition of comments report, a revised text and a recommendation on further processing of this work item.
DUE DATE--
NO. of PAGES
FILE SIZE (KB)
DISKETT NO.
ISSUE NO.
FILE NAMES
ACCESS LEVEL
LANGUAGE USED
N/A
17.3 (except isoiec.gif)
29D297
29F202
isoiec.gif, 29n2913c.htm
Def
English
DISTRIBUTION SC 29 P, O and L-members; SC 29 Officers;
JTC 1 Secretariat; ISO/IEC ITTF

Narumi Hirose, Secretariat, ISO/IEC JTC 1/SC 29
IPSJ/ITSCJ*, Room 308-3, Kikai-Shinko-Kaikan Bldg., 3-5-8, Shiba-Koen, Minato-Ku Tokyo 105-0011 Japan
Telephone: +81-3-3431-2808; Facsimile: +81-3-3431-6493; E-mail: hirose@itscj.ipsj.or.jp
* Information Processing Society of Japan/Information Technology Standards Commission of Japan (A standards organization accredited by JISC)


Summary of Voting on
Combined Ballot of CD Registration and CD Consideration
ISO/IEC CD 13522-7
Information technology --
Coding of multimedia and hypermedia information --
Part 7: Interoperability and conformance testing for ISO/IEC 13522-5
National BodyCD registrationCD considerationNo VoteComments
Approval
*:Comments
Disapproval AbstentionApproval
*:Comments
DisapprovalAbstention
P-member
Australia X

X



Belgium X

X



Brazil X

X



Canada X

X



China X

X



Czech Republic X

X



Denmark X

X



Finland X

X



France





X
Germany X *

X *


Comments
India





X
Ireland X

X



Israel X

X



Italy X

X



Japan X *


X #

Comments
Korea, Rep. of X

X



Netherlands X

X



Norway X

X



Poland X

X



Portugal

X

X

Romania





X
Russian Federation





X
Singapore





X
Spain X

X



Sweden X

X



Switzerland X

X



UK X *

X *


Comments
US

X

X

Total (28) 2102 2012 5

#: Acceptance of the reasons and appropriate changes in the text will change the vote to approval.


Germany

1. The single steps in the test case scenarios should be numbered. This would simplify referencing the steps from other test cases or in error reports. A proposal is to change the "control_observe" definition of the format of the scenario part to:

control_observe ::= "(" <INTEGER> ")" [control] [observe] .

2. MHEG-7 does not specify the format of the identifier of the test cases. It should, however, be unified for easier exchange of and referencing to test cases. A format could be the following:

idformat ::= <INTEGER> "." <STRING> [ "." <INTEGER> ].

The first integer value (2 digits) refers to the number of the class as defined in annex F. The string value could be the name of the class or further information. The second integer value is optional and can be used to specify the number of a sub-test case.


Japan

1. CD registration

The scope of this part of ISO/IEC13522 should be both test procedure document and its accompanying test data on MHEG-5 interoperability and conformance testing.

2. CD consideration

1 (G) The scope of this part of ISO/IEC 13522 should be both test procedure document and its accompanying test data on MHEG-5 interoperability and conformance testing. Hence, they should be normative parts.

2 (G) As for the conformance criteria, it should be clearly said that test case adaptation by an application domain is permitted no more than (1) Test case selection, (2) Macro replacement, (3) Content coding conversion and (4) Addition of local test cases.

3 (T) Each test data should be organised, in principle, as one scene per one test case, in order that test can be processed separately.

4 (T) Input events used in each test case should not be application specific. To accomplish this, input events should follow those specified by DAVIC.

5 (T) Attributes to be in Macro representation should be clearly defined and their Macro names should be consistent through all test data.

6 (G) The NHK profile supplied as an Annex should be replaced by the final ARIB profile which is actually used.

7 (G) Each test data should be checked by no less than two bodies.


UK

  • General comments

    1. There are several typographical errors in the text, some of which are pointed out in the comments by clauses below. A pass through with a word processor spell check should be done as soon as possible to pick up any that the reviewers miss.

    2. A paragraph describing the contents of the Annexes A - F should be added someplace early on in the text. Where this should be located is a decision left to the editors.

    3. Once the final draft of the MHEG-5 COR1 has been sent for publication this text should be checked against it to ensure consistency between the clarifications made in the COR and the test case procedures and results expected. They may be especially true for the ListGroup class and StreamEvents.

    4. Some Acronyms, like UIT, TBA, and N/A should be expanded in a note on the page where they first appear.

    5. Copyright ownership with regard to the UK DTT specification is mentioned but it is not clear what are the implication of this for users, or what exact part of the Domain Definition this applies to.

    6. For Davic the version, 1.3, is clearly stated, but what is the case for the UK DTT, the NHK, and the JISC specification. How will newer versions of these Specification as they appear affect the MHEG-7 maintenance procedures, or even the progress of the standard to the IS level.

    7. The number of test cases will have to be expanded, even in this version if the Standard is to be really useful for implementers.

  • Comments by section and clause number and designated as Editorial

    3.1 last sentence

    Change monomedia to: media

    4. line 11

    Change guaranteed to be stable to : stable (can we really determine when a DD is guaranteed to be stable )

    5. 4th paragraph

    Change that we cannot use to: it is not feasible to use
    Change As an alternative we can define and develop to: Alternatively the

    5. 5th paragraph 2nd bullet

    Change on the other which to: that

    5. last paragraph

    remove workable

    6.

    7. Note 2

    The reference is missing from the end of the sentence

    8.1 1st paragraph

    The reference source did not print out.

    2nd paragraph 3rd bullet

    Change behaviours the to: behaviours according to the

    8.2.1 4th paragraph

    The reference source did not print out

    5th paragraph

    Change status notation is as follows to: status notation of the MHEG-5 requirements column is as follows

    Table 1 heading in column 5
    Expand the IUT acronym in a note to table.

    6th paragraph

    There is a need to explain what are the values or notation that will be found in the Application Domain column of the PICS feature list.

    Note that the template in Table 1 is not consistent with the PICS Table of Annex F, which does not contain the Application Domain Requirements column

    8.3 2nd sentence

    Change should to: shall

    8.3.2 4th paragraph last sentence

    Change may be should to: shall

    8.4 1st sentence

    Change utilises to: use

    A.4 1st Sentence

    Reference Source not printed out

    A.6 1st sentence

    Add: the following table, to the end of this sentence.

    A.7 1st sentence

    Missing table reference at end of sentence

    Table A.4 row 9

    Change >129 to: >128

    Note this table is duplicated in the hard copy of the standard.

    A.10 Table A.5 row 14

    Change support to: supports

    Note: this table and Table A.6 are also duplicated in my hard copy

    Annex B

    TBD and perhaps other acronyms should be expanded here.

    F.1 1st Paragraph last sentence

    Change DAVIC13 to: DAVIC1.3

    2nd paragraph 1st sentence

    Change the status to: the MHEG-5 Requirement status

    2nd, 3rd, 4th, and 5th bullets

    The status notation references I, O, C, and X are missing

    G.1 last entry in last row

    Change sLink to: Link

    Note: acronym RTE should be expanded here

    G.3 6th row Description

    After from 0% to 100% the sentence need to be fixed. Perhaps it should read as a new sentence: 100%. The transparent bitmap is alternated with updates to the banner text object at the top.

    G.7 10th row External events

    Add KEY2 to the list of events

    G.8 10th row External events

    Same comment as in G.7 above

    G.9 9th row enterTest observe

    Change blue ground to: blue background

    G.11 9th row main observe 10 & 2)

    Change Hotspot brinks to: Hotspot blinks

    G.12 7th row Description penultimate sentence

    Change diffrent to: different

    G.14 5th row Purpose

    Change object. To: objects.

    G.15, G.16, G17, & G.20 5th row Purpose

    Change objectes to objects

    Note: a search and replace on this word should be done on the complete document.

    G.20 8th row control observe

    Change disageared to: disappeared (in two places)

    G.28 6th row Description

    Change runned to: run

    9th row External events

    remove Prev from the list of events

  • Technical

    A.2

    It is not clear what is the intent of this clause. Is it simply saying that the ASN.1 BER or the DER can be used as the interchange format. As it is written it is confusing and leads one to believe both shall be used at the same time

    D.2 Same comment applies as in A.2 above

    G.5 Row 6 Description

    Description ends abruptly with comment that This test requires improvement. Obvoiusly more work needs to be done on this test and description

    G.19 Row 6 Description

    Description refers to "there should not be much time delay". This is a subjective indefinite criterion. Perhaps we need to clarify what is meant by "much time delay". Maybe the terms user unacceptable time delay are better.