1、ITU-T RECMN*T*l07 75 4862573 Obob904 ObT INTERNATIONAL TELECOMMU N CATION UN ION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU TERMINALS FOR TELEMATIC SERVICES T.107 (08/95) ENHANCED MAN MACHINE INTERFACE FOR VIDEOTEX AND OTHER RETRIEVAL SERVICES (VEMMI) ITU-T Recommendation T.107 (Previousl
2、y “CCITT Recommendation”) ITU-T RECMN*T-307 95 = 4862573 0606405 TTb FOREWORD The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union TU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recomm
3、en- dations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these top
4、ics. The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). ITLJ-T Recommendation T.107 was prepared by ITLJ-T Study Group 8 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the
5、 1 lth of August 1995. NOTE In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. O ITU 1996 All rights reserved. No part of this publication may be reproduced or utilized in any form or
6、by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. ITU-T RECMN*T-L07 95 4862591 0606406 932 CONTENTS Page 1 Scope 2 References 3 Definitions and abbreviations . 3.1 Definitions 3.2 Abbreviations 4 General model 4.1 Introduction 4
7、.2 Definition of the VEMMI elements 4.2.1 VEMMI object definition and identification . 4.2.2 VEMMI component definition 4.2.3 VEMMI component item definition 4.2.4 Resource definition . 4.2.5 4.2.6 Resource transfer VEMMI plane structure model . 4.3.1 4.3.2 The VEMMI objects plane Operation modes fo
8、r VEMMI terminals . 4.4.1 The standard mode 4.4.2 The VEMMI mode 4.4.3 VEMMI elements data content . . 4.5.1 Text data definition . 4.5.3 Colour . 4.5.4 Videotex data 4.5.5 Sound 4.5.6 Graphical data . 4.5.7 Video da ta . VEMMI objects positioning and dimensioning 4.6.2 Dimensioning VEMMI elements s
9、tates and state parameters 4.7.1 Object 4.7.2 Component Transfer of VEMMI objects The standard plane for videotex data 4.3 4.4 Switching between standard mode and VEMMI mode 4.5.2 Bitmaps . 4.5 4.6 4.6.1 Positioning 4.7 4.8 Local action management . 4.9 Memory considerations 4.10 Common rules for ob
10、ject handling . 4.10.1 Active state and focus management 4.10.2 Behaviour of the modal mode . 4.10.3 Size considerations and clipping . 4.1 1 Local object storage 4.12 Symbolic directory names 4.13 Specific rules for dedicated terminals . 5 Service description . 5.1 5.2 Service elements initiated by
11、 the VEMMI application and the terminal Service elements initiated by the VEMMI application . 5.2.1 VEMMI-Open . i 5.2.3 VEMMI-Resume 5.2.2 VEMMI-Close . 1 1 2 2 3 4 4 4 5 5 6 6 6 6 7 7 7 7 7 7 9 9 9 10 11 11 11 11 11 11 11 12 13 13 16 17 18 18 18 19 19 19 20 20 21 23 23 23 24 24 Recommendation T.10
12、7 (08/95) 1 ITU-T RECMN*T.307 95 m 4862593 0606407 877 m 5.2.4 VEMMI-Suspend . 5.2.5 VEMMI-IdentifyTerrn-Cap . 5.2.6 VEMMI-Set-Options . 5.2.7 VEMMI-Create-Object 5.2.8 VEMMI-Open-Object . . 5.2.9 VEMMI-Open-Blocking-Object . 5.2.10 VEMMI-Close-Object 5.2.1 1 VEMMI-CloseAll . . 5.2.12 VEMMI-Destroy-
13、Object . 5.2.13 VEMMI-Obj-Access-Disable . 5.2.14 VEMMI-Obj-Access-Enable 5.2.15 VEMMI-ModifyComponent 5.2.17 VEMMI-Load-Col-Table 5.2.18 VEMMI-Reset-ColTable . 5.2.20 VEMMI-Delete-Outdated-Objects 5.2.22 VEMMI-Erase-Objects 5.2.23 VEMMI-User-Lock . 5.2.24 VEMMI-User-Unlock . 5.2.25 VEMMI-Resource-T
14、ransfer Service elements initiated by the terminal 5.3.1 VEMMI-Identify-Term-Cap-Resp . 5.3.2 VEMMI-Object-Retransmission 5.3.3 VEMMI-User-Data 5.3.4 VEMMI-Open-Application-Resp . 5.3.5 VEMMI-Store-Objects-Resp 5.3.6 VEMMI-Error 5.3.7 VEMMI-ResourceTransfer-Abo rt . 6 VEMMI objects introduction . 6.
15、1 The application bar . 6.1.1 Composition 5.2.16 VEMMI-ObjLocation-Change 5.2.19 VEMMI-Open-Application . 5.2.21 VEMMI-Store-Objects 5.3 6.2 The button bar . 6.2.1 Composition 6.3.1 Composition 6.4 The dialogue box 6.5 Operative object 6.3 The pop-up menu 6.4.1 Composition 6.6 Bitmap resource object
16、 . 6.7 Videotex resource object 6.8 Text resource object 6.9 Font resource object 6.10 Metacode object 6.1 1 The message box . 7 Functional description General rules for the behaviour of elements . 7.1.1 User interaction . 7.1.2 Local actions and reports 7.1.3 Relationship between objects and compon
17、ents . 7.1.4 Opedclose of audio, video, resource and metacode objects . 7.1.5 Maximize operation 7.1.6 Notational Conventions . 7.1.7 Mnemonic . 7.1 Page 24 25 25 26 26 26 27 27 27 27 28 28 29 29 30 31 31 32 32 32 32 33 34 34 34 35 36 36 36 37 37 38 38 38 38 38 38 39 39 40 41 41 41 41 41 41 41 41 41
18、 41 42 43 43 44 44 11 Recommendation T.107 (08/95) 8 9 10 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 7.10 7.11 7.12 7.13 7.14 7.15 ITU-T RECMNtT-LO7 95 W 4862C93 0606408 705 M Text formats 7.2.1 VEMMI high quality text 7.2.2 Text labels and titles . The Application Bar . The Button Bar . The Pop-up Menu . 7.5.
19、1 Composition 7.6.1 Composition The Message Box . Operative object Videotex resource object Text resource object Font resource object Metacode object VEMMI bitmap data type definition . The VEMMI content encoding identification catalogue . 7.3.1 Composition . . . 7.4.1 Composition The Dialogue Box .
20、 . Bitmap resource object . Complete coded representation of the VEMMI . 8.1 Introduction 8.2 Notation used 8.3 Overall switching of coding environment 8.3.1 Switching into the VEMMI mode . 8.3.2 ISOAEC 9281 14 syntax stnicture 8.4 VEMMI Command Syntax . 8.5 Objects, components 8.6 Local actions . E
21、ncoding 9.1 Command structure . 9.2 Object. component and attribute structure 9.3 Terminal symbols encoding 9.3.1 Opcodes 9.3.2 Integers 9.3.3 Enumerated . 9.3.4 Strings 9.3.5 NDC 9.4 Attributes and lower level symbols 9.5 Opcodes 9.6 Syntax of the VEMMI-ModiQComponent 9.7 Defaults . Introduction of
22、 the VEMMI service into existing Videotex Recommendations 10.1 Introduction of the VEMMI to T.lO1 4 . 10.2 Introduction of the VEMMI to T.105 6 . Annex A . TSlString A.l Scope A.2 Graphic character sets . A.3 Code extension technique . A.4 Repertoire of the Latin based character set . AS Control fun
23、ctions Annex B . Mandatory subset of IS0 8859 13 . Annex C . Minimum datatype kernel Page 44 44 45 46 48 53 54 55 57 58 61 83 85 87 88 88 89 89 89 89 91 91 91 91 91 93 95 98 102 103 103 103 104 104 104 105 105 106 107 108 111 113 116 116 116 116 116 116 119 119 119 120 121 . Recommendation T.107 (08
24、/95) 111 SUMMARY This Recommendation specifies the syntax to be used by videotex or other retrieval services for implementation of an enhanced man machine interface (VEMMI). The VEMMI is a means to improve the ergonomics and interactivity of retrieval systems using graphical dialogue elements such a
25、s application bar, button bar, pop-up menus, dialogue box. The standard plane continues to receive the standard data of the underlying platform. Standard Videotex Applications can therefore run also on a VEMMI terminal. The VEMMI objects plane receives VEMMI objects. An automatic switching mechanism
26、 between standard mode and VEMMI mode is provided. This Recommendation defines datatypes (VEMMI-high quality text, VEMMI bitmaps) and allows the integration of other widely used datatypes (e.g. PEG, BMP, WAVE, MIDI, Videotex) in the VEMMI dialogue. Also operative objects are defined to extent the ca
27、pabilities of a VEMMI application during runtime. VEMMI objects can be distributed between a host and a VEMMI terminal to improve the performance of interactive applications. The VEMMI application can control (save, load, update) VEMMI objects on the terminal. This Recommendation contains the servic
28、e description, the service elements and their coding. iv Recommendation T.107 (08/95) - ITU-T RECMN*T.L07 95 = 4Bb259L ObObYLO 363 Recommendation T.107 ENHANCED MAN MACHINE INTERFACE FOR VIDEOTEX AND OTHER RETRIEVAL SERVICES (VEMMI) (Geneva, 1995) 1 Scope This Recommendation specifies the data synta
29、x to be used by Videotex and Multimediaypermedia Information retrieval services for implementation of the Videotex Enhanced Man Machine Interface (VEMMI). In the Videotex case, this Recommendation is applicable to both the Videotex service and the attached Videotex terminals. Those terminals may be
30、connected to the Videotex service via the hblic Switched Telephone Network (PSTN), Integrated Services Digital Network (ISDN) or Packet Switched Public Data Network (PSPDN). Typically, the terminals should support ISDN Syntax-Based Videotex (SBV). This Recommendation can also be used for any kind of
31、 retrieval service (not related to Videotex) by using the relevant underlying platform and content data types. 2 References The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of public
32、ation, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of
33、 the currently valid IT-T Recommendations is regularly published. CCITT Recommendation T.50 (1992), International Reference Alphabet (IRA) (Formerly International Alphabet No. 5 or IA5) - Information technology - 7-bit coded character set for information interchange. CCITT Recommendation T.51 (1992)
34、, Lutin based coded character sets for telematic services. ITU-T Recommendation T.52 (1993), Non-Latin coded character sets for telematic services. IT-T Recommendation T. 101 (1994), International interworking for videotex services. ITU-T Recommendation T. 102 (1993), Syntax-based videotex end-to-en
35、d protocols for circuit mode ISDN. IT-T Recommendation T. 105 (1994), Syntax-based videotex application layer protocol. IT-T Recommendation H.261(1993), Video codec for audiovisual services atp x 64 kbids. ITU-T Recommendation H.320 (1993), Narrow-band visual telephone systems and terminal equipment
36、. ITU-T Recommendation F.300 (1993), Videotex service. IS0 2022: 1986, Information Processing - IS0 7-bit and ?-bit coded character sets - Code extension techniques. IS0 2375: 1985, Data processing - Procedure for registration of escape sequences. IS0 8632:1992, Information technology - Computer gra
37、phics - Metafile for storage and transfer of picture description information. IS0 8859: 1987, Information Processing - data contents as defined in this Recommendation; data contents as referred to in this Recommendation. A VEMMI terminal may also handle a Videotex application using encoded data and
38、protocols as described in the Videotex Recommendations referred to in clause 2. 4.2 The logical units which form the structure of the VEMMI shall be named and defined as follows: Definition of the VEMMI elements - VEMMI objects or objects; - VEMMI components or components; - VEM component item or it
39、ems. VEMMI element is a generic name used in this Recommendation to designate an object, a component or an item. 4 Recommendation T.107 (08/95) ITU-T RECMNaT-107 95 D 4862571 0606414 TO9 M An example is given Figure 1. I I I I i- I I VEMMI component item VEMMI component TO81 5370-94/dOl VEMMI object
40、 FIGURE liT.107 Example showing objectdcomponentshtems 4.2.1 The following four different types of VEMMI objects are defined in this Recommendation: VEMMI object definition and identification - display objects; - operative objects; - resource objects; - metacode objects. If not stated otherwise, the
41、 term object used alone always refers to a display object. VEMMI objects are the logical units which are used by a VEMMI application to interact with the user. VEMMI objects are composed of different components. The objects are only defined regarding their functionality, their size and position rela
42、tive to the Defined Display Area (DDA). The representation of the objects is terminal dependent. Every object shall be identified by an Object Identification Number (OIN) which shall be unique within a VEMMI application at any one time. 4.2.2 VEMMI component definition VEMMI components always belong
43、 to a VEMMI object and are only valid within this object. The object, to which a component belongs, is named parent object. In order to transport information, components may cany a data content (see 4.5). The components are only defined regarding their functionality, their type of content and their
44、size and position relative to the object. The representation of the components is terminal dependent. The representation of data content is specified either by this Recommendation (for the datatypes that are defined within this Recommendation) or by the corresponding presentation standard (for datat
45、ypes that are defined outside this Recommendation). Every component shall be identified by a Component Identification Number (CIN) which shall be unique within an object. Recommendation T.107 (OW95) 5 ITU-T RECNN*T.LO 75 m 4862573 Ob06435 945 4.2.3 VEMMI component item definition The subunit of a VE
46、MMI component is a component item. Every item is an integral part of a component. The definition of a component item is only valid within this component. 4.2.4 Resource definition Resources are elements which can be referenced by components or objects. One resource can be referenced by more than one
47、 element. The following resources are defined: - - - the colour table which is unique in one application; files stored in the terminal (identified by filenames) can contain sound data, operative objects etc.; a combination of a font and a set of attributes is a resource object. It is identified via
48、a Font Identification Number (FIN); a bitmap is a resource object. It is identified via a Bitmap Identification Number (BIN); text can be a resource object. It is identified via a Text Identification Number (TIN); Videotex can be a resource object. It is identified via a Videotex Identification Numb
49、er (VIN); - - - - NOTE - FIN, BIN, VIN are Object Identification Numbers (OINS). The terms FIN, BIN and VIN are only used to clearly objects sets stored in the terminal between two sessions (they are identified via attributes). indicate that the corresponding object is a resource object. 4.2.5 Transfer of VEMMI objects VEMMI objects can be transmitted to the VEM terminal using a telecommunication network. If they are stored then in the terminal, they become local objects. VEMMI objects can also be downloaded using any filetransfer. They become local objects
