WO2012171165A1

WO2012171165A1 - Method for managing link relationship table and related device

Info

Publication number: WO2012171165A1
Application number: PCT/CN2011/075688
Authority: WO
Inventors: 程海涛; 梁秋霞; 邹建青; 赵黎阳
Original assignee: 华为技术有限公司
Priority date: 2011-06-13
Filing date: 2011-06-13
Publication date: 2012-12-20
Also published as: CN102369527B; CN102369527A

Abstract

A method for managing a link relationship table and a related device are disclosed by the present invention. The method includes: obtaining a state changed topic file from the link relationship table; looking up all the link relationships associated with the topic file from the link relationship table; updating the link relationships according to the state changes of the topic file, and re-integrating the link relationship table.

Description

A link relationship table management method to control devices

The present invention relates to the field of information processing, and in particular, to a link relationship table management method and related devices.

Background technique

The Darwin Information Typing Architecture (DITA) is an open standard for the Organization for the Advancement of Structured Information Standards (OASIS). It defines an Extensible Markup Language (XML) architecture for designing, writing, publishing, and managing content. Content developed based on this standard can be easily released into portable file format (PDF, Portable Document Format), online help, Hypertext Markup Language (HTML), and other forms of data delivery. .

Darwin: DITA adopts the concept of inheritance and variation (special 4匕) similar to Darwin's theory of evolution.

Information Typing: Topic is an information unit in DITA, and each Topic must belong to one type of information. DITA defines three basic types of information for the technical documentation—Concept, Task, and Reference. The basic information type can be extended to a new information type through specialized technology.

DITA is an XML architecture for designing, writing, publishing, and managing content. Under the DITA architecture, Topic and Outline are two basic types of XML files. Topic is a basic, manageable writing and reuse unit with several features: A Topic consists of two parts, title and content; each Topic describes only one topic or answers a question; and each Topic can complete the topic. Or answer this question, it is a self-contained unit of information. Map is an XML file type defined in DITA. It is used to describe the logical hierarchy and order relationship between Topic to form a data delivery. Through Map, you can connect a series of Topics together to output various forms of data delivery, such as manuals, online help, and so on.

DITA provides a variety of ways to generate links that generate rich links in electronic deliverables that make it easy for users to navigate and locate information. Among them, create a Link Relationship Table in the Map The main way is to define the link relationship between Topics.

The prior art manages the link relationship table in the form of a table, that is, supports the creation, editing, and deletion of the link relationship through the table. All of these operations on the interface are automatically synchronized to the underlying Map file, achieving the same effect as manually editing the source file. However, in the prior art, when editing or deleting a Topic file, only the Topic file itself is processed, and the link relationship between the Topic file and other Topic files is not considered, for example, the Topic file is deleted: Link relationship The relationship associated with the Topic file in the table is not deleted synchronously, resulting in inconsistent information, which may lead to file system errors.

Summary of the invention

The embodiment of the present invention provides a link relationship table management method and related apparatus, which are used to synchronously update a link relationship related to the theme file in the link relationship table when the theme file is operated.

The method for managing a link relationship table provided by the present invention includes: acquiring a theme file whose status changes in a link relationship table; searching for all link relationships related to the theme file in the link relationship table; changing according to a state of the theme file Update the link relationship and re-integrate the link relationship table.

The link relationship table management apparatus provided by the present invention includes: an obtaining unit, configured to acquire a theme file whose status changes in the link relationship table; and a searching unit, configured to search for all links related to the theme file in the link relationship table a relationship unit, configured to update the link relationship according to a state change of the theme file, and re-integrate the link relationship table.

As can be seen from the above technical solutions, the embodiment of the present invention has the following advantages: When the status of the theme file changes, the link relationship table management apparatus in the embodiment of the present invention can detect the theme file, and find and search in the link relationship table. Update all the link relationships related to the theme file to conveniently manage the synchronization of the link relationship table.

DRAWINGS

1 is a schematic flow chart of a method for managing a link relationship table in the present invention;

2 is another schematic flowchart of a method for managing a link relationship table in the present invention;

3 is a schematic diagram of a topic link relationship in a link relationship table management method according to the present invention;

Fig. 4 is a structural diagram of a link relationship table management apparatus in the present invention.

detailed description The embodiment of the present invention provides a link relationship table management method and related apparatus, which are used to synchronously update a link relationship related to the theme file in the link relationship table when the theme file is operated.

Referring to FIG. 1, an embodiment of a method for managing a link relationship table in an embodiment of the present invention includes:

101. Obtain a theme file whose status changes;

The link relationship table management device acquires a theme file whose status changes in the link relationship table.

The link relationship table management apparatus in the embodiment of the present invention detects the status of each topic file in the link relationship table in real time, and if the status of the topic file changes in the link relationship table (for example, the theme file is edited, or the theme file is deleted) Then, the link relationship table management can be immediately known, and the related information of the theme file whose status has changed is obtained, and subsequent processing is performed.

102. Find related link relationships;

The link relation table management means finds all the link relationships in the link relationship table related to the theme file whose status has changed.

After obtaining the theme file whose status changes, the file header of the theme file traverses all the link relationships in the link relationship table to find all the link relationships related to the theme file (including: using the theme file as the source theme) The link relationship of the file, the link relationship of the theme file for the purpose of the theme file).

103. Update the link relationship table according to the state change.

The link relationship table management means updates the link relationship related to the topic according to the state change of the theme file, and re-integrates the link relationship table.

In the embodiment of the present invention, the user can perform operations such as creating, editing, and deleting the theme files in the outline. When creating a new theme file, the user can set a link relationship between the newly created theme file and other theme files, and then re-integrate the link relationship table, the link relationship table management device automatically automatically creates a new theme file and other theme files. The link relationship is added to the link relationship table to complete the update of the link relationship table. When the theme file is edited, if the file header of the edited theme file is changed, the above step 102 is updated according to the change of the file header. Related link relationships, and re-integration of the link relationship table according to the updated link relationship; when deleting the topic file, synchronously delete the relevant link relationship found in step 102 above, and re-integrate the link relationship table.

The above method for updating the link relationship according to the state change is only an example. It can be understood that there are other state change situations and related update link relationship operations in the actual application, specifically here. Not limited.

When the status of the theme file is changed, the link relationship table management apparatus in the embodiment of the present invention can detect the theme file, find and update all the link relationships related to the theme file in the link relationship table, and conveniently implement the link. Synchronous management of relational tables.

In addition to the related link relationship of the theme file whose status of the synchronization update is changed, the present invention also provides a link relationship table integration method which is closer to the actual application. Referring to FIG. 2, the link relationship table management in the embodiment of the present invention is provided. Another embodiment of the method includes:

201. Acquire a theme file whose status changes;

The content of step 201 in this embodiment is the same as that of step 101 in the foregoing embodiment shown in FIG. 1, and details are not described herein again.

202. Find related link relationships;

The content of the step 202 in this embodiment is the same as that of the step 102 in the foregoing embodiment shown in FIG. 1, and details are not described herein again.

203. Update a link relationship according to a state change.

The link relationship table management device acquires state change information generated by the theme file, and if the state changes to edit, determines whether the edited theme file has changed the file header, and if so, updates the above step 102 by using the file header of the theme file after editing. The related link relationship found, if not, does not update the link relationship; if the state change is deleted, all related link relationships found in step 102 above are deleted. The foregoing method for updating the link relationship according to the state change is only an example. It can be understood that there are other state change situations and operations related to updating the link relationship in the actual application, which is not limited herein.

204. Delete an integrated link relationship;

The link relationship table management device deletes the integrated link relationship in the original link relationship table.

In the embodiment of the present invention, the link relationship table stores the top-level link relationship and the sub-layer link relationship respectively, and the top-level link relationship is divided into a top-level custom link relationship and an integrated link relationship; the sub-layer link relationship is a user-defined link relationship, The change of the sub-layer link relationship requires the user to perform an active operation (such as modification or deletion), and the integrated link relationship of the top-level link relationship is automatically integrated by the link relationship table management device according to each sub-layer link relationship; When the layer link relationship is changed, the link relationship table management device can automatically delete the integrated link relationship in the original link relationship table, according to the change. Sub-layer link relationships are re-integrated to get a new top-level link relationship.

The top-level link relationship is the link relationship of the top-level outline (map), which contains the link relationship between all related topic files, which can facilitate the user to grasp the link between the theme files as a whole;

The sub-layer link relationship is further divided into a topic link relationship and a map link relationship, where the topic link relationship is a link relationship between each user-defined topic, and the map link relationship is between user-defined sub-layer maps within the theme file. Link relationship. The theme link relationship is that the present invention provides a convenient function module for the user, and each theme file is associated with a relationship set. After the user creates a theme file and edits the theme file, the theme file can be set at the same time. The link relationship between other theme files enables the link relationship table management device to automatically integrate the topic link relationship into the link relationship table when integrating the link relationship table, and quickly and conveniently complete the management of the link relationship table without requiring the user to Time-consuming re-traversal of individual theme files. In addition to the user's own definition of the link relationship between the various topic files, the user can also define the link relationship between the topic files in each sub-layer map when the link relationship table is organized, so that the management of the link relationship table is more humanized.

205. Perform deduplication processing on the sub-layer link relationship.

The link relationship table management device acquires all sub-layer link relationships (including the topic link relationship and the map link relationship), and de-duplicates the sub-layer link relationship.

In the process of defining the link relationship by the user, the link relationship between the two topic files may be repeatedly defined. In order to avoid an error in the integration of the link relationship table, the link relationship table management device will link the sub-layer link. Perform deduplication processing.

Optionally, in the process of integrating the link relation table, you can choose to integrate only the topic link relationship, or only the topic link relationship and the first layer of the sub-layer map. In actual applications, this process can be set. In the form of optional options for the user to select, the user selects the appropriate integration project according to the needs of his own editing, which is convenient for intuitive operation.

206. Generate an integrated link relationship;

The link relationship table management device integrates the sub-layer link relationship after the de-reprocessing process into an integrated link relationship, and determines whether the source theme file and the target theme file in the sub-layer link relationship are in the same map, and if so, the source The link relationship formed by the theme file and the destination theme file is marked as an internal relationship, and if not, the link relationship formed by the source theme file and the destination theme file is marked as an external relationship. In the embodiment of the present invention, the top-level link relationship includes a top-level custom link relationship and an integrated link relationship. The integrated link relationship is obtained by automatically integrating the user-defined sub-layer link relationship by the link relationship table management device, and the top-level custom link relationship is a link relationship in the top-level map defined by the user.

207. Obtain a top-level custom link relationship.

The link relationship table management device obtains a top-level custom link relationship.

208. Obtain a new link relationship table.

The link relationship table management merges the above-mentioned top-level custom link relationship and the integrated link relationship, and generates a DITA standard format link relationship table according to the merged top-level custom link relationship and the integrated link relationship, and exports the file in an XML file.

The embodiment of the present invention is more close to the actual application situation, and provides the user with a function module of the topic link relationship, and associates each theme file from the content point of view when designing the theme file, so that when planning or re-integrating the link relationship table, The user's operation is more convenient.

For ease of understanding, the link relationship table management described in the foregoing embodiment is described in a specific application scenario. Referring to FIG. 3, specifically:

User-defined link relationships are shown in Figure 3. The custom link relationships for topic file 2.1 are as follows:

The custom link relationships within the sublayer map are as follows: Source node destination node

Sub-level outline 1 - theme file 2 sub-layer outline 1 - theme file 3

Assuming that the user deletes the sub-layer outline 1_subject file 2 (subMapl_topic2) while performing the operation, the link relationship table management device searches all the link relationships related to the theme file whose status has changed in the original link relationship table. The theme files linked to subMapl-topic2 are: sub-layer outline 1_subject file 1 (subMapl_topicl) and sub-layer outline 1_subject file 3 (subMa l _topic3 ), then the above related link relationship is: "src: subMap 1 _topic2— dest: subMa l _topic3” and "src: subMapl— topic 1—dest: subMapl— topic2,,.

Since the state of subMapl_topic2 changes to delete, the link relationship table management device deletes the link relationship src: subMap 1 Jopic2_dest: subMa l_topic3" and "src: subMapl_ topic 1_dest: subMa l_topic2".

After deleting the above related link relationship, the link relationship table management device starts to re-integrate the link relationship table:

First, delete the integrated link relationship in the original top-level link relationship;

Then, iterate through all the sub-layer link relationships (including: custom link relationship of theme file 2.1, sub-layer outline 1 - custom link relationship of theme file 1 and map link relationship, custom link relationship within sub-layer map is also child The layer link relationship, but has been deleted when the link relationship is updated, and the sub-layer link relationship is de-duplicated (the sub-layer link relationship in the embodiment of the present invention is not repeated);

Again, the sub-layer link relationship after the de-reprocessing is integrated into an integrated link relationship, and it is determined whether the source theme file and the destination theme file in the sub-layer link relationship are in the same map, and if so, the source theme file and The link relationship formed by the target theme file is marked as an internal relationship. If not, the link relationship formed by the source theme file and the destination theme file is marked as an external relationship (as shown in the following table): Source node destination node type theme file 2.1 Theme file 1.1.2 Internal relationship theme file 2.1 Theme file 2 Internal relationship theme file 2.1 Theme file 2 Internal relationship Theme file 2.1 External - Topic file 1 External relationship sub-layer outline 1 - Topic file 1 External - Topic file 1 External relationship

Finally, the link relationship table management device searches whether there is a top-level custom link relationship in the link relationship table (the top-level custom link relationship is not set in the embodiment of the present invention), and if not, directly uses the integrated link relationship as a link in the DITA standard format. Relational table output (as shown in the table above for integrated link relationships).

Optionally, in the process of integrating the link relation table, if the user chooses to integrate only the inner relationship, the obtained integration relationship is as follows:

In practical applications, more integration conditions can be set to meet the different needs of users. The application scenario in the embodiment of the present invention is described by using only some examples. It can be understood that there are more application scenarios in the actual application, which are not limited herein.

The following describes an embodiment of the link relationship table management apparatus of the present invention for performing the above-described link relationship table management method. For the logical structure, please refer to FIG. 4. One embodiment of the link relationship table management apparatus in the embodiment of the present invention includes:

The obtaining unit 401 is configured to obtain a theme file whose status changes in the link relationship table, and the searching unit 402 is configured to search for all the link relationships related to the foregoing topic file in the link relationship table;

The integration unit 403 is configured to update the link relationship according to the state change of the foregoing topic file, and re-integrate the link relationship table.

The integration unit 403 in the embodiment of the present invention includes:

The relationship update module 4031 is configured to: if the state change of the theme file is edited, determine whether the editing process changes the file header of the theme file, and if yes, update the chain by using the edited file header The connection relationship, if not, does not update the link relationship; if the state of the theme file changes to delete, delete all link relationships related to the theme file;

The relationship integration module 4032 is configured to delete the integrated link relationship; obtain the sub-layer link relationship, and perform de-duplication processing on the sub-layer link relationship; copy the de-reprocessed sub-layer link relationship into the link relationship table, and derive the link relationship table.

The specific interaction process of each unit in the link relationship table management apparatus in the embodiment of the present invention is as follows: When detecting the change of the status of the topic file in the link relationship table, the obtaining unit 401 acquires the topic file whose status changes in the link relationship table. . The link relationship table management apparatus in the embodiment of the present invention detects the status of each topic file in the link relationship table in real time, and if the status of the topic file changes in the link relationship table (for example, the theme file is edited, or the theme file is deleted) Then, the link relationship table management can be immediately known, and the related information of the theme file whose status has changed is obtained, and subsequent processing is performed.

After obtaining the theme file whose status changes, the searching unit 402 searches for all the link relationships related to the theme file whose status changes in the link relationship table (including: the link relationship with the theme file as the source theme file, with the theme The link relationship of the theme file for the purpose of the file).

After the related link relationship is found, the relationship update module 4031 of the integration unit 403 acquires the state change information generated by the theme file, and if the state changes to edit, determines whether the edited theme file changes the file header, and if so, uses After editing, the file header of the theme file updates the related link relationship found in the above step 102. If not, the link relationship is not updated; if the state change is deleted, all the related link relationships found in the above step 102 are deleted. The foregoing method for updating the link relationship according to the state change is only an example. It can be understood that there are other state changes in the actual application and the operation of updating the link relationship, which is not limited herein.

After the update of the related link relationship is completed, the relationship integration module 4032 first deletes the original integrated link relationship in the link relationship table; then, acquires all the sub-layer link relationships (including the topic link relationship and the map link relationship), and The sub-layer link relationship is de-reprocessed; optionally, in the process of integrating the link relationship table, it is possible to choose to integrate only the topic link relationship, or only the topic link relationship and the first-level sub-layer map. In practical applications, this process can be set to an optional form for the user to select. The user selects a suitable integration project according to the needs of his own editing, which is convenient for intuitive operation; again, the sub-layer link after de-reprocessing is completed. Copy to relationship Integrating the link relationship and determining whether the source theme file and the destination theme file in the sub-layer link relationship are in the same map, and if so, marking the link relationship formed by the source theme file and the destination theme file as an internal relationship, if not , the link relationship formed by the source theme file and the destination theme file is marked as an external relationship. In the embodiment of the present invention, the top-level link relationship includes a top-level custom link relationship and an integrated link relationship. The integrated link relationship is obtained by automatically integrating the user-defined sub-layer link relationship by the link relationship table management device, and the top-level custom link relationship is a link relationship in the top-level map defined by the user; finally, obtaining a top-level custom link relationship, The top-level custom link relationship and the integrated link relationship are merged, and the DITA standard format link relationship table is generated according to the merged top-level custom link relationship and the integrated link relationship, and is exported as an XML file.

In the several embodiments provided herein, it should be understood that the disclosed apparatus and method can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in the form of electrical, mechanical or other.

The units described as separate components may or may not be physically separate, and the components displayed as the units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may contribute to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. , including a number of instructions to make a computer device (which can be a personal computer, a server, Or a network device or the like) performing all or part of the steps of the method of the various embodiments of the present invention. The foregoing storage medium includes: a U disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes. .

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Claims

- 12- Claims

A method for managing a link relationship table, comprising:

Obtain a theme file whose status changes in the link relationship table;

Finding all the link relationships in the link relationship table related to the theme file;

The link relationship is updated according to the state change of the theme file, and the link relationship table is re-integrated.

2. The method according to claim 1, wherein the state change of the theme file comprises: editing and deleting.

The method according to claim 2, wherein, if the state changes to an edit, the updating the link relationship according to a state change of a theme file includes:

Determining whether the editing changes the file header of the theme file, and if so, updating the link relationship using the edited file header, and if not, updating the link relationship.

The method according to claim 2, wherein, if the state changes to a deletion, the updating the link relationship according to a state change of a theme file includes:

Delete all link relationships associated with the theme file.

5. A method according to any one of claims 1 to 4, characterized in that

The link relationship table includes: a top-level link relationship and a sub-layer link relationship;

The top-level link relationship includes: a top-level custom link relationship and an integrated link relationship; and the re-integration link relationship table includes:

Delete the original integrated link relationship;

Obtaining the sub-layer link relationship, and performing de-duplication processing on the sub-layer link relationship; copying the de-re-processed sub-layer link relationship into a link relationship table, and deriving the link relationship table.

6. The method of claim 5, wherein

And copying the sub-layer link relationship after the de-duplication processing into the link relationship table, and exporting the link relationship table, including:

Integrating the sub-layer link relationship after de-reprocessing into a new integrated link relationship;

Obtaining a top-level custom link relationship, where the top-level custom link relationship is a user-defined top-level link relationship; - 13 - Merging the top-level custom link relationship and the integrated link relationship, and exporting the merged top-level custom link relationship and the integrated link relationship as a link relationship table.

The method according to claim 6, wherein after the de-duplication processing of the sub-layer link relationship, the method comprises:

Determining whether the source theme file and the destination theme file in the sub-layer link relationship are in the same outline map, and if so, marking the link relationship formed by the source theme file and the target theme file as an internal relationship, and if not, The link relationship formed by the source theme file and the destination theme file is marked as an external relationship.

The method according to claim 5, wherein the sub-layer link relationship comprises: a topic link relationship and a map link relationship, wherein the topic link relationship is a link relationship between user-defined individual topic files, The map link relationship is a link relationship between topic files in each user-defined sub-layer map;

The obtaining the sub-layer link relationship includes:

Get topic link relationships, and / or map link relationships.

9. A link relationship table management apparatus, comprising:

An obtaining unit, configured to acquire a theme file whose status changes in the link relationship table;

a searching unit, configured to search for all the links related to the theme file in the link relationship table;

And an integration unit, configured to update the link relationship according to a state change of the theme file, and re-integrate the link relationship table.

The device according to claim 9, wherein the integration unit comprises: a relationship update module, configured to determine, if the state changes to an edit, whether the edit changes a file header of the theme file If yes, the linked relationship is updated by using the edited file header, and if not, the link relationship is not updated; if the state change is deleted, all link relationships related to the theme file are deleted;

a relationship integration module, configured to delete an original integrated link relationship; obtain the sub-layer link relationship, and perform de-duplication processing on the sub-layer link relationship; and copy the de-reprocessed sub-layer link relationship to the link In the relational table, the linked relationship table is exported.