CAN/CSA-ISO/IEC 13522-7-02 (R2011)

Foreword
1 Scope
  1.1 Context of the scope
  1.2 Scope
2 Normative references
3 Terms and definitions
4 Document structure
5 Objectives of conformance testing
6 Rationale for MHEG-5 application conformance testing
7 Test suite complexity
8 MHEG-5 profile identifier
  8.1 Definition of the profile identifier
  8.2 Attribute registration
  8.3 Syntax description of the profile identifier
  8.4 How to use the profile identifier
9 Framework for conformance testing
  9.1 Overview of the testing process
  9.2 Documents for testing
  9.3 Test notation
Annex A (informative) - UK Digital Terrestrial Television
                        application domain profile
A.1 MHEG-5 profile for the UKEngineProfile1 application
     domain
A.2 Object interchange format
A.3 Set of classes
A.4 Set of features
A.5 Content data encoding
A.6 Attribute encoding
A.7 UserInput registers
A.8 Semantic constraints on the MHEG-5 applications
A.9 EngineEvent
A.10 GetEngineSupport
A.11 Protocol mapping and external interaction
Annex B (informative) - ISDB (Integrated Services Digital
                        Broadcasting) application domain
                        profile
B.1 MHEG-5 profile for the ISDB application domain
B.2 Object Interchange Format
B.3 Set of classes
B.4 Set of features
B.5 Content data encoding
     B.5.1 Content encoding
     B.5.2 Attribute encoding
B.6 UserInput registers
B.7 Semantic constraints on the MHEG-5 applications
B.8 EngineEvent
B.9 GetEngineSupport
B.10 Protocol napping and external interaction
B.11 Resident programs
     B.11.1 Date and time functions
     B.11.2 Random number function
     B.11.3 String manipulation functions
     B.11.4 Table manipulation functions
     B.11.5 EPG related functions
     B.11.6 Group program reservation functions
     B.11.7 Program Index function
     B.11.8 Persistent memory functions
     B.11.9 WWW related function
     B.11.10 Other MHEG related functions
     B.11.11 Two way transmission related functions(base
             level)
     B.11.12 Two way transmission related functions(high
             level)
Annex C (informative) - JISC (Japanese Industrial Standards
                        Committee) Application domain profile
C.1 MHEG-5 profile for the JISC application domain
C.2 Object interchange format
C.3 Set of classes
C.4 Set of features
C.5 Content data encoding
     C.5.1 Content encoding
     C.5.2 Attribute representative
C.6 InputEventRegister
C.7 Semantic constraints on the MHEG-5 applications
     C.7.1 Constraints on GetEngineSupport
C.8 EngineEvent
C.9 GetEngineSupport
C.10 Protocol mapping and external interaction
C.11 ResidentPrograms
Annex D (informative) - DAVIC Application Domain Profile
D.1 Introduction
D.2 Object interchange format
D.3 Set of classes
D.4 Set of features
D.5 Content data encoding
     D.5.1 Attribute Encoding
D.6 UserInput registers
D.7 Constraints on the use of variables
D.8 Semantic constraints on the MHEG-5 applications
D.9 EngineEvent
D.10 GetEngineSupport
D.11 TransitionEffect parameter of the TransitionTo
     elementary action
D.12 MHEG-5 resident programs
     D.12.1 Date and time functions
     D.12.2 Random number function
     D.12.3 String manipulation functions
     D.12.4 Miscellaneous functions
D.13 Protocol mapping and external interaction
Annex E (informative) - Examples for profile identifiers
E.1 Japanese profile JTC1
     E.1.1 International ID
     E.1.2 Domestic ID
Annex F (informative) - PICS table
F.1 PICS Table template

Scope 1.1 Context of the scope ISO/IEC 13522 specifies the coded representation of multimedia/hypermedia information objects (MHEG objects) for interchange as final form units within or across services and applications, by any means of interchange including local area networks, wide area telecommunication or broadcast networks, storage media, etc. ISO/IEC 13522-5:1997 defines the MHEG-5 object classes for interchange and use in base-level applications intended to be run on limited resource terminals such as set-top-boxes in such contexts as interactive broadband services. Annex F of ISO/IEC 13522-5:1997 specifies the features that need to be defined by a specific MHEG-5 application domain. The informative annexes of this part of ISO/IEC 13522-5:1997 give illustrative examples of profiles of some common application domains. 1.2 Scope MHEG-5 engines are system or application components that handle, interpret and present MHEG-5 objects. The scope of this part of ISO/IEC 13522 is to define a test suite that can be used to test an MHEG-5 engine.s conformance to a specific application domain. It also defines a format for test cases that can be used to extend the test suite, either for more detailed testing or for extensions defined by the application domain. It is beyond the scope of this part of ISO/IEC 13522 to define tests for engine performance, engine memory usage or for MHEG-5 applications that run on these engines. This part of the ISO/IEC 13522 specifies test cases for all features of ISO/IEC 13522-5:1997. Application domains define a subset of MHEG-5 features that must be supported. In order to test conformance to a specific application domain, a corresponding subset of the test cases must be defined. This subset of the test suite is then used to test the conformance of the engine. This part of ISO/IEC 13522 tests conformance of the behaviour of an MHEG engine. It does not validate the physical presentation of MHEG-5 objects. The test suite comprises a set of test cases and a corresponding set of test objects. The test cases are defined in terms of: . test purpose; . objects and procedures which are to be used to test one or more MHEG-5 features; . expected result. A set of content data will be provided for the test objects. These content data are intended as a guide for generating a test suite and should be converted or replaced by content formats appropriate to the Application Domain. A test suite for an Application Domain shall be generated by using the PICS template in subclause 9.2.1 PICS Template.

Scope 1.1 Context of the scope ISO/IEC 13522 specifies the coded representation of multimedia/hypermedia information objects (MHEG objects) for interchange as final form units within or across services and applications, by any means of interchange including local area networks, wide area telecommunication or broadcast networks, storage media, etc. ISO/IEC 13522-5:1997 defines the MHEG-5 object classes for interchange and use in base-level applications intended to be run on limited resource terminals such as set-top-boxes in such contexts as interactive broadband services. Annex F of ISO/IEC 13522-5:1997 specifies the features that need to be defined by a specific MHEG-5 application domain. The informative annexes of this part of ISO/IEC 13522-5:1997 give illustrative examples of profiles of some common application domains. 1.2 Scope MHEG-5 engines are system or application components that handle, interpret and present MHEG-5 objects. The scope of this part of ISO/IEC 13522 is to define a test suite that can be used to test an MHEG-5 engine.s conformance to a specific application domain. It also defines a format for test cases that can be used to extend the test suite, either for more detailed testing or for extensions defined by the application domain. It is beyond the scope of this part of ISO/IEC 13522 to define tests for engine performance, engine memory usage or for MHEG-5 applications that run on these engines. This part of the ISO/IEC 13522 specifies test cases for all features of ISO/IEC 13522-5:1997. Application domains define a subset of MHEG-5 features that must be supported. In order to test conformance to a specific application domain, a corresponding subset of the test cases must be defined. This subset of the test suite is then used to test the conformance of the engine. This part of ISO/IEC 13522 tests conformance of the behaviour of an MHEG engine. It does not validate the physical presentation of MHEG-5 objects. The test suite comprises a set of test cases and a corresponding set of test objects. The test cases are defined in terms of: . test purpose; . objects and procedures which are to be used to test one or more MHEG-5 features; . expected result. A set of content data will be provided for the test objects. These content data are intended as a guide for generating a test suite and should be converted or replaced by content formats appropriate to the Application Domain. A test suite for an Application Domain shall be generated by using the PICS template in subclause 9.2.1 PICS Template.