FR2838017A1 - Interactive application preparation procedure for digital television uses hierarchical tree structure for themes and attribute lists with user matched individual link blocking - Google Patents

Abstract

An interactive application preparation procedure prepares XML (Extended Mark Up Language) or HTML (Hyper Text Mark Up Language) meta language data tables (tAppl, tAttr, tEl, tN) for each thematic (45, 46, 47) menu heading identifying a corresponding node (N0-2) with father node (41) and mother heading and uses it to create a hierarchical logical tree structure matching a selected user profile (45, 46, 47) and viewing terminal capability (48, 49).

Description

<Desc / Clms Page number 1>

Method for generating interactive applications, especially for digital television terminals
The present invention relates to the production of interactive applications, in particular for digital television.

 Interactive applications are encoded in a signal distributed over a digital transmission channel (cable, satellite or wireless network). The terminals receiving this signal are constituted in particular by TV receivers provided with a remote control module, forming execution platforms available to users. At least some of the interactive applications are thus intended to be installed on an execution platform to implement a succession of thematic topics in the form of a menu.

 Such interactive applications are associated or not with television programs. They may relate to both TV magazine type applications and services such as weather forecasts, stock market management, and others.

 Each heading of an interactive application menu corresponds to a thematic scene with a graphic and / or sound surround associated with this scene. Thus, the editing of a thematic scene on a TV set implies, on the screen of the station, a graphic dressing and, by associated sound reproduction means, a sound dressing. The graphic dressing can consist of the incorporation into the TV screen of animated sequences (from video files in mpeg format or other), bitmap images (from bitmap files, gif, or

<Desc / Clms Page number 2>

 others), or text with associated text editing attributes (characters, fonts, color).

The sound envelope can consist of a sound sequence that is played during the thematic scene (reading a file in WAV format or other).

 Generally, the menu is hierarchical in headings and sub-headings, with one or more levels of sub-topics. Thus, a plurality of sub-headings can be associated with the same main section, which can itself be the parent heading of a parent heading of a higher level. In principle, the items of the hierarchical menu are classified by themes (TV program, sports, meteorology, or others). It will thus be understood that each menu item may be associated with a graphic and / or sound wrap, as well as a thematic content of the section. For example, the thematic content of a sub-section may relate to basketball, while the thematic content of its parent section is related to sport, in general.

 The passage of a menu item to another topic, or more generally navigation in the menu, are conditioned by event / action pairs. An event may consist of an actuation of an organ of the remote control by the user, for example to access a selected item, while the associated action consists, in this case, in editing (display on the screen and sound reproduction) of a thematic scene corresponding to the selected section.

 The access terminals to these applications are equipped with operating systems allowing the processing

<Desc / Clms Page number 3>

 video images and sound reproduction, to edit and implement interactive applications.

However, this type of application can be accessed via very different access systems such as:
OPEN TV marketed by OPEN TV Incorporated in the United States, - Media Highway, distributed in France by CANAL +,
Mheg open system complying with the ISO standardization system, - the JAVA MHP-DVB system dedicated to television, currently being established, and - an HTML or XML browser that implements an HTML or XML interpreter (or browser) .

 In principle, the development of applications can only be done for a given operating system, corresponding to that of the final access system used.

 In the published application WO 01/04747, it has been proposed a rapid development system of interactive applications capable of correlating event / action pairs. The system generates a general list of possible pairs including identification fields.

In order to prepare the interactive applications that will actually be distributed over the network, the aforementioned list, upstream of the head of the distribution network, will select the event / action pairs that may be used for implementing the distributed interactive applications. , assigning values

<Desc / Clms Page number 4>

 selected in the identification fields of the selected pairs.

 Such a system makes it possible to overcome, in a very advantageous manner, the problems related to the differences between access systems that are not compatible and to the differences between terminals, in particular in terms of terminal capacity (size of RAMs, speed of processing of devices). processors, or fonts available for text editing).

 Nevertheless, as indicated above, interactive applications generally use hierarchical menus by themes. Thus, the addition or deletion of a theme requires the complete reconstruction of the menu and the corresponding interactive application. Updating interactive application menus therefore requires heavy programming on the part of the operator. Similarly, if a terminal user only wants a selection of interactive applications distributed according to a profile of his own (restricted parental agreement, or systematic favorites in a general menu), the operator should, in principle, provide a menu adapted to the requirements of the user.

 If the application development system WO 01/04747 allows a quick adaptation to a modification of the access system or the terminal, it does not allow a rapid reorganization of the interactive application menus when a modification of such menus is desired.

 The present invention improves the situation.

<Desc / Clms Page number 5>

 To this end, it proposes a method for producing interactive applications, in which: - data tables are prepared that comprise, at least, for each current item of a menu, an identifier of a node corresponding to this current item. and an identifier of a parent node corresponding to a parent heading of this current topic in the menu, and generating, from the data of the tables, a list comprising at least descriptive elements of the nodes and hierarchical according to a logical tree whose nodes are positioned according to said identifiers of nodes.

 If necessary, the process continues with a reading of the list by an interpreter, as will be seen later, to build an interactive application corresponding to the menu whose items are declared with a valid identifier in the list, this menu being prioritized according to the values of the identifiers.

 Thus, according to one of the advantages provided by the present invention, the operator can initially have a complete table in which are listed a plurality of possible items in the form of nodes. These headings are associated with respective sub-headings, as well as sub-headings girls of one or more levels still lower. If, in this complete table, it is desired to delete a particular topic, the operator assigns a predetermined identifier code to the n # ud corresponding to this item (for example an unavailability code) and this item, as well as its child items in the menu tree, will not appear when

<Desc / Clms Page number 6>

 the corresponding interactive application will be implemented.

 In a preferred embodiment, a main list is generated comprising several sub-lists hierarchically nested according to the aforementioned logical tree.

The list includes, for each node, respectively descriptive elements: of the position of this node in the logical tree, of information containers of a section corresponding to this node, and of attributes associated with each information container.

 In this embodiment, the data tables comprise: a first table of data relating to positions of nodes in the logical tree, this table comprising for each node at least: the identifier of this node; #ud, # the identifier of the parent node of this node, # and a name assigned to this node, - a second data table relating to the information containers, this table comprising for each container at least : # an identifier of this container, # the identifier of the n # ud with which this container is associated, # and a container name, - and a third data table relating to attributes associated with the information containers, comprising for each attribute at least: # an identifier of this attribute,

<Desc / Clms Page number 7>

 # the identifier of the container with which the attribute is associated, # and a name of the attribute.

 Thus, the elements of the tables have a link of hierarchy from one table to another: we assign to each current attribute (element of the table of attributes) a identifier containing father (element of the table of containers) and, at this father container, an identifier of the parent node (element of the table of nodes). In this embodiment, each table therefore comprises an identifier of an element of the table, a name of this element and an identifier of a parent element of another table.

 In a more elaborate embodiment, the above-mentioned main list also comprises descriptive elements of interactive applications in which one or more nodes intervene. In addition to the three tables above, a fourth table of data relating to interactive applications is provided, this fourth table including for each interactive application: # an identifier of this interactive application, # and a name attributed to this interactive application.

 The first data table further comprises, for each n # ud, the identifier of the interactive application in which a topic associated with this node intervenes. Thus, an element of the node table is hierarchically linked to a parent element of the declarative table of interactive applications.

 As a variant, provision is made for a set of first, second and third data tables per application

<Desc / Clms Page number 8>

 interactive. In this variant, a main list is thus generated by an interactive application.

 Each interactive application being capable of spreading over several successive levels of items, it is advantageous for each node of the first table to provide data relating to a level name in which this node intervenes, the hierarchical list comprising in addition, descriptive elements of levels of nodes. Where appropriate, a level name may be for the level of a set of items in a menu, while a next level name is for a lower level for a set of subtopics of one of the above items.

 Advantageously, the information containers are classified by thematic classes and the second table further includes data relating to a thematic class name to which each information container belongs. Thus, the hierarchical list further includes descriptive elements of classes of containers.

 If necessary, if a user wants a particular interactive application profile (parental control or other), the information containers are thus accessible by thematic classes, it is easy to identify the information containers unwanted menu items, for delete them.

 The aforementioned attributes can be of different types. Advantageously, the attributes of the attribute table are classified by types chosen from a set comprising at least: #a string of alphanumeric characters, such as a text,

<Desc / Clms Page number 9>

 # a path to a graphic and / or sound skin component, such as a link to a multimedia file, # and an attribute aggregate, such as a set defining a text font (size, font, font , style or others).

Thus, the attribute table further includes data relating to an attribute type and the hierarchical list further comprises descriptive elements of attribute types.

 Advantageously, the hierarchical list comprises, on the one hand, descriptive elements of attribute names and, on the other hand, descriptive elements of attribute values, and the third table furthermore includes data relating to a value of each attribute. Thus, one declares both an attribute name in the attribute table (for example a text character size name) and the value of this attribute (for example 12). The value of an attribute can also be thematic (for example, ARIAL can be a thematic value of the text font name attribute).

 In a sophisticated embodiment, the aforementioned declarative sub-list which includes the attribute descriptive elements, includes secondary sublists of attribute descriptive elements, nested according to a logical tree of attribute nodes, and the third The table further includes data relating to an identifier of a father attribute of each attribute.

 So, a father attribute in the attribute sub-list may actually be an aggregate

<Desc / Clms Page number 10>

 attributes, which are identified in a secondary sub-list. Thus, from the attribute table, a hierarchy is generated among the attributes.

 According to one advantageous aspect, a file, said media, of data of information of contents of headings and / or graphic dressing (and / or sound) of headings is also prepared. The aforementioned hierarchical list then includes descriptions of paths to data in this folder.

 In a particular embodiment, these access paths can be defined as attributes (or attribute values), such as Uniform Resource Locator (URL) links.

 Alternatively or additionally, the hierarchical list may also include at least one path to at least one secondary list, which includes paths to data in the media folder.

 Each interactive application being capable of spreading over several successive levels of items as indicated above, an information data file is advantageously prepared and a hierarchical list is generated comprising paths to data in said file. , for each level of an interactive application.

 Thus, the method according to the invention, in its general form, allows an operator or a user of the terminal to easily access the contents of the distributed interactive applications and to modify them quickly.

<Desc / Clms Page number 11>

 The method can be implemented by both the operator and the user. In this respect, the present invention also aims at a system for producing interactive applications, comprising: a headend arranged for distributing signals representative of interactive applications on a digital transmission channel; an execution platform arranged to receive these signals and adapted to install the interactive applications to implement a succession of thematic topics in the form of a menu.

 In the system within the meaning of the present invention, the headend includes: a data table editor comprising at least, for each current item of a menu, an identifier of a node corresponding to this current item and an identifier of a parent node corresponding to a parent heading of this current section in the menu, and a formatting automaton capable of generating, from the data of the tables, a list including at least descriptive elements of the n # #s. uds and hierarchized according to a logical tree whose nodes are positioned according to the identifiers of nodes.

 In a first embodiment, the headend is arranged to send to the execution platform the data of the tables, as well as the formatting automaton, for the purpose of generating the above-mentioned hierarchical list at the platform level. 'execution.

 Advantageously, the execution platform includes means for updating the data of the tables.

<Desc / Clms Page number 12>

 to generate menus based on a user profile of the terminal.

 In a second embodiment, the headend sends only the hierarchical list to the execution platform, the hierarchical list being generated at the headend.

 Advantageously, in this second embodiment, the headend includes means for updating the data tables and sends to the execution platform an updated list as a function of the specificities of the terminal (such as a memory capacity terminal, conditioned access to predetermined menu items, conditioned access to predetermined interactive applications, or the like).

 In an advantageous aspect, the data of the tables are initially coded in the form of a text file script. The updating means may simply comprise a text editor for adding and / or deleting and / or modifying sections and / or contents of menu items.

 In general, the execution platform comprises means for interpreting the hierarchical list to implement on the execution platform a hierarchical menu corresponding to the list.

 According to another advantageous aspect, the headend sends to the execution platform a so-called media file, comprising information data item contents and / or graphical dressing (and / or sound) of items. The hierarchical list then includes path descriptions to data from the

<Desc / Clms Page number 13>

 media folder. The above-mentioned means of interpretation are capable of identifying the access paths of the list and advantageously comprise executable files (commonly known as pluggins) for reading the files of the media folder and thus implementing the content of each menu item. on the execution platform, in correspondence of a graphical (and / or sound) layout described in the hierarchical list.

 Each interactive application being capable of spreading over several successive levels of items, the headend sends advantageously to the execution platform: a file comprising data of content information of items and / or dressing graphic and / or sound of items, - a hierarchical list comprising descriptions of paths to data in the media folder, for each level of the interactive application.

 Thus, in a system within the meaning of the present invention, the hierarchical list is generated from the data tables, using a formatting automaton.

However, formatting the tables to generate the list is done under the control of a document type definition file (commonly referred to as the Document Type Definition (DTD) abbreviation). Such a file is therefore an important means for implementing the invention. As such, the present invention also aims at a data structure comprising data from the DTD file and then comprising a succession of declarative tags comprising at least: a declaration of nodes corresponding to the items,

<Desc / Clms Page number 14>

 - a declaration of elements corresponding to the containers of rubrics, - and a declaration of attributes associated with the containers of rubrics.

 In practice, particularly in the case of a transmission of the tables to the terminal for a list generation at the terminal, the data of the DTD file are encoded with the data of the tables and, in an advantageous embodiment, the data structure therefore comprises a first data table relating to node positions in a logical tree representative of a menu tree, such as the first node table of the above type; a second data table relating to information containers, such as the second container table of the above type, and a third data table relating to attributes associated with the information containers, such as the third attribute table of the above type.

The data structure further comprises means for formatting the data of the tables to generate a hierarchical list under the control of the aforementioned declarative tag sequence (DTD).

 In an advantageous embodiment, the succession of declarative tags is in the form of a document type definition file (DTD), this definition being according to a metalanguage such as SGML or XML.

Advantageously, the hierarchical list is in the form of a metafile (XML or HTML) intended to be read and interpreted on an execution platform.

<Desc / Clms Page number 15>

 Formatting the data according to a metafile (XML or HTML) is of interest for generating or modifying trees, such as hierarchical menus in the present application of the invention.

 There are lists of descriptive elements of items and / or containers of items of a menu (with reference to themes of the menu), lists of descriptive elements of contents of the menu items (with reference to information contained in the menu). To generate these lists of elements describing content of topics (including links to one or more media folders), we use a document type definition file (DTD) but whose data structure is still different from the one stated. above.

 To generate such listings of item content descriptive items, the present invention provides a data structure comprising data from this DTD file, in the form of a succession of declarative tags including at least: - a statement of a object as the contents of a field, - a declaration of a state of the object, - a declaration of an interaction automaton capable of generating event / action pairs suitable for modifying the state of the object .

 Content of a topic, for example audiovisual content, or content of information in the form of text, is understood to mean the other.

<Desc / Clms Page number 16>

 The state of the object, for example a selected state, a selectable state, a hidden state, or the like.

 In one embodiment, the terminal is provided with a list of topic contents with at least one media folder for an interactive application level, the list including paths to files in the media folder. To switch to a sub-level of the interactive application, a second transmission of another list with paths to another media folder is provided.

 In an advantageous variant, the aforementioned data structure comprising the data of the DTD file, with one or more media files, is transmitted to the terminal, which makes it possible, at the level of the terminal, to generate a list of contents of sections selected by the user. following his profile (parental agreement or other). Thus, the aforementioned data structure further comprises: - at least one media file comprising: # editorial data of contents of sections, # multimedia files (sound files, image files, video files, or other) and / or files information (text files, text font files, and others).

The data structure further comprises means for formatting the data of the media folder to generate, under the control of the aforementioned declarative tag succession (DTD), at least one list comprising at least one description of a path to the file. a file in the media folder, or a description of a path to a

<Desc / Clms Page number 17>

 another list to predict a level change in the interactive application.

 Advantageously, the succession of declarative tags is therefore in the form of a document type definition file (DTD) according to a metalanguage type SGML or XML. The generated list is in the form of a metafile such as an HTML or XML page that can be read and interpreted on an execution platform to implement, on this execution platform, the content of at least one topic in correspondence of the data of the media folder.

 Advantageously, the aforementioned declarative tag sequence further comprises a declaration of a graphic organization of the object for correspondingly editing the content of the item on the execution platform. This can be for example a position definition of an image on the screen of the TV set.

 Other characteristics and advantages of the invention will appear on examining the detailed description below, and the attached drawings in which: FIG. 1 schematically represents an interactive application development system, for digital television, comprising: a server and a terminal for implementing the interactive applications distributed by the server; FIG. 2 represents data tables comprising identifiers of interactive application elements, the data of these tables being intended to be formatted according to a hierarchical list;

<Desc / Clms Page number 18>

 FIG. 3 schematically represents the steps of a method of formatting a hierarchical list and interpreting this list for implementing an interactive application on an execution platform; FIG. 4 diagrammatically represents a tree of the hierarchical list as a function of the identifiers that comprise the data tables, with, in the example represented, a deletion of branches of the tree controlled by the user of the terminal; FIG. 5A partially represents the aforementioned hierarchical list, edited in the form of a table, from a spreadsheet program such as ACCESS; FIG. 5B partially represents a hierarchical list edited in the form of a table, in which the columns respectively comprise the identifiers of nodes, the identifiers of the parent nodes, the identifiers of the associated interactive applications, the names of the n #uds and node level in the associated interactive application; FIG. 5C partially represents the aforementioned hierarchical list, edited in the form of a table, with nodes removed on command of a user of the terminal, in the example represented; FIGS. 6A, 6B and 6C represent displays on a screen of an execution platform, respectively of a graphic skin associated with a menu item, of a graphic skin associated with a second item of a same level of the menu, and a graphic skin associated with a sub-item of a lower level of the menu;

<Desc / Clms Page number 19>

 FIG. 7A partially represents a tree structure of a node to attributes associated with information containers; and FIG. 7B schematically represents the tables transmitted at different levels of progress of an interactive application.

 In Annex I are transcribed data tables (TableO file for a home portal menu) relating to a first level in the progress of an interactive application.

 In Annex II are transcribed the data tables (TableOl file for a TV programs section) relating to a second level in the course of the interactive application.

 In Annex III are partially transcribed the instructions of an automaton formatting AFT data tables in language JAVA.

 In Annex IV are retranscribed the data of a DTD document type definition file to generate a hierarchical list, of the aforementioned type.

 Annex V is partially transcribed a hierarchical list, in XML language (menuO.xml file), obtained from the tables in Annex I.

 In Annex VI is partially transcribed a hierarchical list, in XML language (menuOl.xml file), obtained from the tables of Annex II.

 In Appendix VII are transcribed the data of a DTD document type definition file to generate a graphical declaration declaration XML file of interactive application menu items.

<Desc / Clms Page number 20>

 In Annex VIII are partially transcribed the data of the aforementioned XML file, declaration of graphic appearance, obtained by formatting data under the control of the DTD file of Annex VII.

 In Annex IX is transcribed a hierarchical list, in XML (menu0bis.xml file), variant of the list of Annex V because it declares both menu items and a graphic skin associated with each item.

 Referring first to FIG. 1, a headend 2 of a server transmits, via the radio network (antenna AS, in the example shown), a signal comprising digital television data, as well as data interactive applications intended to be implemented on an execution platform comprising, in the example described, a terminal 1 and a television set equipped with an ECR screen, this execution platform comprising an AT antenna adapted to receive the signal transmitted from the server.

 The interactive applications are installed at a point of the digital transmission network to enable transmission of these interactive applications, either on request of a user in the case where these interactive applications are transmitted via the WWW ("World Wide Web"). "), in the form of HTML documents, or else broadcast in a cyclic manner when the digital transmission channel is a television channel, as in the example shown in FIG. 1. In particular, the cyclic data may contain XML documents or HTML and applications in JAVA interpreted language, for example with the system

<Desc / Clms Page number 21>

 MHP-DVB access point indicated above. Alternatively, the transmission of HTML documents can be performed from a WWW site and a dedicated server. However, as will be seen below, the present invention advantageously makes it possible to dispense with an access route to a WWW site, since the user can himself, according to his profile, directly program his terminal 1, to select the items of the menu broadcast cyclically, which he wishes to edit on his computer.

 Each interactive application consists of a succession of thematic scenes that may incorporate bitmap or video images (with the reference IM in Figure 1), sound sequences, and text file information. Thus, with reference to FIG. 1, on the ECR screen of the station of the execution platform, an IM video or bitmap image appears on a BCG screen, as well as a TXT text. , where appropriate referring to an event represented in the IM image, and a PIC pictogram allowing the user to start an animated video sequence or a sound sequence, in relation to an event represented in the IM image. On a lower part of the ECR screen appears a BM menu bar which, in the example shown, is in the form of a scrolling banner comprising menu items (in the example shown radio program guide, news , meteorology, TV program guide, return to the previous menu or exit the "menu" application). The items shown on the menu bar BM are, at least in part, selectable from an input member 11 (such as a remote control). A CU cursor is

<Desc / Clms Page number 22>

 moves along the BM menu bar to visually indicate to the user the current topic he can select. For example, when the execution platform uses the OPEN TV access system, the operating system is, in principle, dedicated to the interactive application in question and the control module allowing the selection of items in the unfolding the interactive application is constituted by a control module 11, such as a universal remote control with buttons, for controlling the TV with the ECR display monitor. It will thus be understood that the above-mentioned execution platform comprises a television set equipped with an ECR display screen, a universal button remote control 11, the access terminal 1 and, if applicable, the antenna of FIG. AT reception.

 Referring to FIGS. 6A, 6B and 6C, the screen of the execution platform can display animated video sequences (eg from MPEG, AVI or other files), still images (for example, still images). bitmap mode), PIC pictograms (for example, vector-mode images), as well as TXT text (which is associated with a chosen font, a chosen font size, or other). In particular, the screen is divided into two zones Z1 and Z2, an upper zone in which are presented the graphic elements of a menu item and a lower zone Z2 in which is represented the menu bar BM with the names of these topics. Of course, the delimitation (shown here in dotted lines) between the upper and lower areas of the screen does not appear, in practice, on the screen of the execution platform. The user of

<Desc / Clms Page number 23>

 terminal, when for example selects the TV category, appears on the screen a TV program guide presented in the form of a sequence of IM images and TXT texts in correspondence of these images IM (Figure 6A) . When the user activates with his input member 11, a "right" arrow, the graphic skin associated with the new section "NEWS" (for news) appears on the screen of the execution platform with new images and, in the example shown in FIG. 6B, pictograms corresponding to these IM images.

 Referring to Figure 6C, when the user validates a topic in the BM menu bar (the "NEWS" in the example shown), the user will see a second BM2 menu bar, while the attributes of the old BM1 menu bar are modified: the unselected items of the old BM1 menu bar are represented in shaded parts. Advantageously, it is preferentially retained a remanence of the formerly selected parent items, when passing from a menu item to a sub-heading. In addition, each item and / or sub-item of the menu corresponds to a graphic skin, on the one hand, of the menu bar in which this item appears (lower zone Z2 of the screen) and, on the other hand, editorial content associated with this topic (in the upper Zl area of the screen).

 It will thus be understood that the items and sub-menus of the interactive applications menu respect a logical chaining, according to a tree structure which will be described below.

<Desc / Clms Page number 24>

Referring now to FIG. 2 on which data tables T1, T2, T3 and T4 are initially prepared, assigning values to identifiers it comprises, the aforementioned hierarchical list being obtained from a formatting of these data tables T1 to T4 as will be seen later
In the example described, the table T4 includes data relating to all the interactive applications envisaged by the server. It can be in the form of a text file, or script, whose assigned file name is t ~ Appl. This table T4 contains all the identifiers of interactive applications intended to be received by the terminal 1 or by a family of terminals receiving interactive applications distributed by the same operator. The table T4 therefore comprises an identifier of the interactive application ID ~ Appl, as well as a name (variable "Name") that is assigned to this interactive application. For example, an interactive application identifier may be the language in which this interactive application is to be implemented (French, English, Spanish or other).

Thus, it will be understood that a numerical value is assigned to the interactive application identifier ID ~ Appl, for example "1" for an interactive application in French, to which is given the name "French" (variable "Name") . Similarly, an interactive English application will have an ID ~ Appl identifier with a numeric value "2" and the name given to this interactive application becomes Name "English".

 The table T1 of FIG. 2 is an underlying table of the table of interactive applications T4. She

<Desc / Clms Page number 25>

 is also in the form of a text file or script, name "t ~ N". This table Tl is intended to represent the different nodes of the tree that implements the respective sequences of all the interactive applications envisaged. Each application is identified in the table Tl by the variable ID ~ Appl.

In the example described, the parameters of the table T2 are: a numerical identifier of a current node ID ~ N; a numerical identifier of a parent node of this current node ID ~ PN; the numerical identifier of the interactive application that implements these ID ~ Appl nodes; the "Name" variable (in principle an alphanumeric variable) corresponding to the name of the current node; and the variable "Level" (alphanumeric variable in the example described) corresponding to a level of the node in the tree of the interactive application. This level variable allows the grouping of nodes by classes. Advantageously, a list of nodes is thus constituted by grouping the nodes of the same father node, on the one hand, and the nodes of the same level variable, on the other hand. By way of example, reference can be made to FIG. 5B in which all the nodes of the list are associated with the same interactive application, with identifier "3". In particular, the first level of the interactive application corresponds to the variable "Mainlist". This level "Mainlist" corresponds to the first level of the interactive application identifier "3", when loading a home portal menu to implement the interactive application "3". So, the root node of the application

<Desc / Clms Page number 26>

 interactive (first n # ud father) is named level the variable "Mainlist". The numeric identifier of this root node is "1". Thus, line 11 of FIG. 5B is relative to the name of a "radio program" of the identifier of n # ud "3" and of the identifier of n # of the parent "1" (root node).

Following the same example, the next line is relative to the name node "List of radios". It is then a lower level in the tree of the interactive application implemented, this lower level bearing the name "radiolist". The identifier of the node "list of radios" is 30 (column ID ~ N), while the identifier of its parent node ("radio program") has the numerical value "3" (column ID ~ PN ). In another example in Figure 5B, the interactive application tree begins with the root node "Mainlist", another node of this root node is the "Sports" identifier node. 5 ". A n # ud son of the n # ud "Sports" is the n # ud "Football", in the level "Sportlist". The identifier of the "Football" node is "52". In a still lower level "Sportfoot", a child of the N # ud "Football" is "contentsportfootball", carrying the identifier "520".

 Reference is again made to FIG. 2, in which the table T2 comprises data relating to information containers of the interactive applications implemented. It is also in the form of a text file or script file name t ~ El. In principle, the table T2 contains only information related to one node or several nodes of the table T1, but no information specific to the actual content of the menu items. The parameters of the table T2 are the following: an identifier of information container ID ~ El;

<Desc / Clms Page number 27>

 an identifier of a current node with which this information container is associated ID ~ N; a "Name" variable corresponding to the name given to this information container; and - a variable "ClassEl" (in principle alphanumeric) relating to a class of information container, such as a menu theme, or a user profile.

 The table T3 of FIG. 2 relates to the attributes associated with its information containers. It is in the form of a text file or script, file name t ~ Attr. Thus, it will be understood that each line of this table identifies information content.

An attribute can have a relatively complex structure. For example, a "sports event" information container may consist of a date, a venue, a host team, a guest team. The information container "sports event" is, in principle, listed in the table T2. On the other hand, the date, the place and the aforementioned teams will be attributes listed in table T3. Nevertheless, "it will be understood that the date itself is formed of a day, a month and a year, so an attribute may be the current attribute of a father attribute and, for this purpose, the table T3 of the attributes comprises: - an identifier of a current attribute ID ~ Attr, - a father attribute identifier of this current attribute ID PAttr, thus creating a hierarchy within the table of attributes T3; an information container in the table T2, ID ~ E1;

<Desc / Clms Page number 28>

 a name given to the current attribute (alphanumeric variable "Name"); a value (variable "Val") given to this current attribute, which will be described below; and a "Type" variable associated with this current attribute, which will be described below.

 As indicated above for a container "sports event", the name of the current attribute can be the variable "Name": "Guest Team". In this case, the variable Val corresponds to the value of this attribute, for example "Marseille" in the example described. It is thus clear that the variable Val (in principle alphanumeric) can be a thematic value associated with an attribute.

However, it can still be a physical value.

For example, "12" is the Val value of the "character size" attribute.

 The Type variable is relative to a current attribute type, among: - a text in the form of an alphanumeric character string (Type = TXT); - a path, such as a URL (Type = URL); and an aggregate of attributes such as, for example, the characteristics of a font: size, font, style (bold, underlined, italic). In the latter case, the Type variable is "GrpAttr".

 The aforementioned alphanumeric character string may correspond to the part of text in zone 1 of the graphical skin in correspondence of the menu items, or to the text in the menu bar BM, in zone 2 of the screen of display. The URL address mentioned above

<Desc / Clms Page number 29>

 can correspond to a path to a component, such as a multimedia file (image, animated sequence, sound sequence or other) for dressing in zone 1 of the screen, or to a corresponding secondary hierarchical list at a different level (higher or lower) in the implementation of the interactive application on the runtime platform, as will be discussed below. In the case of an aggregate of attributes, it will be understood that the identifier of the attribute aggregate corresponds to the identifier of a father attribute ID ~ PAttr of a plurality of current attributes.

 In general, it will be understood that the tables T1 to T4 are hierarchized as follows: each downstream table comprises element identifiers which are fully described in an upstream table, according to an advantageous characteristic of the present invention. In a preferred embodiment, the table of nodes Tl is hierarchized "internally" since it includes data relating both to a current node and to a parent node of this node. current declared in the same table. The same is true for the attribute table T3, in the preferred embodiment shown in FIG. 2.

 As an alternative to the embodiment shown in FIG. 2, the table T4 of the interactive applications can be deleted. In this case, for each interactive application considered, provision is made for a set of three data tables T1, T2 and T3, respectively relating to the nodes of the interactive application under consideration, to the information containers of these nodes and to the attributes of these information containers.

<Desc / Clms Page number 30>

 In addition, in a less sophisticated variant of the embodiment shown in Fig. 2, the table of information containers T2 may be deleted. In this case, the data relating to the information container can be incorporated in the table Tl of the nodes, or in the table T3 of the attributes. Nevertheless, the deletion of the T2 information container table makes the structure of the Tl and / or T3 tables more complex and the updating of the data in the Tl and T3 attribute tables proves more difficult. .

 Reference is now made to Figure 7A to describe an example of classes of information containers listed in Table T2. The node of the Tl table, with the name "TV program", has the numerical ID ID # N "1" (box 61 in Fig. 7A).

In the information container table T2, the identifier of this "TV program" node is listed for three classes of information containers (boxes 62, 63 and 64 of FIG. 7A). The identifiers of the information containers grouped in the class "LogicalContent" are identified by the numerical values "11" to "14". This class of elements may relate to a thematic element such as today's date to display the headings of a television program guide corresponding to that date. In box 65, the attributes associated with information containers in the box 62 class will be the date, with its value of the day, if any, the current time, with its value, or whatever.

 A second class of information containers (Box 63 in Figure 7A) relates to the

<Desc / Clms Page number 31>

 navigation of a heading to a sub-heading. Thus, the attributes associated with this class of information containers (box 66 in FIG. 7A) correspond, for example, to a path to a next hierarchical list (file in XML format in the example described). As will be seen later, this next hierarchical list includes all the information relating to the next level in the interactive application implemented (sub-section "TV program" of the main home portal). Thus, it will be understood that the attribute table T3 may include paths to a second hierarchical list when moving from a first level to a second level in the interactive application. The file corresponding to the next hierarchical list is named "menu0l.xml" here.

 The third class of information containers (box 64 of FIG. 7A) relates to the graphic cover in the upper area Z1 of the execution platform ECR screen. Thus, the attributes associated with the information container in this class "contenerEdito" include a path to a "programTV.XML" file (box 67 of Figure 7A). In this file "programTV.XML" are listed URL links to multimedia files (sound, image, video or other) to produce the graphic dressing of the upper zone of the display screen.

 Thus, the classes of the table T2 can be relative to a logical theme (for example the time and the date), to a menu theme (to pass from a heading to

<Desc / Clms Page number 32>

 the other) or to a theme of dressing of heading (dressing of zone Zl).

 Reference is now made to FIG. 3 to describe an interactive application transmission method from server 2 to terminal 1, supra. In this embodiment, provision is made for a cyclic diffusion of all the interactive applications intended to be implemented on the execution platform.

 In a preferred embodiment, the data tables T1 to T4 are formatted at the terminal 1, to generate a hierarchical list representative of a menu item. In this embodiment, the operator distributing the interactive applications prepares, at the head end, the contents of the interactive application data tables T4, Tl nodes, T2 information containers and T3 attributes. These data tables are encoded and transmitted in a wireless signal, from the server 2 and to the terminal 1. Preferentially, the data tables T1 to T4 are transmitted with a media folder 36 comprising for example multimedia files dressing graphic, sound or other, as will be seen later.

 In a preferred embodiment, the terminal 1 comprises a memory in which are pre-recorded digital data of a table formatting automaton 30. Annex III partially transcribes a formatting automaton in JAVA language, capable of generating a hierarchical list in XML language from the data tables T1 to T4. Of course, the formatting automaton which is retranscribed in the appendix involves JAVA classes and, if necessary, other non-transcribed JAVA programs.

<Desc / Clms Page number 33>

 right here. The formatting automaton 30 makes it possible to generate a document in XML format, here the hierarchical list 31, and to validate this XML document under the control of a document type definition file 35 (DTD file of the aforementioned type). Annex IV retranscribes the contents of a suitable document type definition file for editing hierarchical lists corresponding to menu items displayed in the BM menu bar on the ECR screen.

The DTD file 35 is preferably transmitted with the data tables T1 to T4, from the server 2 to the terminal 1. In a variant, the DTD file can be stored in the memory of the terminal 1.

 Moreover, the user of the terminal can enter, from an appropriate controller of the terminal, a user profile that he chooses. The user profile data 32 is thus entered in the memory of the terminal 1. When the terminal receives the data tables T1 to T4, if necessary with the formatting automaton of the tables 30 and the file DTD 35, the terminal 1 (In particular with computing means such as a suitable processor and a cooperative RAM working memory) generates a hierarchical list 31 whose content is modified or updated according to the user profile stored by the terminal 1.

 Referring to FIG. 5A, the hierarchical list 31, initially in XML format, has been interpreted and edited as an ACCESS file.

We note advantageously the tree structure of the list which begins with a declaration of the interactive application bearing the identifier "3". Then, a root node with the identifier "1" is the father of a

<Desc / Clms Page number 34>

plurality of successive nodes carrying the identifiers "2" to "13". To this plurality of successive nodes correspond therefore the headings of the main menu "Main List" that displays the screen of the ECR execution platform, as a home portal
Preferentially, a set of data tables is provided by successive levels of interactive applications (passage of a heading to a sub-heading). In fact, referring to FIG. 7B, the interactive application takes place in the example shown, on three levels, thus a first level "Level 0" corresponds to a menu bar of the type home portal. The set of tables transmitted Table 0 is transcribed in Appendix I. In particular, the node table contains the main sections of the home portal, including the "TV programs" section. Thus, when the user actuates a command button to display the home portal, the terminal 1 has already captured in the cyclically distributed wireless signal the tables in Appendix I, if necessary a media folder for the graphic dressing and the DTD file in Annex IV. The hierarchical list resulting from the formatting of the tables in Annex I is given in XML in Annex V. The hierarchical list thus generated corresponds to a "MenuO.XML" file. Only the first two pages of this XML file are retranscribed in Appendix V.

 Advantageously, the tables of the home portal are systematically captured in memory of the terminal 1, while the display of the home portal is conditioned by the operation of a key of the remote control 11. On the other hand, when the user

<Desc / Clms Page number 35>

 controls the display of the home portal, the terminal 1 captures in memory the tables corresponding to the lower level "Level 1" in the distributed interactive application. Indeed, we take into account here a delay induced by the capture period performed by the terminal. Thus, even if the user only requests the display of a menu item of the home portal, the terminal pre-captures and loads in memory all the data tables relating to all the sections of the home portal, so as not to delay the display of a particular section of the home portal that would then select the user.

 Annex II retranscribes the Table 01 data table set of level "Level 1" to generate a hierarchical list corresponding to the "TV Program" section. This hierarchical list is in the form of an XML file named "Menu01.XML", the first two pages of which are transcribed in Annex VI. As indicated above, the other tables of level "Level 1" are also loaded and other lists can be generated, for example a list relating to the section "News" (file Menu02.XML), there is still a section " Sports "(Menu03.XML file). Finally, if the user selects the "TV program" section, the terminal 1 then captures all the lower level "Level 2" data tables relating to the subtopics of the "TV program" parent section. Of course, it is possible to provide a capture of several successive levels, depending on the "depth" of the terminal, that is to say according to its memory and processing capabilities.

<Desc / Clms Page number 36>

 In principle, each actuation of a key on the remote control 11 by the user, corresponds to an event / action pair that can be defined as an attribute in a T3 attribute table captured by the terminal beforehand.

 Referring again to FIG. 3, the hierarchical list 31 (for example in an XML or HTML language) is interpreted (box 33) by an appropriate JAVA interpreter. Further provided (Box 34) is a library of executable files (so-called "pluggings") for reading the files of the media folder 36 for graphical editing of the items on the ECR screen.

 As a variant of the embodiment shown in FIG. 3, the data tables T1 to T4 can be prepared at the head end of the network. In addition, the table formatting automaton can be provided at the headend, with the DTD file, so as to generate the hierarchical list at the headend. This hierarchical list can be initially provided in an XML language and encoded to be sent to the terminal by the wireless network. In this case, the terminal has only a JAVA interpreter from the list and pluggings to interpret the files of the sent media folders.

Nevertheless, this embodiment is less advantageous insofar as the terminal user can not directly program his profile at the terminal.

 In a first embodiment, the graphic dressing of the zone Z1 of the screen of the execution platform ECR is carried out independently of the graphic dressing of the menu bar in the lower zone Z2 of the ECR display screen. For this, we plan a

<Desc / Clms Page number 37>

 media file comprising the aforementioned multimedia files (bearing the reference 36 in Figure 3), and a document type definition file (not shown in Figure 3) specific to the graphic dressing of the upper zone Zl of the ECR screen. Annex VII retranscribes such a document type definition file. For each interactive application page, we declare objects (image, text, sound, video clip or other) and their different states (normal, selected, highlighted, hidden, or other). It also declares an interaction automaton (up arrow, down arrow, right arrow, left arrow) which allows to navigate within the upper zone Z1 of the screen (for example to reach and select a pictogram and thus start a sound or video sequence). In this document type definition file, a graphic organization of the objects in the zone Z1 of the ECR screen is also declared. The XML file resulting from the formatting under the control of the document type definition file of Annex VII is reproduced in Annex VIII.

Advantageously, this XML file includes links to media files in the Media folder 36, as well as alphanumeric character strings for editing texts in the upper Zl area of the ECR screen.

 Only the first two pages of this XML file are retranscribed in Annex VIII.

 In a second, more advantageous embodiment, provision is made for a common DTD file for the graphic dressing of the zone Z1 and for the declaration of the fields in the zone Z2 of the application menu.

<Desc / Clms Page number 38>

 interactive. Similarly, there is a graphical dressing in the Zl area in correspondence with a selected item in the menu of the interactive application implemented. The hierarchical list is then generated from the data tables T1 to T4, the attribute table T3 including media folder paths, as well as a definition of the graphical organization of the objects in the zone Z1 and a definition an interaction automaton (an event / action pair definition). According to this second embodiment, Annex IX retranscribes a hierarchical list in XML format which is a variant of the "MenuO.XML" file of Annex V. Thus, this hierarchical list is representative of the home portal of the interactive application. Advantageously, in this variant, each section of the home portal is listed with a path to a page in HTML format (link "URL").

These HTML pages advantageously include access paths to multimedia files of the media folder 36 and paths to other HTML pages relating to sub-sections.

 In what follows, an update of the contents of an interactive application menu is described, for example by controlling a user profile stored in the terminal 1. A condition chosen here for a node to become a element of a hierarchical list, after formatting, is that this node has the same father as the other elements of the list. Thus, by modifying the identifier ID ~ PN of the table Tl of the nodes, one can add or remove an element of a list. In the same way, it is easy to add or remove an element and its

<Desc / Clms Page number 39>

 associated attributes by modifying the parameter ID ~ N in the table T2 of the information containers. Data relating to an information container can be added or deleted by modifying the value of the parameter ID ~ E1 in the table T3 of the attributes. Referring to FIG. 5B, the identifier of the parent node associated with the "News" and "Your Magazines" sections has been modified and a predetermined value has been assigned to it ("10,000" in the example described). This numeric value code indicates that the aforementioned items will not be displayed or accessible during the implementation of the interactive application on the runtime platform. Also, the subtopics of these "News" and "Your Magazines" sections will not appear in the hierarchical list.

Indeed, with reference to FIG. 5C, the items carrying the identifiers "4" and "6" no longer appear.

 Reference is now made to FIG. 4 to describe a modified tree according to a chosen user profile. In the example, an interactive application 1 is implemented (box 41). A root NO node provides a home portal with a plurality of items (box 42). Among the usual items, there is for example an item "e-mails" (carrying the identifier "9" in Figure 5C). If the user's terminal is not arranged to receive email messages of the email type, the corresponding N # node N1 (box 43 in FIG. 4) is deleted. In practice, a code "10,000" can be assigned to the identifier of the parent node of this "email" node in the table T1 of the nodes. On the other hand, if the user selects a chosen parental profile, classes of information containers may be

<Desc / Clms Page number 40>

 deleted (Boxes 45 and 46 in Figure 4). In this case, the identifier of the node N2 (box 44) in the table of information containers T2 will be assigned a value "10,000".

 In an implementation based on a complete implementation in XML, the terminal is advantageously equipped with a parser (or XML parser with API for Application Protocol Interface), which allows to delete the complete node corresponding to the item e - or some of the nodes in the parent profile section (and their underlying nodes and attributes).

 In addition, some terminals may not be equipped with sufficient memory or sufficient processing capacity to play relatively long video sequences. In this case, the attributes relating to such video sequences (eg links to the graphic dress declaration file in Annex VIII) may be deleted (Box 49 in Figure 4).

Similarly, the information container identifier in attribute table T3 is assigned a value of "10,000" for this attribute "Attr2" (box 49 of Figure 4). On the other hand, for other attributes such as "Attrl" (Box 48), the identifier of the information container in the T3 table of the attributes is assigned a correct value, which corresponds to the corresponding information container in table T2 (containing information E3 of box 47).

 Finally, the terminal, reading and interpreting the hierarchical list thus generated, truly behaves like a computer equipped with a

<Desc / Clms Page number 41>

 operating system of its own, perfectly autonomous.

 Of course, the present invention is not limited to the embodiment described above by way of example. It extends to other variants.

 Thus, it will be understood that the hierarchical lists can be in the form of files in XML format, but still in other forms of files such as an HTML page, or a text or script page, which can be interpreted by an adequate JAVA interpreter.

 In respective appendices I and II, the data tables are grouped as a single file. A "return line" character can be interpreted during formatting as a separation of data from tables. Alternatively, one can provide a file (text or script) per table. In addition, the hierarchical lists transcribed in the appendix are in XML format. Alternatively, they may be HTML pages.

 Of course, the interactive applications can be distributed over a wireless network as described above, or by a wired network, or the like.

 More generally, the present invention is not limited to applications for digital television, but to all applications using hierarchical menus.

<Desc / Clms Page number 42>

illir ; liolit ;iijit ;"ProgrammeTV";"niveau0l' "10" ;"01";"1";"Quitter";"niveau0"

"2";"Ol";"1";"Programmeradio";"niveau0" "10" ;"01";"1";"Quitter";"niveau0" "4" ;"01";"1";"Sports";"niveau0" "5" ;"01";"1";"Vosmagazines";"niveau0" "6" ;"01";"1";"Vielocale";"niveau0"

n 7 ii ; n o i " ; i ; "ViePrat ique " ; "niveauO "8" ;"01";"1";"Email";"niveau0" "9" ;"01";"1";"Internet";"niveau0" Table t~El "100";"10";"Lquitter";"contenerlogique" "101";"10";"Equitter";"contenerEdito" "102";"10";"Nquitter";"contenernavigation" "103";"10";"Nquitter";"contenernavigation" "11" ;"1";"Ltv";"contenerlogique" "12" ;"1";"Etv";"contenerEdito" "13" ;"1";"Ntv";"contenernavigation" "21";"2";"Lradio";"contenerlogique" "22";"2";"Eradio";"contenerEdito" "23";"2";"Nradio";"contenernavigation" "31";"3";"Lactualite";"contenerlogique" APPENDIX I TableO Table t ~ Appl "1";"Metalistfrench" Table t ~ N "01";"0";"1";"Menu0";"level0";

illir; liolit; iijit; "ProgramTV";"level0l""10";"01";"1";"Exit";"level0";

"2";"Ol";"1";"Programmeradio";"level0""10";"01";"1";"Exit";"level0""4";"01";"1";"Sports";"Level0""5";"01";"1";"YourMagazines";"Level0""6";"01";"1";"Vielocale";"Level0";

n 7 ii; noi ";i;" FieldPeriod ";" levelO "8";"01";"1";"Email";"level0""9";"01";"1";"Internet";"level0"; Table t ~ El "100";"10";"Litter";"logical""101";"10";"Equitter";"contenerEdito""102";"10";"Nquitter";"contenernavigation"" 103 ";" 10 ";" Nquitter ";" contenernavigation "" 11 ";" 1 ";" Ltv ";" conenerlogic "" 12 ";" 1 ";" Etv ";" contenerEdito "" 13 ";" 1 "Ntv";"contenernavigation""21";"2";"Lradio";"conenerlogic""22";"2";"Eradio";"contenerEdito""23";"2";"Nradio";"contenernavigation""31";"3";"Lactuality";"conenerlogic";

<Desc / Clms Page number 43>

"1112";"1111";"11";"descriptionetat2";"PROGRAMMES TV";"texte" "1113";"1111";"11";"descriptionetat3";"programmes TV";"texte" "1121" ;"0";"11";"position";"1";"nombre"

"1122";"1121";"11";"scrollmount";"200";"pixels" "1123";"1121";"11";"scrolldelay";"10";"ms" "32";"3";"Actual";"contenerEdito""33";"3";"Actuality";"contenernavigation""41";"4";"Lsport";"logical""42";" 4 ";" Esport ";" contenerEdito "" 43 ";" 4 ";" Nsport ";" contenernavigation "" 51 ";" 5 ";" Lmagazine ";" dynamic "" 52 ";" 5 ";" Emagazine ";" ContenerEdito "" 53 ";" 5 ";" Nmagazine ";" contenernavigation "" 61 ";" 6 ";" Llocal ";" logical "" 62 ";" 6 ";" Elocal ";" contenerEdito ";"63";"6";"Nlocal";"contenernavigation""71";"7";"Practice";"logical""72";"7";"Epaic";"contenerEdito""73";" 7 ";" Npratic ";" contenernavigation "" 81 ";" 8 ";" Lemail ";" conenerlogic "" 82 ";" 8 ";" Eemail ";" contenerEdito "" 83 ";" 8 ";" Nemail "conternernavigation""91";"9";"Linternet";"conenerlogic""92";"9";"Einternet";"contenerEdito""93";"9";"Ninternet";"contenernavigation" Table t Attr "1100";"0";"11";"date";"27/11/2001";"date""1111";"0";"11";"descriptionetatl";"TVPrograms";"text"

"1112";"1111";"11";"descriptionetat2";"TVPROGRAMS";"text""1113";"1111";"11";"descriptionetat3";"TVprograms";"text""1121";" 0 ";" 11 ";" position ";" 1 ";" number "

"1122";"1121";"11";"scrollmount";"200";"pixels""1123";"1121";"11";"scrolldelay";"10";"ms"

<Desc / Clms Page number 44>

"1125";"1111";"11";"taille";"16";"caractere" "1126";"1111";"11";"style";"gras";"stylecaractere" "1127";"1111";"11";"couleur";"0,0,0";"couleurRVB" "1128";"1111";"11";"background";"10,10,10";"couleurRVB"

"1130";"1131";"11";"PiCtoetat2";"plCtOZOOml.jpg";"image" "1131";"0";"11";"Pictoetatl";"pictonormall.gif";"image" "1132";"1131";"11";"Pictoetat3";"pictoeteintl.gif";"image" "1500";"0";"12";"urleditohtml";"programmetv.html";"url" "1501"-"0"-"13" "urlmetalistdtdStvdbml" "menu01.xm1"-"url" "1502";"1500";"12";"descriptionedito";"description éditorial programme Tv";"texte" "1503";"1500";"12";"date";"date de mise à jour de l'édito programme Tv";"date" "1504";"0";"12";"urleditoxml";"programmetv.xml";"url" "1505";"0";"12";"urleditogif";"programmetv.gif";"image" "1506";"1504";"12";"descriptionxml";"description suivant la DTD de l'habillage zone l""Tvi.dtd""";"texte" "1507";"1501";"13";"description";"Url du pivotnavigation suivant DTD ""STVDbml.dtd""Element Application, ElementNoeud, Element Element,Element Attribut";"texte"

"1508"-"0";"13";"urlmetalistbis";"menubis0l.xml";"url" "1509";"1508";"13";"description";"Url de pivotnavigation suivant un formatsimple";"texte" "1510";"1505";"12";"description";"autre type de présentation de la partie éditoriale de l'habillage zone 1 sous forme d'une image codée gif";"texte"

"4100";"0";"41";"date";"27/11/2001";"date" "4111";"0";"41";"descriptionetatl";"Sports";"texte" "4112";"4111";"41";"descriptionetat2";"SPORTS";"texte" "4113";"4111";"41";"descriptionetat3";"sports";"texte" "1124", "1111";"11","police","Helvetica","character"

"1125";"1111";"11";"size";"16";"character""1126";"1111";"11";"style";"bold";"stylecaracter""" 1127 ";"1111";"11";"color";"0,0,0";"RGBcolor""1128";"1111";"11";"background";"10,10,10";"RGBcolor"

"1130";"1131";"11";"PiCtoetat2";"plCtOZOOml.jpg";"image""1131";"0";"11";"Pictoetatl";"pictonormall.gif";"image""1132";"1131";"11";"Pictoetat3";"pictoeteintl.gif";"image""1500";"0";"12";"urleditohtml";"programmetv.html";"url";"1501" - "0" - "13""urlmetalistdtdStvdbml""menu01.xm1" - "url""1502";"1500";"12";"descriptionedito";"editorial description program Tv";"text"" 1503 ";" 1500 ";" 12 ";" date ";" update date of the Tv program editorial ";" date "" 1504 ";" 0 ";" 12 ";" urleditoxml ";" programmetv .xml ";" url "" 1505 ";" 0 ";" 12 ";" urleditogif ";" programmetv.gif ";" image "" 1506 ";" 1504 ";" 12 ";" descriptionxml ";" description according to the DTD of the enclosure area "Tvi.dtd""""text""1507";"1501";"13";"description";"Url of the pivotnavigation following DTD""STVDbml.dtd"" Element Application, ElementNode, Element Element, Element Attribute ";" text "

"1508" - "0";"13";"urlmetalistbis";"menubis0l.xml";"url""1509";"1508";"13";"description";"Pivoting url in a single format";"text""1510";"1505";"12";"description";"other type of presentation of the editorial part of the skin area 1 as a gif-encoded image";"text"

"4100";"0";"41";"date";"27/11/2001";"date""4111";"0";"41";"descriptionetatl";"Sports";"text""4112";"4111";"41";"descriptionetat2";"SPORTS";"text""4113";"4111";"41";"descriptionetat3";"sports";"text"

<Desc / Clms Page number 45>

"4122";"4121";"41";"scrollmount";"200";"pixels" "4123";"4121";"41";"scrolldelay";"10";"mS" "4124""4111""41""police""helvetica""caractere" "4125";"4111";"41";"taille";"16";"caractere" "4126";"4111";"41";"style";"gras";"stylecaractere" "4127";"4111";"41";"couleur";"0,0,0";"couleurRVB" "4128";"4111";"41";"background";"10,10,10";"couleurRVB" "4130";"413l";"41";"Pictoetat2";"pictozooml.jpg";"image" "4131";"0";"41";"Pictoetatl";"pictonormall.gif";"image" "4132";"4131";"41";"Pictoetat3";"pictoeteintl.gif";"image" "4500";"0";"42";"urleditohtml";"programmetv.html";"url" "4501" floit ;1143";"urlmetalistdtdStvdbml";"menuO4.xml";"url" "4502";"4500";"42";"descriptionedito";"description éditorial sport";"texte" "4503";"4500";"42";"date";"date de mise à jour de 1' éditorial sport";"date" "4504";"0";"42";"urleditoxml";"sport.xml";"url" "4505";"0";"42";"urleditogif";"sport.gif";"image" "4506";"4504";"42";"descriptionxml";"description suivant la DTD de l'habillage zone 1""Tv.dtd""";"texte" "4507";"4501";"42";"description";"Url du pivotnavigation suivant DTD ""STVDbml.dtd""Element Application, ElementNoeud, Element Element,Element Attribut";"texte"

"4508" "0";"42";"urlmetalistbis";"menubis04.xml";"url" "4509";"4508";"42";"description";"Url de pivotnavigation suivant un formatsimple";"texte" "4510";"4505";"42";"description"; "autre type de présentation de la partie éditoriale de la zone 1 sous forme d'une image codée gif";"texte" "4121";"0";"41";"position";"4i";"number"

"4122";"4121";"41";"scrollmount";"200";"pixels""4123";"4121";"41";"scrolldelay";"10";"mS""4124"" 4111 "" 41 "" font "" helvetica "" character "" 4125 ";" 4111 ";" 41 ";" size ";" 16 ";" character "" 4126 ";" 4111 ";" 41 ";" style ";" bold ";" stylecaracter "" 4127 ";" 4111 ";" 41 ";" color ";" 0,0,0 ";" RGB color "" 4128 ";" 4111 ";" 41 ";" background ";" 10,10,10 ";" RGB color "" 4130 ";" 413l ";" 41 ";" Pictoetat2 ";" pictozooml.jpg ";" image "" 4131 ";" 0 ";" 41 ";;"Pictoetatl";"pictonormall.gif";"image""4132";"4131";"41";"Pictoetat3";"pictoeteintl.gif";"image""4500";"0";"42";;"urleditohtml";"programmetv.html";"url""4501";floit; 1143 ";" urlmetalistdtdStvdbml ";" menuO4.xml ";" url "" 4502 ";" 4500 ";" 42 ";" descriptionedito ";"sports editorial description";"text""4503";"4500";"42";"date";"sports editorial update date";"date""4504";"0";"42""urleditoxml";"sport.xml";"url""4505";"0";"42";"urleditogif";"sport.gif";"image""4506";"4504";"42";"descriptionxml";"description according to the DTD of the skin area 1""Tv.dtd""";"text""4507";"45 01 ";" 42 ";" description ";" Pivoting url following DTD "" STVDbml.dtd "" Element Application, ElementNode, Element Element, Element Attribute ";" text "

"4508""0";"42";"urlmetalistbis";"menubis04.xml";"url""4509";"4508";"42";"description";"pivoting url in a single format";" text "" 4510 ";" 4505 ";" 42 ";" description ";"other type of presentation of the editorial part of zone 1 as a coded image gif""text"

<Desc / Clms Page number 46>

"7";"01";"1";"selectionportail";"niveau0l" "8" ;"01";"1";"retour";"niveau01" Table t~El "11" ;"1";"Lmaintenant";"contenerlogique" "12" ;"1";"Emaintenant";"contenerEdito"

"13";"1";"Nmaintenant";"contenerNavigation" "21";"2";"Lsuivant";"contenerlogique" "22";"2";"Esuivant";"contenerEdito" "23";"2";"Nsuivant";"contenerNavigation" "31";"3";"Lcesoir";"contenerlogique" "32";"3";"Ecesoir";"contenerEdito" "33";"3";"Ncesoir";"contenerNavigation" Table t Attr

"1100";"0";"11";"date";"27/11/2001";"texte" APPENDIX II TABLET TableT ~ Appl "1";"Metalistfrench" Table t ~ N "01";"0";"1";"Menunl";"level01""1";"01";"1";"now";"levelOl""10";"01";"1";"next";"level01""2";"01";"1";"caster";"level01""3";"01";" 1 ";" grid ";" level01 "" 4 ";" 01 ";" 1 ";" themes ";" level01 "" 5 ";" 01 ";" 1 ";" mosaic ";" level01 "" 6 ";01";"1";"cineatTV";"level01";

"7";"01";"1";"selectionportal";"level01""8";"01";"1";"return";"level01" Table t ~ El "11";"1";"Now","conenerlogic""12","1","Now","contenerEdito"

"13";"1";"Nnowtenant";"contenerNavigation""21";"2";"NextNext";"logical""22";"2";"Next";"contenerEdito""23";" 2 ";" Nsuivant ";" ContenerNavigation "" 31 ";" 3 ";" Lcesoir ";" Conenerlogic "" 32 ";" 3 ";" Ecesoir ";" ContenerEdito "" 33 ";" 3 ";" Ncesoir "ContenNavigation" table t Attr

"1100";"0","11","date","27/11/2001","text"

<Desc / Clms Page number 47>

"1111" 11011 "11" ;"descriptionetatl"; "Maintenant"; "texte" "1112";"1111";"11";"descriptionetat2";"Maintenant";"texte" "1113";"1111";"11";"descriptionetat3";"maintenant";"texte" "1121";"0";"11";"position";"1";"nombre" "1122";"1121";"11";"scrollmount";"200";"pixels" "1123";"1121";"11";"scrolldelay";"10";"ms" "1124";"1111";"11";"police";"helvetica";"caractere" "1125";"1111";"11";"taille";"16";"caractere" "1126";"1111";"11";"style";"gras";"stylecaractere" "1127";"1111";"11";"couleur";"0,0,0";"couleurRVB" "1128";"1111";"11";"background";"10,10,10";"couleurRVB" "1130";"113l";"11";"Pictoetat2";"pictozooml.jpg";"image" "1131";"0";"11";"Pictoetatl";"pictonormall.gif";"image" "1132";"1131";"11";"pictoetat3";"pictoeteintl.gif";"image" "1500" "0"-"12"-"urleditohtml" "maintenant.html" "url" "1501""0"-"13";"urlmetalistdtdStvdbml";"menu010.xml";"url " "1502";"1500";"12";"descriptionedito";"description éditorial maintenant";"texte" "1503";"1500";"12";"date";"date de mise à jour de l'édito maintenant";"date"

"1504"-"0"-"12";"urleditoxml";"maintenant.xml";"url" "1505";"0";"12";"urleditogif";"maintenant.gif";"image" "1506";"1504";"12";"descriptionxml";"description suivant le format pivot du pivotdisplay suivant DTD ""Tvi.dtd""" ;"texte" "1507";"1501";"13";"description";"Url du pivotnavigation suivant DTD ""STVDbml.dtd"" Element Application, ElementNoeud, Element Element,Element Attribut";"texte"

"1508" "0""13";"urlmetalistbis";"menubisOl0.xml";"url"

"1111" 11011 "11";"descriptionetatl";"Now";"text""1112";"1111";"11";"descriptionetat2";"now";"text""1113";"1111";"11";"descriptionetat3";"now";"text"" 1121 ";" 0 ";" 11 ";" position ";" 1 ";" number "" 1122 ";" 1121 ";" 11 ";" scrollmount ";" 200 ";" pixels "" 1123 ";" 1121 ";" 11 ";" scrolldelay ";" 10 ";" ms "" 1124 ";" 1111 ";" 11 ";" font ";" helvetica ";" character "" 1125 ";" 1111 ";" 11 ";" size ";" 16 ";" character "" 1126 ";" 1111 ";" 11 ";" style ";" bold ";" stylecaracter "" 1127 ";" 1111 ";" 11 ";" color ";" 0,0,0 ";" RGB color "" 1128 ";" 1111 ";" 11 ";" background ";" 10,10,10 ";" RGB color "" 1130 ";" 113l ";" 11 ";" Pictoetat2 ";" pictozooml.jpg ";" image "" 1131 ";" 0 ";" 11 ";" Pictoetatl ";" pictonormall.gif ";" image "" 1132 ";" 1131 ";" 11 ";" pictoetat3 ";" pictoeteintl.gif ";" image "" 1500 "" 0 "-" 12 "-" urleditohtml "" now.html "" url "" 1501 "" 0 "-" 13 ";" urlmetalistdtdStvdbml ";" menu010.xml ";" url "" 1502 ";" 1500 ";" 12 ";" descriptionedito ";" editorial description now ";" text "" 1503 ";" 1500 ";" 12 ";" date ";" update date of the editorial now ";" date "

"1504" - "0" - "12";"urleditoxml";"now.xml";"url""1505";"0";"12";"urleditogif";"now.gif";"image""1506";"1504";"12";"descriptionxml";"description following the pivot format of the pivotdisplay following DTD""Tvi.dtd""";"text""1507";"1501";"13";"description";"Url of the following DTD pivotnavigation""STVDbml.dtd""Element Application, ElementNode, Element Element, Element Attribute";"Text"

"1508""0""13";"urlmetalistbis";"menubisOl0.xml";"url";

<Desc / Clms Page number 48>

 "1509"; "1508"; "13"; "description"; "pivoting url in a single format"; "text" "1510"; "1505"; "12"; "description"; "other type of presentation of the editorial part in zone zl in the form of a coded image gif ";" text "

<Desc / Clms Page number 49>

 ANNEX III import java.sql. *; import java.io. *; import org.apache.xerces.dom. *; import org.apache.xerces.parsers. *; import java.util. *; import java.lang. *; import org.xml.sax. *; import org.log4j. *; import.TDF.SApplication.extractor.extractorException. *; import org.apache.xml.serialize. *; // START OF MODIFIABLE AREA @ OBJID @ 32810 @ 1703936116: 1616 @ N @ Descriptor @ Javadoc // END OF MODIFIABLE AREA @ OBJID @ 32810 @ 1703936116: 1616 @ E @ Descriptor @ Javadoc public class Extractor extends to TDF.SApplication. extractor.ExtractEventListener // START OF MODIFIABLE ZONE @ OBJID @ 33056 @ 1703936116: 1786 @ N @ Descriptor @ Javadoc / ** * STVDbFactory <BR> * Object encapsulating the connector * / // END OF MODIFIABLE ZONE @ OBJID @ 33056 @ 1703936116 : 1786 @ E @ Descriptor @ Javadoc protected en.TDF.SApplication.extractor.STVDbFactory STVDbFactoryPart; public.TDF.SApplication.extractor.STVDbFactory getSTVDbFactoryPart () {

<Desc / Clms Page number 50>

 return this.STVDbFactoryPart; public void setSTVDbFactoryPart (en.TDF.SApplication.extractor.STVDbFactory value) this.STVDbFactoryPart = value; } int public cardSTVDbFactoryPart () {if (this.STVDbFactoryPart == null) return 0; else return 1; // START OF MODIFIABLE ZONE @ OBJID @ 36418 @ 1703936116: 3271 @ N @ Descriptor @ Javadoc / ** * Output document in STVDbML format * / // END OF MODIFIABLE ZONE @ OBJID @ 36418 @ 1703936116: 3271 @ E @ Descriptor @Javadoc protected static org.apache.xerces.dom.DocumentImpl STVDbDocPart; public org.apache.xerces.dom.DocumentImpl getSTVDbDocPart () {return this.STVDbDocPart; } public void setSTVDbDocPart (org.apache.xerces.dom.DocumentImpl value) this.STVDbDocPart = value; public int cardSTVDbDocPart () if (this.STVDbDocPart == null) return 0; else return 1;

<Desc / Clms Page number 51>

// START OF MODIFIABLE AREA @ OBJID @ 33137 @ 1703936116: 1827 @ N @ Descriptor @ Javadoc / ** <B> EExtractEventListener </ B> * @param evt ExtractEvent caught * / // END OF MODIFIABLE AREA @ OBJID @ 33137 @ 1703936116: 1827 @ E @ Descriptor @ Javadoc public void CatchEvent (en.TDF.SApplication.extractor.ExtractEvent evt) {// START OF MODIFIABLE AREA @ OBJID @ 33154 @ 1703936116: 1830 @ T // Start Trace cat.info (" Event atrappe by an object of class "+ this.getClass (). GetName ()); // End Trace try
Class fact = Class.forName (evt.classSTVDbFactory);
STVDbFactoryPart = (STVDbFactory) fact.newInstance ();
STVDbFactoryPart.setUri (evt.srcData); // Start Trace cat.debug (IISTVDbFactory cree "); cat.debug (" class. "+ Fact.getName ()); cat.debug (" Uri. "+ STVDbFactoryPart.getUri ()); // End Trace

<Desc / Clms Page number 52>

} catch (java.lang.ClassNotFoundException e) cat.error (e.toString ()); System.out.println (e.ToString ()); System.exit (l); } catch (java.lang.InstantiationException e) cat.error (e.toString ());
System.out.println (e.toString ());
System. exit (1); catch (java.lang.IllegalAccessException e) cat.error (e.toString ()); System.out.println (e.ToString ()); System.exit (l); } try {// Start Trace cat.info ("Starting the creation of a document"); // End Trace
STVDbDocPart = STVDbFactoryPart.CreateDoc (evt.srcData); catch (DocValideException e)

<Desc / Clms Page number 53>

cat.error (e.ToString ()); System.out.println (e.ToString ()); System. exit (1); try cat.info ("Valid document"); cat.info ("Serialization of the document");
OutputFormat format = new OutputFormat (); format.setEncoding ( "ISO-8859-1"); format.setIndenting (true); format.setIndent (100); format.setLineSeparator ( "\ n"); format.setLineWidth (O); format.setMethod (Method.FOP);
XMLSerializer serialiser = new XMLSerializer (new FileOutputStream (evt.cibleData), format); serialiser.serialize (STVDbDocPart); cat.info ("Serialized Document"); catch (IOException e) {System.out.println (e.toString ()); } // END OF MODIFIABLE AREA @ OBJID @ 33154 @ 1703936116: 1830 @ E}

<Desc / Clms Page number 54>

APPENDIX IV <? Xml version = "1.0" encoding = "ISO-8859-1"?><! - edited with XML Spy v3.0.7 NT (http://www.xmlspy.com) by Yves Hervet (TDF CCETT PROGRAM) -><! ELEMENT Application (Node +, Element * <! ATTLIST Application
ID ~ CDATA Application #REQUIRED name CDATA #IMPLIED><! ELEMENT Node (Element Node) *><! ATTLIST Node
ID ~ CDATA Node #REQUIRED ID ~ Father CDATA #REQUIRED
ID ~ CDATA Application #REQUIRED name CDATA #IMPLIED
CDATA Level #REQUIRED><! ELEMENT Element (Attribute + <! ATTLIST Element
ID ~ Element CDATA #REQUIRED
ID ~ CDATA Node #REQUIRED
ClassElement CDATA #REQUIRED name CDATA #IMPLIED><! ELEMENT Attribute (Value? Attribute + <! ATTLIST Attribute
ID ~ Attr CDATA #REQUIRED
ID Father CDATA #IMPLIED
ID Element CDATA #IMPLIED
Type CDATA #REQUIRED name CDATA #REQUIRED

<Desc / Clms Page number 55>

 value CDATA #IMPLIED> <! ELEMENT Value (#PCDATA)>

<Desc / Clms Page number 56>

<Attribut ID Attr="1100" ID Element="11" ID Pere="0" Name="date" Type="date"> <Valeur> 27/11/2001 </Valeur> </Attribut> <Attribut ID~Attr="1121" ID~Element="11" ID~Pere="0" Name="position" Type="nombre"> <Valeur> </Valeur> <Attribut ID~Attr="1122" ID~Element="ll" ID~Pere="1121" Name="scrollmount"Type="pixels"> <Valeur> 200 </Valeur> </Attribut> <Attribut ID~Attr="1123" ID~Element="11" ID~Pere="1121" Name="scrolldelay" Type="ms"> <Valeur> 10 </Valeur> </Attribut> </Attribut> <Attribut ID~Attr="llll" ID~Element="ll" ID~Pere="0" Name="descriptionetatl" Type="texte"> <Valeur> Programmes TV </Valeur> <Attribut ID~Attr="1124" ID~Element="ll" ID~Pere="1111" Name="police" Type="caractere"> <Valeur> helvetica </Valeur> </Attribut> <Attribut ID~Attr="1125" ID~Element="ll" ID Pere="1111" Name="taille" Type="caractere"> <Valeur> 16 </Valeur> </Attribut> <Attribut ID~Attr="1126" ID~Element="ll" ID~Pere="llll" Name="style" Type="stylecaractere"> APPENDIX V MenuO.xml <? Xml version = "1.0" encoding = "ISO-8859-1"?><Application ID ~ Application = "l" Name = "Metalistfrench"><ID Node ~ Application = "l" ID ~ Node = "01" ID ~ Father = "0" Name = "MenuO" Level = "level0"><Node ID ~ Application = "1" ID ~ Node = "l" ID ~ Father = "01" Name = "ProgramTV "Level =" level0 "><Element ClassElement =" logical "ID ~ Element =" ll "ID ~ Node =" l "Name =" Ltv ">

<Attribute ID Attribute = "1100" Element ID = "11" Parent ID = "0" Name = "date" Type = "date"><Value> 27/11/2001 </ Value></Attribute><Attribute ID ~ Attr = "1121" ID ~ Element = "11" ID ~ Parent = "0" Name = "position" Type = "number"><Value></Value><Attribute ID ~ Attr = "1122" ID ~ Element = "ll" ID ~ Pere = "1121" Name = "scrollmount" Type = "pixels"><Value> 200 </ Value></Attribute><Attribute ID ~ Attr = "1123" ID ~ Element = "11" ID ~ Pere = "1121" Name = "scrolldelay" Type = "ms"><Value> 10 </ Value></Attribute></Attribute><ID Attribute ~ Attr = "llll" ID ~ Element = "ll" ID ~ Pere = "0" Name = "descriptionetatl" Type = "text"><Value> TV Programs </ Value><ID Attribute ~ Attr = "1124" ID ~ Element = "ll" ID ~ Father = "1111" Name = "font" Type = "character"><Value> helvetica </ Value></Attribute><Attribute ID ~ Attr = "1125" ID ~ Element = "ll" ID Pere = "1111" Name = "size" Type = "character"><Value> 16 </ Value></Attribute><Attribute ID ~ Attr = "1126" ID ~ Element = "ll" ID ~ Father = "llll" Name = "style" Type = "stylecaracter ">

<Desc / Clms Page number 57>

 <Value> bold </ Value> </ Attribute> <Attribute ID ~ Attr = "1127" ID ~ Element = "ll" ID ~ Father = "llll" Name = "color" Type = "colorRGB"> <Value> 0 , 0,0 </ Value> </ Attribute> <Attr ID Attribute = "1128" ID ~ Element = "ll" ID ~ Parent = "llll" Name = "background" Type = "colorRGB"> <Value> 10, 10,10 </ Value> </ Attribute> <ID Attribute ~ Attr = "1112" ID ~ Element = "ll" ID ~ Pere = "llll" Name = "descriptionetat2" Type = "text"> <Value> TV PROGRAMS </ Value> </ Attribute> <Attribute ID ~ Attr = "1113" ID ~ Element = "ll" ID ~ Pere = "llll" Name = "descriptionetat3" Type = "text"> <Value> TV programs </ Value > </ Attribute> </ Attribute> <Attribute ID ~ Attr = "1131" ID ~ Element = "11" ID ~ Parent = "0" Name = "Pictoetatl" Type = "image"> <Value> pictonormall.gif < / Value> <ID Attribute ~ Attr = "1130" ID ~ Element = "ll" ID ~ Parent = "1131" Name = "Pictoetat2" Type = "image"> <Value> pictozooml.jpg </ Value> </ Attribute > <Attribute ID ~ Attr = "1132" ID ~ Element = "ll" Pere ID = "1131" Name = "Pictoetat3" Type = "image"> <Value> pictoeteintl.gif </ Value> </ Attribute> </ Attribute> </ El > <Element ClassElement = "contenernavigation" ID ~ Element = "13" ID ~ Node = "l" Name = "Ntv"> <ID Attr Attribute = "1508" ID ~ Element = "13" ID ~ Pere = "0 "Name =" urlmetalistbis "Type =" url "> <Value> menubisOl.xml </ Value> <ID Attribute ~ Attr =" 1509 "ID ~ Element =" 13 "ID ~ Pere =" 1508 "Name =" description " Type = "text"> <Value> Url of pivotnavigation following a simple format </ Value> </ Attribute>

<Desc / Clms Page number 58>

 APPENDIX VI MenuOl.xml <? Xml version = "1.0" encoding = "ISO-8859-1"?> <Application ID ~ Application = "l" Name = "Metalistfrench"> <ID Node ~ Application = "l" ID ~ Node = "01" ID ~ Father = "O" Name = "Menunl" Level = "level0l"> <Node ID ~ Application = "l" ID ~ Node = "l" ID ~ Father = "Ol" Name = "now "Level =" level0l "> <Element ClassElement =" logical "ID ~ Element =" ll "ID ~ Node =" 1 "Name =" Now "> <Attr Attribute ID =" 1100 "ID ~ Element =" ll "ID ~ Pere = "0" Name = "date" Type = "text"> <Value> 27/11/2001 </ Value> </ Attribute> <Attribute ID ~ Attr = "1121" ID ~ Element = "ll" ID ~ Pere = "O" Name = "position" Type = "number"> <Value> </ Value> <ID Attribute ~ Attr = "1122" ID ~ Element = "ll" ID ~ Father = "1121" Name = " scrollmount "Type =" pixels "> <Value> 200 </ Value> </ Attribute> <Attr Attribute ID =" 1123 "ID ~ Element =" ll "Pere ID =" 1121 "Name =" scrolldelay "Type =" ms "> <Value> 10 </ Value> </ Attribute> </ Attribute> <ID Attribute ~ Attr =" llll "ID ~ Element =" ll "ID ~ Pere =" 0 "Name =" descriptionetatl "Type =" text "> <Value> Now </ Value> <ID Attribute ~ Attr = "1124" ID ~ Element = "ll" ID ~ Pere = "llll" Name = "font" Type = "character"> <Value> helvetica </ Value> </ Attribute> <Attribute ID ~ Attr = " 1125 "ID ~ Element =" ll "ID ~ Pere =" llll "Name =" size "Type =" character "> <Value> 16 </ Value> </ Attribute> <Attribute ID ~ Attr =" 1126 "ID ~ Element = "ll" ID = Pere = "llll" Name = "style" Type = "stylecaractere"> <Value> bold </ Value> </ Attribute>

<Desc / Clms Page number 59>

 <Attribute ID Attribute = "1127" ID ~ Element = "ll" ID ~ Father = "1111" Name = "color" Type = "colorRGB"> <Value> 0,0,0 </ Value> </ Attribute> < Attribute ID Attr = "1128" ID ~ Element = "ll" ID ~ Father = "1111" Name = "background" Type = "colorRGB"> <Value> 10,10,10 </ Value> </ Attribute> <Attribute ID Attr = "1112" ID ~ Element = "11" ID ~ Pere = "llll" Name = "descriptionetat2" Type = "text"> <Value> Now </ Value> </ Attribute> <Attr ID Attribute = "1113 "ID ~ Element =" ll "ID ~ Pere =" llll "Name =" descriptionetat3 "Type =" text "> <Value> now </ Value> </ Attribute> </ Attribute> <Attribute ID ~ Attr =" 1131 "ID ~ Element =" ll "ID ~ Parent =" 0 "Name =" Pictoetatl "Type =" image "> <Value> pictonormall.gif </ Value> <Attribute ID Attr =" 1130 "ID ~ Element =" ll "ID Pere =" 1131 "Name =" Pictoetat2 "Type =" image "> <Value> pictozooml.jpg </ Value> </ Attribute> <Attr Attribute ID =" 1132 "ID ~ Element =" 11 "ID Pere = "1131" Name = "pictoetat3" Type = "image"> <Value> pictoeteintl.gif </ Value> </ Attribute> </ Attribute> </ Element> <Element ClassElement = "contenerNavigation" ID ~ Element = "13" ID ~ Node = "l" Name = "NNow"> <Attr Attribute ID = "1508" ID Element = "13" ID ~ Pere = "0" Name = "urlmetalistbis" Type = "url "> <Value> menubisi010.xml </ Value> <ID Attribute ~ Attr =" 1509 "Element ID =" 13 "Pere ID =" 1508 "Name =" description "Type =" text "> <Value> Pivoting Url following a simple format </ Value> </ Attribute>

<Desc / Clms Page number 60>

...................................................... -> <!-- Habillage graphique zl pour télévision interactive--> <!-- Version 1. 3.2 --> <!--

...................................................... -> <!-- CHANGELOG--> <!-- 16. 01.2001 ver 1.3.2 - Removed ID and IDREF for CDATA - Added an optional View for Page content - Added Property* in Object --> <!-- 29. 01.2001 ver 1.3.1 - Added page attribute on the event~hook --> <!-- 14. 12.2000 ver. 1.3 - Moved the property of an object in the object~property - Added a META tag - Added property tags in tvi, page, object, state tags in order to further customize and extend the format. APPENDIX VII <? Xml version = "1.0" encoding = "ISO-8859-1"?><! -

.................................................. .... -><! - Zl graphics for interactive TV -><! - Version 1. 3.2 -><! -

.................................................. .... -><! - CHANGELOG -><! - 16. 01.2001 ver 1.3.2 - Removed ID and IDREF for CDATA - Added an optional View for Page content - Added Property * in Object ->< ! - 01.01.2001 ver 1.3.1 - Added page attribute on the event ~ hook -><! - 14. 12.2000 ver. 1.3 - Moved the property of an object in the object ~ property - Added a META tag - Added property tags in tvi, page, object, state tags in order to further customize and extend the format.

 - Enriched the page and tvi tags.

 - Added meta information - Added tvi and page level event ~ hooks -> <! - 11. 12.2000 ver. 1. 2 - Minor changes (new entities, internal ~ event ~ source removed, name attribute become attribute, on object default-> default-state in IMPLIED form) ->

<Desc / Clms Page number 61>

<! - 30.11.2000 ver. 1. 1 - added the concept of multiple states for an object, internai events. Renamed and simplified some tags. -><! -
DEFINITIONS ENTITY: DATA Type <! - possible states of an object -><! ENTITY% gstate, (normal selected higlighted hidden) "><! - data source definition -><! ENTITY% dataSource" CDATA "><! - action types definition (onLoader ...) -><! ENTITY% actionType "CDATA"><! - action source definition (Up, Down ...) -><! ENTITY% actionSource "CDATA "><! - DEFINITIONS ENTITY: attributes -><! ENTITY% stdAttrs" id CDATA #REQUIRED "><! - structure definition ->

<Desc / Clms Page number 62>

 <! ELEMENT tvi (meta *, property *, page *, event ~ hook *)> <! ATTLIST tvi background ~ type CDATA #IMPLIED background ~ source% dataSource; #IMPLIED <! ELEMENT meta title> CDATA #IMPLIED description CDATA #IMPLIED author CDATA #IMPLIED date CDATA #IMPLIED copyright CDATA #IMPLIED version CDATA #IMPLIED pragma CDATA #IMPLIED <! ELEMENT property ANY> <! ATTLIST property name CDATA #IMPLIED <! ELEMENT page (property *, object *, state *, view?)> <! ATTLIST page% stdAttrs; name CDATA #IMPLIED background ~ type CDATA #IMPLIED background ~ source% dataSource; #IMPLIED default ~ state CDATA #IMPLIED <! ATTLIST object% stdAttrs; type CDATA #REQUIRED default ~ state% gstate; #IMPLIED pos ~ x CDATA #IMPLIED pos ~ CDATA #IMPLIED width CDATA #IMPLIED height CDATA #IMPLIED

<Desc / Clms Page number 63>

 <! ELEMENT object ~ state (property *)> <! ATTLIST object ~ state state ~ name% gstate; #REQUIRED source% dataSource; #IMPLIED <! ELEMENT state (property *, objectitem *, event ~ hook *)> <! ATTLIST state% stdAttrs; <! ELEMENT objectitem EMPTY> <! ATTLIST objectitem name CDATA #REQUIRED state% gstate; #REQUIRED <! ELEMENT event hook EMPTY> <! ATTLIST event source hook% actionSource; #REQUIRED type% actionType; #REQUIRED target CDATA #REQUIRED CDATA page #REQUIRED <! ELEMENT view (tr * <! ATTLIST view rows CDATA #REQUIRED pass CDATA #REQUIRED <! ELEMENT tr (td *)> <! ELEMENT td (objectref @ view <! - Definition of the objectref -> <! ELEMENT objectref EMPTY> <! ATTLIST objectref object CDATA #IMPLIED

<Desc / Clms Page number 64>

 APPENDIX VIII <? Xml version = "1.0" encoding = "ISO-8859-1"?> <! DOCTYPE tvi SYSTEM 'tvi.dtd'> <tvi> <meta title = "Lighthouse West May 2001" description = "AFP Application" author = "Yves Hervet" copyright = "TDF CCETT" version = "" pragma = "" /> <page name = "page" id = "page" background ~ type = "image" background ~ source = "fond2.gif" default ~ state = "null"> <object type = "tvi.bean.TviLabel" id = "labell" pos ~ x = "253 pos ~ y =" 10 "width =" 226 "height =" 52 "> <property name = "Scrollable"> true </ property> <property name = "Opaque"> false </ property> <property name = "Name"> labell </ property> <property name = "Text"> Afp page </ property> <property name = "Foreground"> 255,255,255 </ property> <property name = "Font"> Arial, 2,32 </ property> </ object> <object type = "tvi.bean.TviImage" id = " Afp "pos ~ x =" 32 "pos ~ y =" 80 "width =" 69 "height =" 44 "> <object ~ state state ~ name =" normal "source =" logoafp.gif "/> <property name = "Name"> Afp </ property> </ object> <object type = "tvi.bean.TviLabel" id = "obj486" pos ~ x = "561" pos ~ y = "18" width = "60" height = "30"> <property name = " Name "> obj486 </ property> <property name =" Opaque "> true </ property> <property name =" Scrollable "> true </ property> <property name =" Font "> Arial Narrow, 3.20 </ property>

<Desc / Clms Page number 65>

 <property name = "Foreground"> 192,192,192 </ property> <property name = "BorderColor"> 128,128,128 </ property> <property name = "BorderWidth"> 4 </ property> <property name = "Text"> Page l < / property> </ object> <object type = "tvi.bean.TviLabel" id = "followingeladepeche" pos ~ x = "164" pos ~ y = "441" width = "51" height = "15"> <property name = "Opaque"> true </ property> <property name = "Scrollable"> true </ property> <property name = "Name"> consequenteladepeche </ property> <property name = "Text"> MORE </ property> <property name = "Font"> Arial, 1.14 </ object> <object type = "tvi.bean.Text" id = "text" default ~ state = "normal" pos ~ x = "329 "pos ~ y =" 229 "width =" 224 "height =" 190 "> <object ~ state state ~ name =" normal "source =" Recent photo of journalist Johanne Sutton, senior reporter at RFI, killed on November 11 on the north-eastern front of Afghanistan in an ambush of the Taliban.

"/>

<Desc / Clms Page number 66>

 APPENDIX IX <MENU> <SECTION> <ID> O </ ID> <NUMBER> 0 </ NUMBER> <TITLE> TV Programs </ TITLE> <DESCRIPTION> Programmatic description of the @TV portal </ DESCRIPTION> <URL> programmetv .html </ URL> /> <DATE> November 16, 2001 </ DATE> </ SECTION> <HEADING> <ID> 1 </ ID> <NUMBER> 1 </ NUMERO> <TITLE> Radio Programs </ TITLE> <DESCRIPTION> description of the radio programs of the portal @TV </ DESCRIPTION> <URL> programsradio.html </ URL> /> <DATE> November 16, 2001 </ DATE> </ RUBRIQUE> <SECTION> <ID> 2 </ ID> <NUMBER> 2 </ NUMERO> <TITLE> Actalities </ TITLE> <DESCRIPTION> Access the @TV news portal html pages </ DESCRIPTION> <URL> news.html </ URL> /> <DATE > 16 November 2001 </ DATE> </ ITEM> <SECTION> <ID> 3 </ ID>

<Desc / Clms Page number 67>

 <NUMBER> 3 </ NUMERO> <TITLE> sports </ TITLE> <DESCRIPTION> Access to the sports pages of the portal @TV </ DESCRIPTION> <URL> sports.html </ URL> /> <DATE> November 16, 2001 < / DATE> </ RUBRIC> <RUBRIC> <ID> 4 </ ID> <NUMBER> 4 </ NUMERO> <TITLE> Your Magazines </ TITLE> <DESCRIPTION> access to the first page of your @TV portal magazines </ DESCRIPTION> <URL> magazine.html </ URL> /> <DATE> November 16, 2001 </ DATE> </ RUBRIQUE> <HEADING> <ID> 5 </ ID> <NUMBER> 5 </ NUMERO> < TITLE> vielocale </ TITRE> <DESCRIPTION> access to the first page of your @TV portal magazines </ DESCRIPTION> <URL> local.html </ URL> /> <DATE> November 16, 2001 </ DATE> </ SECTION> <SECTION> <ID> 6 </ ID> <NUMBER> 6 </ NUMERO> <TITLE> practical life </ TITLE> <DESCRIPTION> access to the first page of your @TV portal magazines </ DESCRIPTION>

<Desc / Clms Page number 68>

 <URL> pratique.html </ URL> /> <DATE> November 16, 2001 </ DATE> </ SECTION> <HEADING> <ID> 7 </ ID> <NUMBER> 7 </ NUMERO> <TITLE> practical life </ TITRE> <DESCRIPTION> access to the first page of your @TV portal magazines </ DESCRIPTION> <URL> pratique.html </ URL> /> <DATE> November 16, 2001 </ DATE> </ RUBRIQUE> < SECTION> <ID> 8 </ ID> <NUMBER> 8 </ NUMERO> <TITLE> emails </ TITLE> <DESCRIPTION> access to the first page of the email service </ DESCRIPTION> <URL> email.html < / URL> /> <DATE> November 16, 2001 </ DATE> </ ITEM> <ITEM> <ID> 9 </ ID> <NUMBER> 9 </ NUMERO> <TITLE> internet </ TITLE> <DESCRIPTION> access to the wanadoo portal </ DESCRIPTION> <URL> http://www.voila.com/ </ URL> /> <DATE> November 16, 2001 </ DATE> </ ITEM> <ITEM>

<Desc / Clms Page number 69>

 <ID> 10 </ ID> <NUMBER> 10 </ NUMERO> <TITLE> Exit </ TITLE> <DESCRIPTION> How to leave the @TV portal if there is no url is the last url is saved </ DESCRIPTION> <URL> / </ URL> /> <DATE> November 16, 2001 </ DATE> </ SECTION> </ MENU>

Claims (28)

CLAIMS 1. A method for producing interactive applications, at least part of the interactive applications, distributed on a digital transmission channel, being intended to be installed on an execution platform to implement a succession of thematic sections. in the form of a menu, in which: - data tables (T1, T2, T3, T4) are prepared comprising at least, for each current item of a menu, an identifier of a node corresponding to this current item. and an identifier of a parent node corresponding to a parent heading of this current topic in the menu, and generating, from the data of the tables, a list comprising at least descriptive elements of the nodes and hierarchical according to a logical tree whose nodes are positioned according to said identifiers of nodes. 2. Method according to claim 1, in which a main list is generated comprising several sub-lists hierarchically nested according to said logical tree and comprising, for each node, respectively descriptive elements: of the position of this node in the logical tree, - information containers of a section corresponding to this node, - and attributes associated with each information container, <Desc / Clms Page number 71>  and wherein the data tables comprise: - a first data table relating to node positions in the logical tree (t ~ N), comprising for each n # ud at least: # the identifier of this n #ud (ID ~ N), # the identifier of the n # ud father of this node (ID ~ PN), # and a name assigned to this node #, - a second table of data relative to containers of information (t ~ El), comprising for each container at least: # an identifier of this container (ID ~ E1), # the identifier of the node # which is associated with this container (ID ~ N), # and a name of container (Name), and a third table of data relating to attributes associated with information containers (t ~ Attr), comprising for each attribute at least: # an identifier of this attribute (ID ~ Attr), # the identifier of the container with which the attribute (ID ~ E1) is associated, # and a name of the attribute (Name). 3. The method according to claim 2, wherein: said main list further comprises descriptive elements of interactive applications in which one or more nodes intervene, said data tables comprise a fourth data table relating to the interactive applications. (t ~ Appl), including for each interactive application: # an identifier of this interactive application (ID ~ Appl), <Desc / Clms Page number 72>  # and a name assigned to this interactive application (Name), - and the first data table further comprises, for each node, the identifier of the interactive application in which a heading associated with this node. intervenes (ID ~ Appl). 4. The method of claim 2, wherein a set of first, second and third tables of data by interactive application is provided. 5. Method according to one of claims 3 and 4, wherein, each interactive application being able to extend over several successive levels of items: - the first data table further comprises, for each n # ud, data relating to a level name in which this node (Level) intervenes, and the hierarchical list further comprises descriptive elements of levels of nodes. 6. Method according to one of claims 2 to 5, wherein: the information containers are listed by thematic classes (classEl), - the second table (t ~ El) further comprises data relating to a class name thematic to which each information container belongs, - and the hierarchical list further comprises descriptive elements of classes of containers. <Desc / Clms Page number 73> 7. Method according to one of claims 2 to 6, wherein: the attributes are classified by types of attributes selected from a set comprising at least: # a string of alpha-numeric characters (txt), # a path d access (URL) to a graphical and / or audio skin component, # and an attribute aggregate (GrpAttr), - the third table further includes data relating to an attribute type (Type), - and the hierarchical list further includes descriptive elements of attribute types. The method according to one of claims 2 to 7, wherein the hierarchical list comprises, on the one hand, descriptive elements of attribute names and, on the other hand, descriptive elements of attribute values, and the third table further includes data relating to a value of each attribute (Value). The method according to one of claims 2 to 8, wherein the declarative sub-list comprising the attribute descriptive elements comprises secondary sub-lists of attribute descriptive elements, nested according to a logical tree of nodes. of attributes, and the third table (t ~ Attr) further comprises data relating to an identifier of a father attribute of each attribute (ID ~ PAttr). 10. Method according to one of the preceding claims, wherein: <Desc / Clms Page number 74>  an information data file (36) is furthermore prepared for the content of items and / or the graphic and / or sound wrapping of items, and said list of items further includes descriptions of paths to data from that file. The method of claim 10, wherein said hierarchical list further comprises at least one path to a secondary list comprising paths to data in said folder. 12. Method according to one of claims 10 and 11, wherein, each interactive application being capable of extending over several successive levels of items (Level 0, Level 1, Level 2), a data file of information (36) and generates a hierarchical list including paths to data in said folder for each level of an interactive application. 13. A system for producing interactive applications, comprising: a headend (2, AS) arranged to distribute signals representative of interactive applications on a digital transmission channel, - an execution platform (1, 11, ECR, AT) arranged to receive said signals and suitable for installing said interactive applications to implement a succession of thematic topics in the form of a menu, characterized in that the headend comprises: <Desc / Clms Page number 75>  a data table editor (Tl, T2, T3, T4) comprising at least, for each current item of a menu, an identifier of a node corresponding to this current item and an identifier of a n # ud parent corresponding to a parent heading of this current item in the menu, and a formatting automaton (AFT) capable of generating, from the data of the tables, a list comprising at least descriptive elements of the nodes and ranked according to a logical tree whose nodes are positioned according to said node identifiers. 14. System according to claim 13, characterized in that the headend is arranged to send to the execution platform the data of said tables, as well as the formatting automaton, for the purpose of generating said hierarchical list at the level of the execution platform. 15. System according to claim 14, characterized in that the execution platform comprises means for updating the data of said tables to generate menus according to a user profile of the terminal (32). 16. System according to claim 13, characterized in that the headend is arranged to send said hierarchical list to the execution platform. 17. System according to claim 16, characterized in that the headend includes means for updating the data tables and is arranged to send to the execution platform a hierarchical list, set to <Desc / Clms Page number 76>  day depending on specificities of said terminal selected from a set comprising at least one memory capacity of the terminal, a conditioned access to predetermined menu items and conditioned access to predetermined interactive applications. 18. System according to one of claims 15 and 17, characterized in that the data of the tables are initially encoded as a text file script, and in that the updating means comprise a text editor. to add and / or delete and / or modify topics and / or contents of menu items. 19. System according to one of claims 13 to 18, characterized in that the execution platform comprises means for interpreting (33) said list to implement on the execution platform a hierarchical menu corresponding to the list. 20. System according to claim 19, characterized in that the headend is arranged to send to the execution platform a file (36) comprising data content information topics and / or graphic dressing and / or sound of items, in that said hierarchical list further comprises descriptions of paths to data of said folder, and in that said means of interpretation are arranged to read the access paths of said list and comprise in addition executable files (34) for <Desc / Clms Page number 77>  implement the content of each menu item on said execution platform, in correspondence of a graphic and / or sound dressing described in the hierarchical list. 21. System according to claim 20, characterized in that, each interactive application being capable of extending over several successive levels of items, the headend is arranged to send to the execution platform: a file containing data content information of items and / or graphic and / or sound wrapping of items, - a hierarchical list comprising descriptions of paths to data of said folder, or a set of data tables to generate such list, for each level of the interactive application (Level 0, Level 1, Level 2). 22. Data structure for developing lists of descriptive items of topics and / or topic containers of a menu of interactive applications to be installed on an execution platform for the implementation of a succession of menu items in the form of a menu, characterized in that it comprises a succession of declarative tags (DTD) comprising at least: a declaration of nodes corresponding to the items, a declaration of items corresponding to the containers headings, <Desc / Clms Page number 78>  - and a declaration of attributes associated with the topic containers. 23. Data structure according to claim 22, characterized in that it further comprises: a first data table (t ~ N) relating to node positions in a logical tree representative of a menu tree; , comprising for each n # ud at least: # the identifier of this node (ID ~ N), # the identifier of the n # ud father of this node (ID ~ PN) # and a name assigned to this node (Name), - a second data table relating to information containers (t ~ El), comprising for each container at least.  # an identifier of this container (ID ~ E1), # the identifier of the n # ud with which this container is associated (ID ~ N), # and a name of container (Name), a third table of data relating to attributes associated with the information containers (t ~ Attr), comprising for each attribute at least: # an identifier of this attribute (ID ~ Attr), # the identifier of the container with which the attribute (ID ~ E1) is associated, # and a name of the attribute (Name), and data formatting means of said first, second and third tables for generating, under the control of said succession of declarative tags (DTD), a hierarchical list according to said logical tree and <Desc / Clms Page number 79>  comprising, for each node of the logical tree, respectively descriptive elements: of the position of this node in the logical tree, of information containers of a section corresponding to this node, and attributes associated with each information container. Data structure according to one of claims 22 and 23, characterized in that said succession of declarative tags is in the form of a document type definition file (DTD) according to a metalanguage (XML), and what said hierarchical list is in the form of a metafile (XML, HTML) intended to be read and interpreted on an execution platform to implement a menu tree corresponding to the logical tree of n #uds. 25. Data structure for developing lists of descriptive elements of section contents of a menu of interactive applications intended to be installed on an execution platform for the implementation of a succession of items thematic menu form, characterized in that it comprises a succession of declarative tags (DTD) including at least: - a declaration of an object as content of a topic (audio, video, text, ...) ) - a declaration of a state of the object (selected, selectable, hidden, ...), <Desc / Clms Page number 80>  a declaration of an interaction automaton capable of generating event / action pairs suitable for modifying the state of the object. 26. Data structure according to claim 25, characterized in that it further comprises: a media file (36) comprising: # editorial data of contents of sections, # files among a set comprising at least sound files , image files, video files, text files, text font files, - and means for formatting the data of the media folder to generate, under the control of said succession of declarative tags (DTD), at least a list (xml; html) comprising at least one description of a path to a file of said media folder and / or a description of a path to another list. Data structure according to claim 26, characterized in that said succession of declarative tags is in the form of a document type definition file (DTD) following a metalanguage (XML), and in that said list is in the form of a metafile (xml; html) intended to be read and interpreted on an execution platform to implement the content of at least one item on said execution platform, in correspondence data from the media folder. <Desc / Clms Page number 81> 28. Data structure according to one of claims 25 to 27, characterized in that said succession of declarative tags further comprises a declaration of a graphic organization of the object to edit in correspondence the content of the item on the platform execution.