SIST ETS 300 715 E1:2003

• Abstract:

  Specify a representation allowing the description of access & process- ing of Mulitmedia & Hypermedia Information used in AVI applications in a platform-independent way.

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.160.60 - Multimedia systems and teleconferencing equipment
• ICS: 35.180 - IT Terminal and other peripheral equipment
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI ETS 300 715 ed.1 (1997-06) - Terminal Equipment (TE); MHEG script interchange representation (MHEG-SIR)

SIST ETS 300 715 E1:2003 is the Slovenian standard identical to ETS 300 715 Edition 1 from ETSI. It specifies MHEG-SIR, a platform-independent script interchange representation for describing and processing multimedia and hypermedia information in AVI applications. It is written for MHEG applications, MHEG engines, and implementers that need scripts to be encoded, interpreted, and exchanged in a consistent way.

What does SIST ETS 300 715 E1:2003 specify?

SIST ETS 300 715 E1:2003 specifies the coded representation of the MHEG script object class and the semantics that MHEG engines shall follow when interpreting interchanged scripts. In practice, it tells you how to package script data, how an engine should execute it, and how scripts can call external services or manipulate MHEG objects.

The scope is limited to the script object class within ISO/IEC 13522 and extends the base MHEG provisions so that scripts can carry data-processing logic and run-time access in a standard form. It applies to applications that interchange multimedia and hypermedia information.

The document is organised as follows:

• Clauses 1 to 5 cover scope, references, definitions, general background, and conformance.
• Clauses 6 to 9 explain the MHEG-SIR model, the MHEG/MHEG-3 relationship, and the virtual machine.
• Clauses 10 and 11 define access to the run-time environment and to MHEG objects.
• Clause 12 defines script declarations.
• Clause 13 defines the instruction set and its execution rules.
• Clause 14 maps IDL into MHEG-SIR.
• Clause 15 defines the MHEG-3 API.

Annex	What it covers
A	Formal syntax of interchanged scripts in ASN.1
B	Encoding of interchanged scripts and program code
C	Predefined types, functions, and messages, including their encoding
D	Platform mapping specification form for run-time environment access
E	Framework for defining an MHEG API in IDL and mapping it to MHEG-SIR
F	Normative IDL specification of the MHEG-3 API
G	Relationship with ISO/IEC 13522-1 and ISO/IEC 13522-5
H	Informative EBNF syntax for MHEG-SIR scripts
J	Informative textual notation for MHEG-SIR scripts
K	MHEG entities such as MHEG objects, mh-objects, and rt-objects
L	Main features of MHEG-SIR

What are the key requirements of SIST ETS 300 715 E1:2003?

SIST ETS 300 715 E1:2003 sets requirements on script conformance, script structure, execution behaviour, external service access, and the MHEG-3 API. These requirements matter because they determine whether a script object can be exchanged, decoded, and interpreted predictably by different engines.

Conformance and application scope

Clause 5 separates conformance into information objects, implementations, and applications. A conforming MHEG-3 script object must itself conform to ISO/IEC 13522 representation rules and must encapsulate a conforming MHEG-3 interchanged script. For users, that means the script content and the object that carries it are both part of interoperability.

Clause 5 also ties testing to ISO/IEC 9646. If you need to verify an engine or an object for conformance, the standard expects conformance measurements to use that testing framework.

Script structure and execution model

Clause 12 defines an interchanged script as a sequence of:

• type declarations
• constant declarations
• global variable declarations
• package declarations
• handler declarations
• routine declarations

This structure matters because it tells implementers what to parse before execution begins and what is only used later at run time. Routines contain the program code, while declarations describe the data and interfaces that code can use.

Clause 9 defines the MHEG-SIR virtual machine, including memory areas, stacks, queues, script statuses, and processing units. The model is deliberately abstract: an engine may implement it in any way, but it shall behave as if it followed the same interpretation rules. The practical result is predictable execution across implementations.

Instructions and data handling

Clause 13 defines the instruction set and groups instructions into control flow, variable, stack, arithmetic, logical, comparison, memory, and conversion operations. The instruction set includes calls, jumps, pushes and pops, allocation and freeing, and access to constructed data. For a reader, this means MHEG-SIR can express both computation and structured script logic, not just simple message passing.

Clause 13.4 defines type conversion rules for the parameter stack. Some conversions are reversible or lossless, while others are truncating. This matters when routines pass values between external services, variables, and stack operations, because type compatibility is not left to guesswork.

External services and MHEG object access

Clause 10 explains how scripts call external services through package declarations. A package declaration describes services and exceptions by name, signature, and identifiers, and the run-time platform must provide a platform mapping specification for those services when one exists. In practice, this is the bridge between portable script logic and platform-specific software or services.

Clause 10 also requires the package mapping to define availability, loading, unloading, invocation, data encoding, parameter passing, return value retrieval, and exception retrieval. That means a script can be written against abstract service descriptions, while the platform mapping tells the engine how to reach the actual implementation.

Clause 11 defines access to the MHEG API. MHEG actions are invoked through the same general mechanism as external services, but the MHEG API is treated as predefined. The standard also defines how scripts receive MHEG messages, including those related to API run operations and API exceptions.

IDL mapping and the MHEG-3 API

Clause 14 maps IDL specifications into MHEG-SIR package, type, service, and exception declarations. It also maps IDL operations, attributes, inherited operations, exceptions, types, and constants. For implementers, this is the rule set that makes external interfaces language-independent inside an MHEG-SIR script.

Clause 15 defines the MHEG-3 API as the unique IDL module MHEG_3. It includes the objects ScriptInterpreter, MhScript, RtScript, and RoutineInvocation, together with predefined types and exceptions. The predefined MHEG-3 API functions are synchronous, so script authors and engine implementers can rely on call-and-response behaviour.

What terms does SIST ETS 300 715 E1:2003 define?

SIST ETS 300 715 E1:2003 defines a set of terms that anchor the execution model and the interface model.

• MHEG-SIR - The script interchange representation defined by the standard for MHEG script objects.
• interchanged script - The coded representation of the script data attribute of an MHEG script object.
• mh-script - The internal representation, within an MHEG engine, of an available MHEG script object.
• rt-script - The run-time representation created from an mh-script and executed by the engine.
• MHEG-3 engine - An MHEG engine that processes and interprets MHEG-SIR interchanged scripts.
• MHEG API - The API that an MHEG engine provides to applications for manipulating MHEG objects.
• IDL - Interface Definition Language, used here to specify types, operations, attributes, and exceptions in a platform-independent way.
• RoutineInvocation - The MHEG-3 API object that represents the invocation context of a routine and carries its parameters and execution state.

Who uses SIST ETS 300 715 E1:2003?

SIST ETS 300 715 E1:2003 is used by people who build, integrate, test, or buy systems that exchange MHEG scripts. That includes MHEG engine developers, terminal equipment vendors, multimedia system integrators, and teams that need predictable script interoperability.

Typical users and tasks include:

• engine implementers defining how scripts are parsed, prepared, and executed
• application developers packaging multimedia or hypermedia logic as interchanged scripts
• platform providers defining the platform mapping specification for external services
• quality and conformance teams checking script objects and engine behaviour
• system integrators linking MHEG scripts to external data, functions, or device services
• buyers and technical evaluators checking whether a product supports MHEG-SIR and the MHEG-3 API

What changed in SIST ETS 300 715 E1:2003 from the previous edition?

SIST ETS 300 715 E1:2003 is identical to ETS 300 715 Edition 1.

Which standards are used with SIST ETS 300 715 E1:2003?

SIST ETS 300 715 E1:2003 relies on several cited standards and companion parts:

• ISO/IEC 8824-1 - provides ASN.1 basic notation used for formal syntax
• ISO/IEC 8825-1 - provides BER, CER, and DER encoding rules; this ETS uses DER for interchanged scripts
• ISO/IEC 9646 Parts 1 to 5 - provides the conformance testing methodology and framework
• ISO/IEC 10646-1 - provides the UCS character repertoire used for text-related types
• ISO/IEC 13522-1 - provides the base notation for MHEG object representation and the script class framework
• ISO/IEC 13522-4 - provides the registration procedure for MHEG format identifiers
• ISO/IEC 13522-5 - provides support for base-level applications and the related InterchangedProgram context
• ISO/IEC 14750-1 - provides the CORBA IDL notation used for interface mapping
• IEEE 754-1985 - defines binary floating-point arithmetic used in numeric semantics

What does the SIST ETS 300 715 E1:2003 document contain?

The document contains a formal model of how MHEG-SIR scripts are built and executed, plus the syntax and encoding rules needed for interchange. Clause 13 includes a structured instruction catalogue with semantics for control flow, arithmetic, stack operations, memory management, and data access.

It also contains mapping rules for IDL, including how operations, attributes, types, constants, and exceptions are turned into MHEG-SIR declarations. Annex F gives the full MHEG-3 API in IDL form, while Annex H and Annex J provide syntax notations that help developers and testers read or generate scripts.

Annex B gives the octet-level coding of script programs, and Annex C identifies the predefined elements used by engines. Annex K describes the MHEG entities that an engine handles, and Annex L summarises the main functional and technical features of MHEG-SIR, including hardware independence, compact representation, and secure script processing.

SLOVENSKI STANDARD
01-december-2003
Terminalska oprema (TE) – Prikaz izmenjave skriptov po MHEG (MHEG-SIR)
Terminal Equipment (TE); MHEG script interchange representation (MHEG-SIR)
Ta slovenski standard je istoveten z: ETS 300 715 Edition 1
ICS:
33.160.60 9HþSUHGVWDYQLPXOWLPHGLMVNL Multimedia systems and
VLVWHPLLQRSUHPD]D teleconferencing equipment
WHOHNRQIHUHQFH
35.180 Terminalska in druga IT Terminal and other
periferna oprema IT peripheral equipment
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 715
TELECOMMUNICATION June 1997
STANDARD
Source: ETSI TC-TE Reference: DE/MTA-001047
(formerly DE/TE-01047)
ICS: 33.020
Key words: AVI, MHEG, MHI, multimedia
Terminal Equipment (TE);
MHEG script interchange representation (MHEG-SIR)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail]
Tel.: [phone] - Fax: [phone]
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1997. All rights reserved.

Page 2
ETS 300 715: June 1997
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

Page 3
ETS 300 715: June 1997
Contents
Foreword .11
Introduction.11
1 Scope .13
2 Normative references.13
3 Definitions.14
3.1 Definitions .14
3.2 Abbreviations .17
4 General.18
5 Conformance.18
5.1 Information object conformance .18
5.1.1 Profiles .18
5.1.2 Encoding .19
5.1.3 Syntax.19
5.1.4 Semantics.19
5.2 Implementation conformance .19
5.2.1 Conformance requirements.19
5.2.2 Conformance documentation.20
5.3 Application conformance .20
5.4 Test Methods .20
6 Overview .20
6.1 Description methodology .20
6.2 Data processing operations .21
6.3 Access to external data and functions.21
7 MHEG/MHEG-3 relationship .22
7.1 MHEG entities.22
7.2 Functional entities.22
7.3 MHEG-SIR script interpreter.23
8 Elements of MHEG-SIR .23
8.1 Data types.23
8.1.1 Predefined types.24
8.1.1.1 Primitive types .25
8.1.1.1.1 void type.25
8.1.1.1.2 octet type .25
8.1.1.1.3 short type .25
8.1.1.1.4 long type .25
8.1.1.1.5 unsigned short type.25
8.1.1.1.6 unsigned long type.25
8.1.1.1.7 float type .26
8.1.1.1.8 double type .26
8.1.1.1.9 boolean type .26
8.1.1.1.10 character type .26
8.1.1.1.11 data identifier type.26
8.1.1.1.12 object reference type .26
8.1.1.2 Predefined constructed types .26
8.1.2 Declared constructed types.26
8.1.2.1 sequence types.27
8.1.2.2 string types .27

Page 4
ETS 300 715: June 1997
8.1.2.3 array types. 28
8.1.2.4 structure types. 28
8.1.2.5 union types. 28
8.2 Data. 29
8.2.1 Immediate values. 29
8.2.2 Constants. 29
8.2.3 Variables. 30
8.2.3.1 Global variables . 30
8.2.3.2 Local variables . 30
8.2.3.2 Dynamic variables. 30
8.3 Functions. 31
8.3.1 Routines. 31
8.3.2 Services . 32
8.3.3 Predefined functions. 32
8.4 Messages. 32
8.4.1 Package exceptions. 32
8.4.2 Predefined messages. 33
8.5 Instructions. 33
8.6 Identifiers. 33
8.6.1 Type identifiers . 33
8.6.2 Data identifiers. 34
8.6.3 Function identifiers. 34
8.6.4 Message identifiers. 34
9 The MHEG-SIR virtual machine . 34
9.1 Structure of the MHEG-SIR virtual machine . 34
9.2 Structures and notations . 35
9.2.1 Table. 35
9.2.2 Stack. 35
9.2.3 Parameter stack . 35
9.2.4 Queue . 36
9.2.5 Data representation . 36
9.3 Memory areas . 37
9.3.1 Mh-script memory areas. 37
9.3.1.1 Data areas. 37
9.3.1.1.1 Type definition table . 37
9.3.1.1.2 Constant table . 37
9.3.1.1.3 Global variable definition table . 37
9.3.1.2 Code areas. 37
9.3.1.2.1 Routine definition table. 38
9.3.1.2.2 Package definition table . 38
9.3.1.2.3 Service definition table . 38
9.3.1.2.4 Exception definition table . 39
9.3.1.2.5 Handler definition table. 39
9.3.1.2.6 Program code area . 39
9.3.2 Rt-script memory areas . 39
9.3.2.1 Dynamic memory areas . 39
9.3.2.1.1 Variable table . 40
9.3.2.1.2 Call stack. 40
9.3.2.1.3 Parameter stack. 40
9.3.2.1.4 Message queue. 41
9.3.2.1.5 Heap. 41
9.3.2.2 Registers. 41
9.3.2.2.1 Instruction pointer register. 42
9.3.2.2.2 Instruction register. 42
9.3.2.2.3 Error register . 42
9.3.2.2.4 Stack pointer register . 42
9.3.2.2.5 Frame pointer register. 42
9.3.2.2.6 Queue pointer register . 42
9.3.2.2.7 Function register . 42
9.4 Script statuses. 42
9.4.1 Mh-script statuses. 42
9.4.1.1 Not available . 42

Page 5
ETS 300 715: June 1997
9.4.1.2 Available .43
9.4.2 Rt-script statuses.43
9.4.2.1 Not ready .43
9.4.2.2 Ready .43
9.4.2.3 Running .43
9.4.2.4 Erroneous .44
9.5 Processing units.44
9.5.1 Message reception.44
9.5.1.1 MHEG-3 API operations .44
9.5.1.2 External exception .44
9.5.1.3 InstructionExecutionError exception.45
9.5.1.4 MHEG-3 API exception.45
9.5.2 Mh-script initialization .45
9.5.3 Rt-script initialization.45
9.5.4 Rt-script execution unit.45
9.5.5 MHEG-SIR instruction execution unit.46
10 Provisions for run-time environment access .46
10.1 General model .46
10.2 Declaration of IDL interfaces .46
10.3 Invocation of external operations in an MHEG-SIR program.47
10.4 Handling of external exceptions in an MHEG-SIR program .47
10.5 Invocation of external operations by an MHEG-3 engine .48
10.6 Handling of external exceptions by an MHEG-3 engine .48
10.7 Platform mapping specifications.48
11 Provisions for MHEG object manipulation.48
11.1 Invoking MHEG actions .48
11.1.1 Sending messages to other scripts .49
11.1.2 Exchange of information with MHEG objects.49
11.2 Receiving MHEG messages.49
11.2.1 MHEG-3 API run operations.49
11.2.2 MHEG API exceptions.49
12 MHEG-SIR declarations.50
12.1 Type declaration .50
12.1.1 Type identifier.50
12.1.2 Type description .51
12.1.2.1 String description.51
12.1.2.2 Sequence description .51
12.1.2.3 Array description.51
12.1.2.4 Structure description.51
12.1.2.5 Union description.51
12.2 Constant declaration.52
12.2.1 Data identifier .52
12.2.2 Type identifier.52
12.2.3 Constant value .52
12.3 Global variable declaration .53
12.3.1 Data identifier .53
12.3.2 Type identifier.53
12.3.3 Constant reference.53
12.4 Package declaration .53
12.4.1 Package identifier.54
12.4.2 Name.54
12.4.3 Service description .54
12.4.3.1 Function identifier .54
12.4.3.2 Name .54
12.4.3.3 Calling mode.54
12.4.3.4 Type identifier .55
12.4.3.5 Parameter description .55
12.4.3.5.1 Passing mode .55
12.4.3.5.2 Type identifier .55
12.4.4 Exception description .55

Page 6
ETS 300 715: June 1997
12.4.4.1 Message identifier. 55
12.4.4.2 Name . 56
12.4.4.3 Parameter description. 56
12.5 Handler declaration . 56
12.5.1 Message identifier. 56
12.5.2 Function identifier . 56
12.6 Routine declaration . 56
12.6.1 Function identifier . 57
12.6.2 Type identifier . 57
12.6.3 Parameter description. 57
12.6.3.1 Passing mode . 57
12.6.3.2 Type identifier. 57
12.6.4 Local variable declaration . 57
12.6.4.1 Data identifier. 57
12.6.4.2 Type identifier. 58
12.6.4.3 Constant reference . 58
12.6.5 Program code . 58
13 MHEG-SIR instructions. 58
13.1 Presentation methodology. 58
13.1.1 Error conditions. 59
13.1.2 Formal specification. 59
13.1.3 Data table notation. 59
13.1.4 Template instruction notation. 60
13.1.5 Primitives . 60
13.2 Classification of MHEG-SIR instructions. 60
13.3 Description of instructions .61
13.3.1 No operation . 61
13.3.2 Yield. 62
13.3.3 Return . 62
13.3.4 Free . 63
13.3.5 Not . 63
13.3.6 Or. 63
13.3.7 Exclusive or . 64
13.3.8 And . 64
13.3.9 Equal reference . 65
13.3.10 Equal. 65
13.3.11 Less than . 66
13.3.12 Greater than. 66
13.3.13 Add . 66
13.3.14 Subtract . 67
13.3.15 Multiply. 67
13.3.16 Divide. 67
13.3.17 Negate . 68
13.3.18 Remainder . 68
13.3.19 Duplicate. 69
13.3.20 Convert . 69
13.3.21 Jump on true. 69
13.3.22 Jump on false . 70
13.3.23 Jump. 70
13.3.24 Shift. 70
13.3.25 Get object reference . 71
13.3.26 Long jump on true. 71
13.3.27 Long jump on false . 72
13.3.28 Long jump. 72
13.3.29 Call. 72
13.3.30 External call . 73
13.3.31 Push. 74
13.3.32 Push reference . 75
13.3.33 Push immediate. 75
13.3.34 Pop . 76
13.3.35 Pop reference . 76
13.3.36 Pop contents. 76

Page 7
ETS 300 715: June 1997
13.3.37 Allocate.77
13.3.38 Increment .77
13.3.39 Decrement.78
13.3.40 Get.78
13.3.41 Get contents.79
13.3.42 Set .79
13.3.43 Set contents .80
13.4 Type conversion rules.81
13.4.1 Reversible conversions .81
13.4.2 Lossless extensions .81
13.4.2.1 Conversions from boolean.81
13.4.2.2 Conversions from octet to a numeric type.82
13.4.2.3 Lossless conversions from a numeric to a larger numeric
type .82
13.4.3 Lossy extensions.82
13.4.4 Truncations to boolean.82
13.4.5 Truncations between integer or between floating-point types .82
13.4.6 Truncations from floating-point to integer.82
14 IDL mapping to MHEG-SIR.82
14.1 IDL specifications.82
14.2 IDL interfaces and modules.83
14.3 IDL operations.83
14.3.1 Operation name.83
14.3.2 Operation parameters .83
14.3.3 Implicit parameter.83
14.3.4 Return value .83
14.4 IDL attributes.83
14.4.1 Accessor.84
14.4.2 Modifier.84
14.4.3 Readonly attribute .84
14.5 IDL inherited operations.84
14.6 IDL exceptions .84
14.6.1 Exception name.84
14.6.2 Exception members .84
14.6.3 Implicit member.84
14.7 IDL types.84
14.7.1 char type.85
14.7.2 enum type.85
14.7.3 Constructed types .85
14.7.4 any type .85
14.7.5 Restrictions on types .86
14.8 IDL constants.86
15 The MHEG-3 API .86
15.1 ScriptInterpreter object .86
15.1.1 kill operation .86
15.1.2 prepare operation .87
15.2 MhScript object .87
15.2.1 destroy operation.87
15.2.2 new operation.88
15.3 RtScript object.88
15.3.1 delete operation.88
15.3.2 setPriority operation.88
15.3.3 getPriority operation .89
15.3.4 setData operation .89
15.3.5 getData operation.90
15.3.6 allocate operation .90
15.3.7 free operation .91
15.3.8 stop operation.91
15.3.9 reInit operation .91
15.3.10 getRtScriptStatus operation .92
15.3.11 open operation .92

Page 8
ETS 300 715: June 1997
15.4 RoutineInvocation object. 92
15.4.1 close operation . 93
15.4.2 routine_id readonly attribute . 93
15.4.3 setParameter operation . 93
15.4.4 getPrototype operation. 94
15.4.5 run operation. 94
15.4.6 reset operation. 95
15.4.7 getInvocationStatus operation . 95
Annex A (normative): ASN.1 specification of interchanged scripts . 96
Annex B (normative): Coded representation of interchanged scripts. 99
B.1 Coding for interchanged scripts. 99
B.2 Coding for the program code. 99
B.2.1 Instruction op-codes. 99
B.2.2 Instruction operands. 99
B.2.2.1 Data identifier operands. 99
B.2.2.2 Function identifier operands . 99
B.2.2.3 Miscellaneous numeric operands . 99
Annex C (normative): MHEG-SIR predefined elements . 104
C.1 Predefined types. 104
C.1.1 Primitive types . 104
C.1.2 MHEG API types . 104
C.2 Predefined functions. 105
C.2.1 MHEG API operations. 105
C.2.2 MHEG-3 API operations. 105
C.3 Predefined messages. 105
C.3.1 MHEG-3 API operations. 106
C.3.2 The InstructionExecutionError exception . 106
C.3.3 MHEG-3 API exceptions . 106
C.3.4 MHEG API exceptions. 106
Annex D (normative): IDL Platform mapping specification form. 108
Annex E (normative): MHEG API definition process . 110
E.1 Generic API definition framework. 110
E.1.1 MHEG elements input to MHEG API definition process . 110
E.1.2 IDL elements output by MHEG API definition process. 110
E.1.3 Requirements on the MHEG API definition process . 110
E.1.3.1 Portability . 110
E.1.3.2 Genericity. 111
E.1.3.3 Conformance testability . 111
E.1.3.4 Implementability. 111
E.1.3.5 Fulfilment of technical requirements. 111
E.1.4 General structure of the MHEG API. 111
E.1.5 IDL non-object datatype definition. 112
E.1.5.1 Name mapping . 112
E.1.5.1.1 Data types . 112
E.1.5.1.2 Components. 112
E.1.5.1.3 Values . 112
E.1.5.2 Type mapping . 113
E.1.5.2.1 INTEGER . 113
E.1.5.2.2 BOOLEAN. 113
E.1.5.2.3 OCTET STRING . 113
E.1.5.2.4 ENUMERATED. 113
E.1.5.2.5 SEQUENCE OF. 113

Page 9
ETS 300 715: June 1997
E.1.5.2.6 CHOICE.114
E.1.5.2.7 SEQUENCE.114
E.1.5.3 Order of declarations.114
E.1.6 IDL interface definition .116
E.1.7 IDL attribute definition.116
E.1.7.1 MHEG interchanged attributes.116
E.1.7.2 MHEG internal attributes .117
E.1.8 IDL operation definition.117
E.1.8.1 Operations mapping MHEG elementary actions.117
E.1.8.2 Operations enabling the deletion of an interface instance .119
E.1.8.3 Operations to attach and detach an interface instance to a MHEG entity.119
E.1.9 IDL exception definition.119
E.2 MHEG API mapping to MHEG-SIR.120
Annex F (normative): IDL specification of the MHEG-3 API .121
Annex G (normative): Relationships with other parts of ISO/IEC 13522 .123
G.1 Relationships with ISO/IEC 13522-1 .123
G.2 Relationships with ISO/IEC 13522-5 .123
Annex H (informative): MHEG-SIR syntax (EBNF notation) .125
Annex J (informative): Textual notation for MHEG-SIR scripts .127
Annex K (informative): MHEG entities .130
K.1 MHEG objects .130
K.2 Mh-objects.130
K.3 Rt-objects .130
K.4 Interchanged MHEG objects .
...