EP2836922A1 - Documentation data file having detail levels - Google Patents

Abstract

The invention relates to a method for saving a documentation data file intended for being displayed on a screen, comprising the following steps: subdividing said documentation data into data blocks; associating a detail level with at least one data block; and saving said data block with a level marker relating to said associated detail level, said marker being intended for being compared with a desired detail level in order to display data on the screen.

Description

 Documentation data file with levels of detail

The present invention relates to the recording and display of documentation data of a documentation data file.

 Companies designing high-tech products that are complex in their implementation (eg computer software, high-performance computers, etc.) provide their customers and users of these products with one or more technical documentation, most often under electronic form (CD-ROM, DVD-ROM, USB key, or other).

 These documents are very detailed because the products in question can address both a broad spectrum of users, from the least qualified to the most experienced. This level of detail can, however, make these documentation difficult to use, especially when the level of detail does not match the level of technical knowledge of the reader.

 The inventors have thus highlighted a need for a new documentation file format making it possible to adapt the displayed content, in particular the level of detail of this content, to the user of the file.

 The present invention falls within this framework.

 A first aspect of the invention relates to a method of recording a documentation data file for display on a screen, comprising the following steps:

 subdivision of said documentation data into data blocks,

 associating a level of detail with at least one block of data, and

recording said data block with a level marker relative to said associated level of detail, said marker being intended to be compared to a desired level of detail for displaying the data on the screen. The method according to the present invention can be implemented by computer means, for example by means of word processing software.

 According to the present invention, it is possible, in the same file representing a document (with text, images or other), to have several versions of an element of the document with different levels of detail. This offers the possibility, when the document is edited on a screen, to choose a display level according to a desired level of detail.

 Thus, when a documentation relating, for example, to a complex product and addressed to a wide range of users, is created, it is possible to include several levels of detail. Each user, according to his technicality, can then choose a level of detail display.

 The method may further include a step of registering a link marker with said data block to make a documentation link with at least one other data block of the file.

 Thus, it is possible to link the different versions of an element of the document.

 For example, said link marker gives a level of detail associated with said at least one linked block.

 Thus, in addition to specifying the links between the different versions of the element, it is possible to know the level of detail of each version.

 It is thus possible to present to the user, for an element of the document, the different levels of detail available. It is also possible to choose from the available versions, the one most suitable for a specified display level to display the file data.

 For example, at least one of the level marker and the link marker is a metadata.

 Such a type of data is simple and effective to implement.

The documentation data may for example include text data, image data, or the like.

For example, the file is in XML (eXtended Markup Language) format. A second aspect of the invention relates to a method of displaying file documentation data, comprising the following steps of:

 comparing a level marker, in said file, relating to a level of detail associated with a data block of said file, at a detail level of display for displaying said block of data, and

 generating a data display signal of said block if said level marker corresponds to said level of display detail.

 The method can be implemented by computer means. The method may further comprise a step of determining, from a link marker with said data block, in said file, a documentation link with at least one other data block of the file.

 The method may further include a step of generating a display signal of said link.

 The method may further comprise a step of determining, from said link marker, a level of detail of said at least one other data block.

 The method may further include a step of generating a display signal of said level of detail of said at least one other data block.

 For example, the generated signals are sent to a display device such as a screen.

 For example, at least one of the level marker, the link marker, and the indicator is a metadata.

 For example, the file was saved according to the first aspect.

A third aspect of the invention relates to computer programs as well as computer program products and storage media for such programs and products, enabling the implementation of methods according to the first and / or second aspect of the invention. the invention, when the programs are stored in a memory of a documentation data file recording device or a documentation data display device and executed by a processor of such devices. A fourth aspect of the invention relates to a data recording medium having recorded data of the first aspect.

 For example, the data recording medium includes a first recording portion for storing a detail level marker relative to a data block associated with said first recording portion.

 For example again, the data recording medium comprises a second recording portion for storing a documentation link marker relating to a link between a data block associated with said second portion and at least one other data block.

 Said second portion of data may include a recording sub-portion for storing for each at least one other linked data block a level of detail mark.

 A fifth aspect of the invention relates to a device configured for implementing a method according to the first aspect. Such a device for recording a documentation data file intended for display on a screen comprises a processing unit configured to subdivide said documentation data into data blocks, associating a level of detail with at least one block of data. data, record said data block with a level marker relative to said associated level of detail, said marker being intended to be compared to a desired level of detail for displaying the data on the screen.

 The processing unit may further be configured to register a link marker with said data block to make a documentation link with at least one other data block of the file.

 The link marker may provide a level of detail associated with the at least one linked block.

 At least one of the level marker and the link marker can be a metadata.

 The documentation data may include text data, image data, or the like.

The file can be in XML (eXtended Markup Language) format. A sixth aspect of the invention relates to a device for implementing a method according to the second aspect. Such a file documentation data display device comprises a processing unit configured to determine a display detail level for displaying a data block of said file, comparing a level marker, in said file, relative at a level of detail associated with said data block at the determined display detail level, and generating a data display signal of said block if said level marker corresponds to said level of display detail.

 The processing unit may further be configured to determine, from a link marker with said data block, in said file, a documentation link with at least one other block of data in the file.

 The processing unit may further be configured to generate a display signal of said link.

 The processing unit may further be configured to determine, from said link marker, a level of detail of said at least one other data block.

 The processing unit may further be configured to generate a display signal of said level of detail of said at least one other data block.

 At least one of the level marker, the link marker and the indicator may be a metadata.

 For example, the file was recorded according to a method according to the first aspect.

 The objects according to the second, third, fourth, fifth and sixth aspects of the invention provide at least the same advantages as those provided by the method according to the first aspect. The devices may include means for implementing optional features mentioned for the first and second aspects in terms of method.

Other characteristics and advantages of the invention will appear on reading the present detailed description which follows, by way of non-limiting example, of the appendices 1 and 2 respectively illustrating a DTD grammar and a XML file according to embodiments, as well as appended figures among which:

 - Figures 1 and 2 illustrate display windows according to embodiments;

 FIG. 3 illustrates a data format according to one embodiment;

 FIGS. 4 and 5 are flow charts of steps implemented according to embodiments; and

 - Figure 6 schematically illustrates a device according to embodiments of the invention.

 In the following description, it is presented a new data format allowing a user to adjust the level of detail of the data he consults in an electronic file according to his needs. As a result, the user can display details for less familiar parts and display less detailed portions for parties with which they are more familiar.

 In general, this is a file format in which data (eg metadata) of "precision level" (or "detail") are recorded for each element constituting the document (for example, a chapter). , paragraph, figure, or other). This data can be specified by a user when saving the data file. For example, he chooses a number of possible levels of detail (one, two, three, or more) and then assigns to various elements of the document represented by the file one of these levels.

 When displaying (or viewing) the file, the level of detail data (for example, metadata) is interpreted to provide the user with the ability to view the different levels of detail available for that or that part of the document.

Several implementations of this display are possible. It is possible to consider the display of several windows arranged side by side with each displaying, for a document element, different levels of detail. In such an embodiment, a coordination between the windows is planned to display in a coordinated manner the same parts of the document but in different levels of detail. Alternatively or in combination, these windows are not presented simultaneously but open at the request of the user. Elements, for example on which it is possible to click, are presented to the user to indicate the possibility of opening a new window with a new level of detail.

 Figure 1 illustrates a viewing window according to one embodiment.

 The window 100 according to FIG. 1 has two sub-windows 101 and 102.

 The sub-window 101 is the main viewing window in which the document is displayed to the user according to a predefined level of detail. For example, when opening the file, the user is asked to specify the level of detail desired to display the data. For example again, there is a default level of detail.

 The user can then consult the document by scrolling the window with a cursor 103.

 A frame 104 is presented to the user to change the level of detail relative to an element of the document. For example, this frame is displayed when the user passes a cursor (a "mouse") on the element in question. In the illustration according to Figure 1, it is assumed that the user has selected the element "text2" (it is for example text, an image or other), for example by placing a mouse on this element. The frame 104 is then displayed and indicates three increasing levels of detail available for this element (DetaiM, Detail2 and Detail3).

 The sub-window 102 is the detail window for displaying a user selected item according to the level of detail selected by the user.

In the example of Figure 1, the user has selected the element "text2". It is assumed that in frame 104, it has selected the level of detail "Detail2". Are then displayed in the sub-window 102 data "Text2_detail2" (text, images, or other) detailing the element "text2". FIG. 2 illustrates another exemplary embodiment of a viewing window.

 The window 200 according to the example of Figure 2 simultaneously displays the different levels of detail available for the file. For the sake of clarity, only the "text2" element is detailed in this viewing window.

 In frame 201, the document displayed in the sub-window 101 of FIG.

 A frame 202, adjacent to the frame 201, displays the document with the detail level "DetaiH" for the "Text2" element. Thus, instead of the element "Text2", there is the element "Text2_detail1" which details the element "Text2".

 A frame 203, adjacent to the frame 202, displays the document with the level of detail "Detail2" for the item "Text2". Thus, in place of the "Text2" element, there is the "Text2_detail2" element which details the "Text2" element, more than the "Text2_detail1" element.

 It is possible to access another frame (not shown) adjacent to frame 203 using a cursor 204.

 This frame (not shown) displays the document with a level of detail "Detail3" for the "Text2" element. Thus, in place of the "Text2" element, this frame displays the "Text2_detail3" element which details the "Text2" element, more than the "Text2_detail2" element.

 Figure 3 illustrates a data structure for representing a file for a display as discussed above.

 This data structure can be recorded on a data medium such as a CD-ROM, a DVD-ROM, a USB key, a hard disk, or the like.

 The data structure 300 of Figure 3 represents a portion of a documentation data file. A file may comprise several elements 300 as discussed with reference to FIG.

A portion of data 301 stores an identification of a data block. For example, this data block is relative to an element of a document represented by the file to which the block belongs. By taking back the illustrations of Figures 1 and 2, this block may for example represent an element such as "Text2". It can be text, image, spreadsheet or other data. The identification of the data block is for example a number coded in binary or hexadecimal.

 A portion of data 302 stores a documentation link marker of the data block with other data blocks of the file to which the block belongs. The link marker includes one or more data sub-portions 303, 304 and 305 identifying data blocks related to the identified block in the data portion 301. The link marker further includes one or more data sub-portions 306, 307 and 308 respectively associated with the sub-portions 303, 304 and 305, identifying a level of detail associated with the linked data blocks.

 Referring again to the example of FIGS. 1 and 2, the data portion 301 can identify the "Text2" element, and the data portions 303, 304 and 305 can respectively identify the "Text2_detail1", "Text2_detail2" and "Text2_detail3" elements. ". Portions 306, 307 and 308 then respectively identify the levels of detail "DetaiH", "Detail2" and "Detail3".

 A portion of data 309 stores a level of detail associated with the data block identified in portion 301. This is for example a level coded in binary or hexadecimal.

 Finally, a portion of data 310 stores the actual data of the data block. These include, for example, text data, image data, spreadsheet data, or the like.

 Fig. 4 is a flowchart of steps implemented in a method of recording a documentation data file according to embodiments. These steps may for example be implemented to generate a data structure according to FIG.

In a first step S400, documentation data is received for recording in a documentation data file. This is for example text data, image, spreadsheet or other. This data is for example generated using a word processor. Then, during a step S401, the received data are subdivided into data blocks. For example, a user having produced the document represented by the file received in step S400 has placed specific markers for recognizing portions of document to be considered as an element (for example, with reference to FIGS. 1 and 2, the user identifies items such as "Text2").

 For example, if the data is generated by word processing software, specific markers can be placed via this software. In this case, the software has a feature for associating a portion of the document with a level of detail. Thus, the editor of the document can write, for example after two (or more) versions of the same part of a document (for example a paragraph) with different levels of detail and associate with each of these versions a level of detail corresponding. Thus, when viewing the document, one or the other of these versions is displayed, depending on the choice of the reader. These markers can also allow the user to make links between parts of the document. For example, instead of creating versions one after the other, the writer can create them in another order and then link them later.

 Returning to FIG. 4, during step S402, a current data block is selected. Its level of detail is determined in step S403. For example, this level of detail is determined based on the specific markers placed by the user. In this case, further subdivision of the document, the markers indicate the level of detail of the subdivisions.

 This level of detail is then encoded and a level marker is generated in step S404. This marker is then recorded in step S405. For example, a data portion 309 as discussed with reference to Figure 3 is generated and then stored in a memory.

Then, it is determined in step S406 whether the current data block is linked to another block of data in the document. Once again, the markers placed by the user can be used for this purpose. If the current block is linked to one or more other blocks (YES), this or these linked blocks are determined in step S407. It is for example to determine their identifiers or their position in the data to be recorded.

 The level of detail of the bound blocks is then determined in step S408. A link marker is then generated in step S409 and then recorded in step S410. For example, it is a question of generating and recording a portion of data 302 as described with reference to FIG.

 In step S41 1, the data block is recorded. This is for example to record the block data in a portion 310 as described with reference to Figure 3. In this step, an identifier of the block can also be recorded (portion 301 of Figure 3).

 In step S406, if no link with another block is determined (NO), go directly to step S41 1. In this case, the portion 302 may be empty or have a code indicating that the data block is not linked to any other block.

 Once step S41 1 is executed, it is determined in a step S412 if there are other blocks to be recorded.

 If it is (YES), return to step S402 to process another block. If it is not the case (NO). The file is saved by associating all the data blocks and generated markers. For example, it is a question of creating a table regrouping memory addresses where each block of data and their markers are stored. For example, these are the memory addresses corresponding to blocks as described with reference to FIG. 3 and constituting the complete file.

 Figure 5 illustrates steps implemented in a display method according to embodiments.

 A documentation data file is received during an S500 step. Then, a current data block is selected in step S501.

A link marker associated with the data block (e.g., data portion 302 of Fig. 3) is read in step S502. A marker the level associated with the data block (for example the data portion 309 of FIG. 3) is read in step S503.

 Once these markers have been read, it may be possible to determine all the blocks linked to the current block and their levels of detail. It may also be possible to determine the level of detail of the current block.

 In step S504, the level of detail of the current block is compared to the desired level of detail for displaying the data in the documentation file. In this step, the detail levels of linked blocks can also be compared to the desired detail level for the display.

 Once the step S504 is executed, it may be possible to determine, for a part (or element) of the document represented by the file received in the step S500, which block is relevant to the desired level of detail.

 In step S505, it is determined whether the current data block is to be displayed. For example, it is a matter of determining whether its level of detail corresponds to the level of detail desired for displaying the data.

 If this is the case (YES), a display signal is generated during step S506 to cause the display of the data (text, image or other) of the current data block, for example on a screen.

 If it is not (NO), go directly to step S507, without executing step S506.

 In step S507, it is determined whether one of the linked blocks is to be displayed, for example if one of these blocks has a level of detail compatible with the level of detail desired for displaying the data.

 If it is the case (YES), a display signal is generated during step S508 to cause the display of the data (text, image or other) of the linked data block corresponding to the desired display level, for example on a screen.

 If this is not the case (NO), go directly to step S51 1 to determine if there are other blocks of data to be processed in the file.

After step S508, a step S509 can be implemented to determine whether to display the level of other linked blocks (for example to display a frame 104, as described with reference to FIG. 1). This For example, determination may depend on a user's display configuration or a user's response to a question in a graphical user interface.

 If the display of the levels of detail of the other blocks is not desired (NO), proceed to the step S51 1 already described.

 If not (YES), a display signal is generated in step S510 to display these levels. For example, this signal can cause the display of the frame 104 described with reference to FIG. Then go to step S51 1.

 In step S51 1, if it is determined that there are other blocks to be processed in the (YES) file, step S501 is returned to process a next block. Otherwise (NO), return to step S500 waiting for a new file.

 Computer programs for carrying out methods according to embodiments of the invention can be made from, in particular, the flowcharts of FIGS. 4 and 5 and the present detailed description.

 A recording or display device according to embodiments is described with reference to FIG. 6.

 The device 60 of FIG. 6 comprises a memory unit 61 (MEM). This memory unit comprises a random access memory for storing in an unsustainable manner calculation data used during the implementation of a method according to the invention, according to various embodiments. The memory unit furthermore comprises a non-volatile memory (for example of the EEPROM type) for storing, for example, a computer program, according to one embodiment, for its execution by a processor (not shown) of a memory unit. processing 62 (PROC) of the device. For example, the memory unit may store a documentation data file as previously described.

The device further comprises a communication unit 63 (COM), for example to receive documentation data files and / or to send display signals to a screen (not shown). The communication unit can also make it possible to communicate with a external storage device (hard disk, CD-ROM drive, DVD-ROM drive, USB stick, or other).

 The present invention has been described and illustrated in the present detailed description with reference to the accompanying figures. However, the present invention is not limited to the embodiments presented. Other variants and embodiments may be deduced and implemented by the person skilled in the art upon reading the present description and the appended figures.

 For example, the data format described in reference 3 has been given by way of example only, other formats may be envisaged. In particular, a documentation data file according to embodiments may take the form of an XML format file ("eXtended Markup Language").

 Such a file is illustrated in the following with reference to Figure 7 and Appendices 1 and 2.

 Referring to Figure 7, we take the non-limiting example of the addition of a user and its integration in a computer. It is a question of describing a part of documentation, for example a 1 .1 (that is to say Title 1, number 1).

 It is assumed that paragraph 1.1 is described by a block of data 70 itself comprising data blocks 71 (TEXT 1), 72 (TEXT 2) and 73 (TEXT 3).

 For example, four levels of detail are available for displaying paragraph 1 .1. It is assumed that data blocks 71 and 73 are associated with all levels of detail (1, 2, 3 and 4). Thus, they are displayed regardless of the level of detail chosen for the display.

 The block 72 can be composed of different combinations of data blocks according to the level of detail chosen.

 Each level of detail is associated with one or more blocks of data. Each block of data is associated with a level of detail.

 Thus, in the example of FIG. 7, the first level of detail

(Level 1) includes blocks 71 and 73 and a block of text data 74 (TEXT 2-1) constituting block 72. For example, in this first level of detail, only the sequence of instructions (possibly accompanied by default values) is presented with little or no explanation. In such a level of detail, which can be referred to as "condensed level", block 74 can be:

"Perform the action: Add a test user and make it available on the cluster using the

 network services available. "

The second level of detail (Level 2) comprises the blocks 71 and 73 and, to compose the block 72, the first block 74, followed by another block of data 75 (TEXT 2-2). For example, the block 75 is a block of text data but it could be another type of data such as image data or other.

 In this second level of detail, in block 72, in addition to the information provided by block 74, brief explanations can be presented as to the purpose of the instructions and the choice of default values. In such a level of detail, which can be referred to as "simplified level", block 75 can be:

"The file system is managed by a server

 NFS configured on the management node.

 Authentication is managed by a NIS server

 configured on the management node. "

The third level of detail (Level 3) comprises the blocks 71 and 73 and, to constitute the block 72, the first block 74, followed by the second block 75 and itself followed by another block of data 76 (TEXT 2- 3). For example, the block 76 is a block of text data but it could be another type of data such as image data, a combination of different types of data or other. In this third level of detail, in addition the information provided by the blocks 74 and 75, can be presented alternative operations and / or adjustments of certain parameters. In such a level of detail, which can be referred to as "detailed level", block 76 can be:

"Standard Linux commands are available.

 As a super user, run the add user command by specifying the group and working directory settings:

 useradd -g number_of_test_group -d

 / directory_export_nfs / test test

 As a super user, execute the password change command for the new user created: passwd test

 Changing password for user test

 New UNIX password: test

 Retype new UNIX password:

 passwd: garlic authentication tokens updated successfully.

 As a super user, run the update command for NIS authentication databases. For that, in the directory / var / yp execute the following command:

Moving from one level of detail to another does not necessarily mean adding a new block of data as a result of previous data blocks from previous levels. Thus, for example, the fourth level of detail (Level 4) comprises the block 71, the block 73 and, to constitute the block 72, the first block 74, followed by a fourth block of data 77 (TEXT 4). The fourth level of detail therefore does not include blocks 75 and 76. Block 77 replaces these blocks. For example, the block 77 is a block of text data but it could be another type of data such as image data, a combination of different types of data or other.

 In this fourth level of detail, in the block 72, furthermore the information provided by the block 74, can be presented detailed explanations and a presentation of fine adjustments. In such a level of detail, which can be referred to as "complex level", block 77 can be:

"Standard Linux commands and services

 are available.

 This user must be identical (id, guid, home)

 on the whole cluster.

 If you do not have access to a global authentication service, you can, for example

 use NIS from the management node.

 To install an NIS server, install the package

 containing the ypserv daemon (the name of the package

 depends on your distribution) and proceed to

 setting up and starting the service with the

 appropriate order. On the computing nodes side, the NIS client is often named ypbind, install

 the corresponding package and postpone

 settings that you used for the

 server configuration in its file

 configuration (/etc/yp/yp.conf) and start it. A

 Once the NIS structure is in place, the use

the make command in the / var / yp directory of the NIS server, proceed to the filling of the NIS bases by using as source the local authentication files (/ etc / passwd / etc / group and / etc / shadow) to the server.

Note To find the test group number, refer to the / etc / group file of the management node. For this temporary user, it is not necessary to use a specific id, the default value can be kept

For performance reasons you can also use local authentication at each compute node, which will avoid network queries when accessing. The procedure is to create a user locally to the server and to post the lines corresponding to it / etc / passwd / etc / group / etc / shadow files in the same files of the client.

Note If you make this choice, make sure you do not overwrite the authentication files of a client with those of a server, the users are not identical on these two different types of installation and the replacement pure and simple authentication files is not recommended

We will not detail the installation of an LDAP server, if you decide to use LDAP, refer to the documentation available on the management node.

The working directory of this user must be on a file system that is accessible to all nodes in the cluster. If there is not already such a file system, you can add one. In this case, we recommend using the default NFS server installed on the management. Edit the / etc / exports file

 server and re-export its content the with the

 exportfs command. On the client side, the NFS client

 is available natively, use the command

 mount to mount and access the system

 file exported from your server.

 In case of difficulty refer to the manual in

 accessible line thanks to the man command. To determine which block of data to display for a given level of detail. Each block can be associated with one or

several levels of detail. So, for example, block 74 is associated

at the four levels of detail, block 75 is associated with levels 2 and

3, block 76 is associated with level 3 and block 77 is associated with

level 4.

 It is possible to consider that the documentation generated according to embodiments is composed only of chapters (for example: Warning, Preface, Chapters, Appendices or other) and paragraphs. For example, the structure is fixed and a paragraph or chapter that contains nothing for the current level is displayed empty (this is the case where it is a paragraph or a chapter that contains only complex level data blocks while it is the simplified level that is required for display).

 Annexes 1 and 2 give examples of implementation. Appendix 1 gives a DTD (Document Type Definition) grammar and Appendix 2 gives an example of an XML file.

The person skilled in the art is able, by reading these appendices, to recognize the structure described above with reference to FIG. 7. In particular, it will find the different levels of detail (1, 2, 3 and 4) associated with the blocks of data (TEXT 1, TEXT2-1, TEXT2-2, TEXT2-3, TEXT2-4 and TEXT 3). In the claims, the term "include" does not exclude other elements or other steps. The indefinite article "one" does not exclude the plural. A single processor or several other units may be used to implement the invention. The various features presented and / or claimed can be advantageously combined. Their presence in the description or in different dependent claims does not exclude the possibility of combining them. The reference signs can not be understood as limiting the scope of the invention.

ANNEX 1

DTD grammar example <! DOCTYPE document [

 <! ELEMENT document (chapter +, blocks)>

<! ELEMENT chapter (paragraph +)>

<! ELEMENT paragraph (block_id ^* )>

 <! ELEMENT block_id (#PCDATA)>

<! ELEMENT blocks (block +)>

 <! ELEMENT block (level, links ?, content)>

<! ELEMENT EMPTY level>

<! ELEMENT liaisons (link ^* )>

 <! ELEMENT link EMPTY>

<! ELEMENT content ANY>

 <! ATTLIST document title CDATA #REQUIRED reference CDATA #REQUIRED>

 <! ATTLIST chapter

CDATA title # REQUIRED

CDATA number # REQUIRED>

 <! ATTLIST paragraph

CDATA title # REQUIRED

CDATA number # REQUIRED>

<! ATTLIST block block CDATA # REQUIRED>

<! ATTLIST level force CDATA "1">

 <! ATTLIST link

CDATA block # REQUIRED

CDATA force # REQUIRED>

]>

ANNEX 2

 Sample XML file

<! DOCTYPE document SYSTEM "document.dtd">

 <title document - Example of a documentation file "reference <title chapter- Title 1" number-> ">

 <title paragraph = "Title 1" number = "1">

 <block_id> Net01 -00K / block_id> <block_id> Net02-00K / block_id> <block_id> Net03-00K / block_id> </ paragraph>

</ Section>

<Block>

 <block_id block = "Net01 -001">

 <force level = "1234" />

 <Content>

 TEXT 1

 </ Content>

 </ Block>

 <block_id block = "Net02-001">

 <force level = "1234" />

 <Link>

 <link block_id = "Net02-002" force = "23" />

<link block_id = "Net02-003" force = "3" /> <block_id link = "Net02-004" force = "4" />

</ Link>

 <Content>

 TEXTE2-1

 </ Content>

 </ Block>

 <block_id block = "Net02-002">

 <strength level = "23" />

 <Link>

 <link block_id = "Net02-001" force = "1234" /> <block_id link = "Net02-003" force = "3" /> <block_id link = "Net02-004" force = "4" /> </ links>

 <Content>

 TEXTE2-2

 </ Content>

 </ Block>

 <block_id block = "Net02-003">

<strength level = "3"/> <Link>

 <link block_id = "Net02-001" force = "1234" /> <block_id link = "Net02-002" force = "23" /> <block_id link = "Net02-004" force = "4" />

</ Link>

 <Content>

 TEXTE2-3

 </ Content>

 </ Block>

 <block_id block = "Net02-004">

 <force level = "4" />

 <Link>

 <link block_id = "Net02-001" force = "1234" /> <block_id link = "Net02-002" force = "23" /> <block_id link = "Net02-003" force = "3" />

</ Link>

 <Content>

 TEXTE2-4

 </ Content>

 </ Block>

 <block_id block = "Net03-001">

 <force level = "1234" />

 <Content>

 texte3

 </ Content>

 </ Block>

</ Block>

 </ Title>

Claims

1. A method of recording a documentation data file for display on a screen, comprising the steps of: subdividing (S401) said data data into data blocks,  associating (S403) a level of detail with at least one block of data, and recording (S405, S41 1) said data block with a level marker relative to said associated level of detail, said marker being intended to be compared to a desired level of detail for displaying the data on the screen. The method of claim 1, further comprising a step of recording (S410) a link marker with said data block to make a documentation link with at least one other data block of the file. The method of claim 2, wherein said link marker provides a level of detail associated with said at least one linked block. The method according to one of the preceding claims, wherein at least one of the level marker and the link marker is a metadata. 5. Method for displaying file documentation data, comprising the following steps of:  comparing (S504) a level marker, in said file, relating to a level of detail associated with a data block of said display level-level file to display said data block, and generating (S506) a data display signal of said block if said level marker corresponds to said level of display detail. The method according to claim 5, further comprising a step of determining (S502), from a link marker with said data block, in said file, a documentation link with at least one other block of file data. 7. Method according to claim 6, comprising a step of generating (S508) a display signal of said link. 8. Method according to one of claims 6 and 7, further comprising a step of determining, from said link marker, a level of detail of said at least one other block of data. The method of claim 8, further comprising a step of generating (S510) a display signal of said level of detail of said at least one other data block. The method of one of claims 5 to 9, wherein at least one of the level marker, the link marker, and the indicator is a metadata. 1 1. Method according to one of claims 5 to 10, wherein the file has been recorded according to one of claims 1 to 4. Method according to one of the preceding claims, wherein the documentation data comprises text data. Method according to one of the preceding claims, wherein the documentation data comprises image data. 14. Method according to one of the preceding claims, wherein said file is in XML (eXtended Markup Language) format. A computer program comprising instructions for carrying out a method according to one of claims 1 to 14, when executed by a processor of a documentation data file storage device or a documentation data display device. Data recording medium (300) having recorded documentation data according to one of Claims 1 to 4 or one of Claims 12 to 14 in combination with one of Claims 1 to 4. 17. A data recording medium according to claim 16, including a first recording portion (309) for storing a detail level marker relative to a data block associated with said first recording portion. 18. Data recording medium according to one of claims 16 and 17. having a second recording portion (302) for storing a link documentation marker relating to a link between a data block associated with said second portion and at least one other data block. The data recording medium according to claim 18, wherein said second data portion has a recording sub-portion (306, 307, 308) for storing for each at least one other linked data block, a tag level of detail. 20. A device (60) for recording a documentation data file for display on a screen, comprising a processing unit (62) configured to subdivide said documentation data into data blocks, to associate a level of detail at least one block of data, recording said block of data with a level marker relative to said associated level of detail, said marker being intended to be compared to a desired level of detail for displaying the data on the screen. 21. The apparatus of claim 20, wherein the processing unit is further configured to register a link marker with said data block to make a documentation link with at least one other data block of the file. Apparatus according to claim 21, wherein said link marker provides a level of detail associated with said at least one linked block. Apparatus according to one of claims 20 to 22, wherein at least one of the level marker and the link marker is a metadata. 24. A file documentation data display device (60) having a processing unit (62) configured to determine a display detail level to display a data block of said file, to compare a level marker in said file, relating to a level of detail associated with said data block at the determined display detail level, and generating a data display signal of said block if said level marker corresponds to said level of display detail. Apparatus according to claim 24, wherein the processing unit is further configured to determine, from a link marker with said data block, in said file, a documentation link with at least one another block of data from the file. The apparatus of claim 25, wherein the processing unit is further configured to generate a display signal of said link. 27. The device according to one of claims 25 and 26, wherein the processing unit is further configured to determine, from said link marker, a level of detail of said at least one other data block. The apparatus of claim 27, wherein the processing unit is further configured to generate a display signal of said level of detail of said at least one other data block. Apparatus according to one of claims 24 to 28, wherein at least one of the level marker, the link marker and the indicator is a metadata. 30. Device according to one of claims 24 to 29, wherein the file has been recorded according to one of claims 1 to 4. 31. Apparatus according to one of claims 20 to 30, wherein the documentation data comprises text data. Apparatus according to one of claims 20 to 31, wherein the documentation data comprises image data. 33. Device according to one of claims 20 to 32, wherein said file is in XML (eXtended Markup Language) format.