CN102369527A - Management method of link relation table and correlative device - Google Patents
Management method of link relation table and correlative device Download PDFInfo
- Publication number
- CN102369527A CN102369527A CN2011800011458A CN201180001145A CN102369527A CN 102369527 A CN102369527 A CN 102369527A CN 2011800011458 A CN2011800011458 A CN 2011800011458A CN 201180001145 A CN201180001145 A CN 201180001145A CN 102369527 A CN102369527 A CN 102369527A
- Authority
- CN
- China
- Prior art keywords
- linking relationship
- subject document
- linking
- sublayer
- relationship table
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims abstract description 51
- 238000000034 method Methods 0.000 claims abstract description 24
- 230000010354 integration Effects 0.000 claims description 26
- 238000012217 deletion Methods 0.000 claims description 15
- 230000037430 deletion Effects 0.000 claims description 15
- 240000005369 Alstonia scholaris Species 0.000 description 11
- 230000008859 change Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 238000011897 real-time detection Methods 0.000 description 2
- 230000015572 biosynthetic process Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000032696 parturition Effects 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/93—Document management systems
- G06F16/94—Hypermedia
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Document Processing Apparatus (AREA)
Abstract
The invention discloses a management method of a link relation table and a correlative device. The method comprises the steps of acquiring a theme file of which the state is changed in the link relation table, searching all link relations correlative to the theme file in the link relation table, according to the state changing of the theme file, updating the link relations, and reintegrating the link relation table.
Description
Technical field
The present invention relates to field of information processing, relate in particular to a kind of linking relationship table management method and relevant apparatus.
Background technology
Darwin's information classification architectural framework (DITA; Darwin Information Typing Architecture) is a kind of open standard that the structured message standard promotes tissue (OASIS, Organization for the Advancement of Structured Information Standards).It defined a kind ofly be used to design, write, extend markup language (XML, the Extensible Markup Language) framework of publication and organize content.Can be easily be issued as portable file layout (PDF based on the content of this standard development according to user's needs; Portable Document Format), Online Help, HTML (HTML, Hyper Text Mark-up Language) and other forms of data are paid part.
Darwin (Darwin): DITA has adopted succession and the notion of variation (specialization) in the similar Darwinian evolution.
Information type (Information Typing): theme (Topic) is a kind of message unit among the DITA, and each Topic must belong to a kind of information type.DITA is that technical documentation has defined three kinds of basic information types---notion (Concept), task (Task) and reference (Reference).Can expand basic information type through specialized technology is new information type.
DITA be a kind ofly be used to design, write, the XML framework of publication and organize content, under the DITA framework, Topic and outline (Map) are two kinds of basic XML file types.Topic is basic, manageable writing and reuses the unit, has several characteristics: a Topic comprises title and two parts of content; Each Topic only describes an exercise question or answers a problem; And each Topic can accomplish this exercise question of statement or answer this problem, is a self-contained message unit.Map is a kind of XML file type that defines among the DITA, and it is used for describing logic level and ordinal relation between the Topic, and the formation data is paid part.Through Map, can be connected in series Topic one by one, be used to export various forms of data and pay part, like handbook, Online Help etc.
DITA provides the method for multiple generation link, can in electron delivery spare, generate abundant link, makes things convenient for the user to navigate and locating information.Wherein, in Map, creating linking relationship table (Relationship Table) is main mode, and it has defined the linking relationship between the Topic.
Prior art is come managing concatenated relation table with the form of form, promptly through the form support to operations such as newly-built, the editor of linking relationship, deletions.All these operations on the interface all can be synchronized in the Map file of bottom automatically, reach the effect the same with the edit source file.But; When prior art is operated the Topic file is edited or deletion etc.; Only this Topic file is handled itself, and reckoned without the linking relationship of this Topic file and other Topic file, as deleted the Topic file: the relation with this Topic file association in the linking relationship table is not synchronized deletion; Cause information inconsistency, cause file system to be made mistakes easily.
Summary of the invention
The embodiment of the invention provides a kind of linking relationship table management method and relevant apparatus, is used for when subject document is operated, and upgrades linking relationship relevant with this subject document in the linking relationship table synchronously.
Linking relationship table management method provided by the invention comprises: obtain the subject document that state changes in the linking relationship table; Search all linking relationships relevant in the said linking relationship table with said subject document; Upgrade said linking relationship according to the state variation of said subject document, and reintegrate said linking relationship table.
Linking relationship table management devices provided by the invention comprises: acquiring unit is used for obtaining the subject document that linking relationship table state changes; Search the unit, be used for searching all linking relationships relevant of said linking relationship table with said subject document; Integral unit is used for upgrading said linking relationship according to the state variation of said subject document, and reintegrates said linking relationship table.
Can find out from above technical scheme; The embodiment of the invention has the following advantages: when the state of subject document changes; Linking relationship table management devices in the embodiment of the invention can detect this subject document; In the linking relationship table, search and upgrade all linking relationships relevant, realize management by synchronization easily the linking relationship table with this subject document.
Description of drawings
Fig. 1 is a schematic flow sheet of link relation table management method among the present invention;
Fig. 2 is another schematic flow sheet of link relation table management method among the present invention;
Fig. 3 is the synoptic diagram of topic links relation in the linking relationship table management method of the present invention;
Fig. 4 is a structural drawing of link relation table management devices among the present invention.
Embodiment
The embodiment of the invention provides a kind of linking relationship table management method and relevant apparatus, is used for when subject document is operated, and upgrades linking relationship relevant with this subject document in the linking relationship table synchronously.
See also Fig. 1, link one embodiment comprises of relation table management method in the embodiment of the invention:
101, obtain the subject document that state changes;
Linking relationship table management devices obtains the subject document that state changes in the linking relationship table.
The state of each subject document in the real-time detection linking relationship table of linking relationship table management devices in the embodiment of the invention; If (as: subject document is edited to have the state of subject document to change in the linking relationship table; Or subject document is deleted); Then linking relationship table management can be known at once, and obtains the relevant information of the subject document that this state changes, and carries out subsequent treatment.
102, search relevant linking relationship;
Linking relationship table management devices is searched in the linking relationship table all relevant linking relationships of subject document that change with this state.
After getting access to the subject document that this state changes; According to all linking relationships in the file header traversal link relation table of this subject document; Find all linking relationships relevant (comprising: with this subject document is the linking relationship of source subject document, is the linking relationship of purpose subject document with this subject document) with this subject document.
103, upgrade the linking relationship table according to state variation.
Linking relationship table management devices upgrades the linking relationship relevant with this theme according to the state variation of this subject document, and reintegrates the linking relationship table.
In embodiments of the present invention, the user can carry out operations such as newly-built, editor and deletion to the subject document in the outline.When the new theme file; The user can be provided with the linking relationship between newly-built subject document and other subject documents; When reintegrating the linking relationship table again; Linking relationship table management devices can add the linking relationship between newly-built subject document and other subject documents in this linking relationship table to automatically, accomplishes the renewal of linking relationship table; When editor's subject document, if the file header of the subject document of being edited changes, the peer link relation that above-mentioned steps 102 is found is upgraded in the variation of then giving birth to according to this document hair, and reintegrates the linking relationship table according to the linking relationship after upgrading; When the deletion subject document, delete the peer link relation that above-mentioned steps 102 is found synchronously, and reintegrate the linking relationship table.
Above-mentioned method according to state variation renewal linking relationship only is that some are given an example, and it is understandable that, in practical application, also has other state variation situation and the relevant operation of upgrading linking relationship, does not specifically limit here.
When the state of subject document changes; Linking relationship table management devices in the embodiment of the invention can detect this subject document; In the linking relationship table, search and upgrade all linking relationships relevant, realize management by synchronization easily the linking relationship table with this subject document.
The peer link relation of the subject document that changes except above-mentioned synchronous update mode; The linking relationship table integration method that the present invention also provides a kind of more closing to reality to use; See also Fig. 2, another embodiment of link relation table management method comprises in the embodiment of the invention:
201, obtain the subject document that state changes;
The content of the step 201 in the present embodiment is identical with the content of step 101 among the aforementioned embodiment shown in Figure 1, repeats no more here.
202, search relevant linking relationship;
The content of the step 202 in the present embodiment is identical with the content of step 102 among the aforementioned embodiment shown in Figure 1, repeats no more here.
203, upgrade linking relationship according to state variation;
Linking relationship table management devices obtains the state change information that above-mentioned subject document takes place; If state variation is editor; Whether the subject document that judgement is edited has changed file header, if then use the peer link relation that the file header renewal above-mentioned steps 102 of this subject document is found after editing; If not, then do not upgrade this linking relationship; If state variation is deletion, delete the peer link relation that all above-mentioned steps 102 are found.Above-mentioned method according to state variation renewal linking relationship only is that some are given an example, and it is understandable that, in practical application, also has other state variation situation and the relevant operation of upgrading linking relationship, does not specifically limit here.
204, linking relationship is integrated in deletion;
Linking relationship table management devices is deleted the integration linking relationship in original linking relationship table.
In embodiments of the present invention, the linking relationship table has been stored top layer linking relationship and sublayer linking relationship respectively, is divided into top layer custom link relation in the top layer linking relationship and integrates linking relationship; The sublayer linking relationship is user-defined linking relationship; The change of this sublayer linking relationship needs the user to carry out operation (as revising or deletion) initiatively, and the integration linking relationship of top layer linking relationship is then by being that linking relationship table management devices is integrated automatically according to each sub-layer linking relationship and formed; When this sublayer linking relationship changed, linking relationship table management devices can be deleted the integration linking relationship in original linking relationship table automatically, reintegrated according to sublayer linking relationship after changing and obtained new top layer linking relationship.
The top layer linking relationship is the linking relationship of top layer outline (map), has comprised the linking relationship between all relevant subject documents in this top layer linking relationship, can be so that the user holds the link situation between the subject document on the whole;
The sublayer linking relationship also is divided into topic links relation and map linking relationship, and this topic links relation is the linking relationship between user-defined each theme, and this map linking relationship is the linking relationship between the subject document in user-defined each sub-layer map.The topic links relation is that the present invention provides the convenient function module for the user; All attached in each subject document have a set of relationship; The user when this subject document is edited, can set the linking relationship between this subject document and other subject document simultaneously after creating a subject document; Make linking relationship table management devices when integrating the linking relationship table; Can automatically this topic links relation be integrated in the linking relationship table, accomplish the management of linking relationship table quickly and easily, need not the user and travel through each subject document more time-consumingly again.The user can also define the linking relationship between the subject document in each sub-layer map voluntarily except can defining voluntarily the linking relationship between each subject document when arrangement linking relationship table, make the management hommization more of linking relationship table.
205, the sublayer linking relationship is gone heavily to handle;
Linking relationship table management devices obtains all sublayer linking relationships (comprising topic links relation and map linking relationship), and this sublayer linking relationship is gone heavily to handle.
In the process that the user defines linking relationship; May carry out the definition of repetition to the linking relationship between two subject documents; For fear of when carrying out the integration of linking relationship table, makeing mistakes, linking relationship table management devices can go heavily to handle to the sublayer linking relationship.
Optional; In the process of carrying out the integration of linking relationship table; Only can select the topic links relation is integrated, or only the sublayer map of topic links relation and ground floor integrated, in practical application, can supply the user to select the form that this process is arranged to option; The user selects suitable integration project according to self editor's needs, is convenient to operate intuitively.
206, generate the integration linking relationship;
Sublayer linking relationship after linking relationship table management devices goes completion heavily to handle is integrated into the integration linking relationship; And judge in this sublayer linking relationship that source subject document and purpose subject document are whether in same map; If; The linking relationship that then this source subject document and purpose subject document is constituted is labeled as interior relation, and if not, the linking relationship that then this source subject document and purpose subject document is constituted is labeled as outer relation.
In embodiments of the present invention, the top layer linking relationship includes top layer custom link relation and integrates linking relationship.This integration linking relationship is that linking relationship table management devices is integrated user-defined sublayer linking relationship automatically and obtained, the interior linking relationship of top layer map that top layer custom link relation defines for the user voluntarily.
207, obtain top layer custom link relation;
Linking relationship table management devices obtains top layer custom link relation.
208, obtain new linking relationship table.
Linking relationship table management merges the above-mentioned top layer custom link relation that obtains and integrates linking relationship, according to the top layer custom link relation after merging and integrate the linking relationship table that linking relationship generates the DITA standard format, and derives with the XML file.
The embodiment of the invention is the closing to reality applicable cases more; The functional module of topic links relation is provided for the user; When the design motif file on the angle of content related each subject document, make in the planning of carrying out the linking relationship table or when reintegrating, user's operation is more convenient.
For the ease of understanding, with a concrete application scenarios linking relationship table management of describing in the above embodiments is described below, see also Fig. 3, be specially:
User-defined linking relationship is as shown in Figure 3, and the custom link of subject document 2.1 concerns as follows:
| Source node | Destination node |
| Subject document 2.1 | Subject document 1.1.2 |
| Subject document 2.1 | Subject document 2 |
| Subject document 2.1 | Subject document 3 |
| Subject document 2.1 | Sublayer outline 1_ subject document 1 |
The custom link of sublayer outline 1 subject document 1 concerns as follows:
| Source node | Destination node |
| Sublayer outline 1_ subject document 1 | Sublayer outline 1_ subject document 2 |
| Sublayer outline 1_ subject document 1 | Outside _ subject document 1 |
Custom link in the map of sublayer concerns as follows:
| Source node | Destination node |
| Sublayer outline 1_ subject document 2 | Sublayer outline 1_ subject document 3 |
Suppose that the user is when operating; Sublayer outline 1_ subject document 2 (subMap1_topic2) have been deleted; Then linking relationship table management devices will be searched the relevant linking relationship of subject document that all change with this state in original linking relationship table; Have the subject document of linking relationship to have with subMap1_topic2: sublayer outline 1_ subject document 1 (subMap1_topic1) and sublayer outline 1_ subject document 3 (subMap1_topic3), then above-mentioned relevant linking relationship is: " src:subMap1_topic2-dest:subMap1_topic3 " and " src:subMap1_topic1-dest:subMap1_topic2 ".
Because the state variation of subMap1_topic2 is deletion, then linking relationship table management devices has been deleted linking relationship src:subMap1_topic2-dest:subMap1_topic3 accordingly " and " src:subMap1_topic1-dest:subMap1_topic2 ".
After having deleted above-mentioned relevant linking relationship, linking relationship table management devices begins to reintegrate the linking relationship table:
At first, delete integration linking relationship in original top layer linking relationship;
Then; Traveling through all sublayer linking relationships (comprising: the custom link relation of subject document 2.1, the custom link relation and the map linking relationship of sublayer outline 1_ subject document 1; Custom link relation in the map of sublayer also is the sublayer linking relationship; But deleted when upgrading linking relationship), this sublayer linking relationship is gone heavily to handle (the sublayer linking relationship in the embodiment of the invention does not have repetition);
Once more; Sublayer linking relationship after completion gone heavily to handle is integrated into the integration linking relationship; And judge in this sublayer linking relationship source subject document and purpose subject document whether in same map, if the linking relationship that then this source subject document and purpose subject document is constituted is labeled as interior relation; If not, the linking relationship that then this source subject document and purpose subject document is constituted is labeled as outer relation (as shown in the table):
| Source node | Destination node | Type |
| Subject document 2.1 | Subject document 1.1.2 | Interior relation |
| Subject document 2.1 | Subject document 2 | Interior relation |
| Subject document 2.1 | Subject document 2 | Interior relation |
| Subject document 2.1 | Outside _ subject document 1 | Outer relation |
| Sublayer outline 1_ subject document 1 | Outside _ subject document 1 | Outer relation |
At last; Linking relationship table management devices searches whether there is top layer custom link relation in the linking relationship table (top layer custom link relation is not set in the embodiment of the invention); If do not have, then directly will integrate the linking relationship table output (as the form of above-mentioned integration linking relationship shown in) of linking relationship as the DITA standard format.
Optional, in the process of carrying out the integration of linking relationship table,, the user integrates if selecting only internally to concern, and the integration relation that then obtains is as shown in the table:
| Source node | Destination node | Type |
| Subject document 2.1 | Subject document 1.1.2 | Interior relation |
| Subject document 2.1 | Subject document 2 | Interior relation |
| Subject document 2.1 | Subject document 2 | Interior relation |
In practical application, more integration condition can also be set, to satisfy user's different demands.Only the application scenarios in the embodiment of the invention is illustrated above, it is understandable that, in practical application, the more applications scene can also be arranged, specifically do not limit here with some examples.
Down the embodiment in the face of the linking relationship table management devices of the present invention that is used to carry out above-mentioned linking relationship table management method describes, and its logical organization please refer to Fig. 4, one embodiment comprises of link relation table management devices in the embodiment of the invention:
Acquiring unit 401 is used for obtaining the subject document that linking relationship table state changes;
Concern integrate module 4032, be used for deletion and integrate linking relationship; Obtain the sublayer linking relationship, and this sublayer linking relationship is gone heavily to handle; Sublayer linking relationship after going heavily to handle is copied in the linking relationship table, derive the linking relationship table.
The concrete reciprocal process in each unit is following in the embodiment of the invention linking relationship table management devices:
The state of the subject document in detecting the linking relationship table sends when changing, and acquiring unit 401 will obtain the subject document that state changes in the linking relationship table.The state of each subject document in the real-time detection linking relationship table of linking relationship table management devices in the embodiment of the invention; If (as: subject document is edited to have the state of subject document to change in the linking relationship table; Or subject document is deleted); Then linking relationship table management can be known at once, and obtains the relevant information of the subject document that this state changes, and carries out subsequent treatment.
After the subject document that the state of getting access to changes; Search unit 402 and search in the linking relationship table the relevant linking relationship (comprising: with this subject document is the linking relationship of source subject document, is the linking relationship of purpose subject document with this subject document) of subject document that all change with this state.
After finding relevant linking relationship; The update module 4031 that concerns of integral unit 403 is obtained the state change information that above-mentioned subject document takes place, if state variation is editor, judges whether the subject document of being edited has changed file header; If; Then use the peer link relation that the file header renewal above-mentioned steps 102 of this subject document is found after editing, if not, then do not upgrade this linking relationship; If state variation is deletion, delete the peer link relation that all above-mentioned steps 102 are found.Above-mentioned method according to state variation renewal linking relationship only is that some are given an example, and it is understandable that, in practical application, also has other state variation situation and the relevant operation of upgrading linking relationship, does not specifically limit here.
After having accomplished the renewal of peer link relation, concern integrate module 4032 at first, the original integration linking relationship in the Remove Links relation table; Then, obtain all sublayer linking relationships (comprising topic links relation and map linking relationship), and this sublayer linking relationship is gone heavily to handle; Optional; In the process of carrying out the integration of linking relationship table; Only can select the topic links relation is integrated, or only the sublayer map of topic links relation and ground floor integrated, in practical application, can supply the user to select the form that this process is arranged to option; The user selects suitable integration project according to self editor's needs, is convenient to operate intuitively; Once more; Sublayer linking relationship after completion gone heavily to handle copies the integration linking relationship to; And judge in this sublayer linking relationship source subject document and purpose subject document whether in same map, if the linking relationship that then this source subject document and purpose subject document is constituted is labeled as interior relation; If not, the linking relationship that then this source subject document and purpose subject document is constituted is labeled as outer relation.In embodiments of the present invention, the top layer linking relationship includes top layer custom link relation and integrates linking relationship.This integration linking relationship is that linking relationship table management devices is integrated user-defined sublayer linking relationship automatically and obtained, the interior linking relationship of top layer map that top layer custom link relation defines for the user voluntarily; At last; Obtain top layer custom link relation; And to this top layer custom link relation and integrate linking relationship and merge, according to the top layer custom link relation after merging and integrate the linking relationship table that linking relationship generates the DITA standard format, and derive with the XML file.
In several embodiment that the application provided, should be understood that the apparatus and method that disclosed can realize through other mode.For example, device embodiment described above only is schematically, for example; The division of said unit; Only be that a kind of logic function is divided, during actual the realization other dividing mode can be arranged, for example a plurality of unit or assembly can combine or can be integrated into another system; Or some characteristics can ignore, or do not carry out.Another point, the coupling each other that shows or discuss or directly coupling or communication to connect can be through some interfaces, the indirect coupling of device or unit or communication connect, and can be electrically, machinery or other form.
Said unit as separating component explanation can or can not be physically to separate also, and the parts that show as the unit can be or can not be physical locations also, promptly can be positioned at a place, perhaps also can be distributed on a plurality of NEs.Can realize the purpose of present embodiment scheme according to the needs selection some or all of unit wherein of reality.
In addition, each functional unit in each embodiment of the present invention can be integrated in the processing unit, also can be that the independent physics in each unit exists, and also can be integrated in the unit two or more unit.Above-mentioned integrated unit both can adopt the form of hardware to realize, also can adopt the form of SFU software functional unit to realize.
If said integrated unit is realized with the form of SFU software functional unit and during as independently production marketing or use, can be stored in the computer read/write memory medium.Based on such understanding; Part or all or part of of this technical scheme that technical scheme of the present invention contributes to prior art in essence in other words can come out with the embodied of software product; This computer software product is stored in the storage medium; Comprise some instructions with so that computer equipment (can be personal computer, server, the perhaps network equipment etc.) carry out all or part of step of the said method of each embodiment of the present invention.And aforesaid storage medium comprises: various media that can be program code stored such as USB flash disk, portable hard drive, ROM (read-only memory) (ROM, Read-Only Memory), RAS (RAM, Random Access Memory), magnetic disc or CD.
The above; Be merely embodiment of the present invention, but protection scope of the present invention is not limited thereto, any technician who is familiar with the present technique field is in the technical scope that the present invention discloses; Can expect easily changing or replacement, all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion by said protection domain with claim.
Claims (10)
1. a linking relationship table management method is characterized in that, comprising:
Obtain the subject document that state changes in the linking relationship table;
Search all linking relationships relevant in the said linking relationship table with said subject document;
Upgrade said linking relationship according to the state variation of said subject document, and reintegrate said linking relationship table.
2. method according to claim 1 is characterized in that, the state variation of said subject document comprises: editor and deletion.
3. method according to claim 2 is characterized in that, if said state variation is editor, then said state variation according to subject document is upgraded said linking relationship, comprising:
Judge whether said editor has changed the file header of said subject document, if, then use the said file header after editing to upgrade said linking relationship, if not, then do not upgrade said linking relationship.
4. method according to claim 2 is characterized in that, if said state variation is deletion, then said state variation according to subject document is upgraded said linking relationship, comprising:
Delete all linking relationships relevant with said subject document.
5. according to any described method of claim 1 to 4, it is characterized in that,
Said linking relationship table comprises: top layer linking relationship and sublayer linking relationship;
Said top layer linking relationship comprises: top layer custom link relation and integration linking relationship;
The said linking relationship table of reintegrating comprises:
Delete original integration linking relationship;
Obtain said sublayer linking relationship, and said sublayer linking relationship is gone heavily to handle;
Said sublayer linking relationship after going heavily to handle is copied in the linking relationship table, derive said linking relationship table.
6. method according to claim 5 is characterized in that,
Said said sublayer linking relationship after will going heavily to handle copies in the linking relationship table, derives said linking relationship table, comprising:
Said sublayer linking relationship after going heavily to handle is integrated into new integration linking relationship;
Obtain top layer custom link relation, said top layer custom link relation is the linking relationship of user-defined top layer;
Merge said top layer custom link relation and integrate linking relationship, top layer custom link relation after also will merging and integration linking relationship are derived as the linking relationship table.
7. method according to claim 6 is characterized in that, after said sublayer linking relationship is gone heavily to handle, comprising:
Judge in the linking relationship of said sublayer that source subject document and purpose subject document are whether in same outline map; If; The linking relationship that then said source subject document and purpose subject document is constituted is labeled as interior relation; If not, the linking relationship that then said source subject document and purpose subject document is constituted is labeled as outer relation.
8. method according to claim 5 is characterized in that, said sublayer linking relationship comprises:
Topic links relation and map linking relationship, said topic links relation is the linking relationship between user-defined each subject document, said map linking relationship is the linking relationship between the subject document in user-defined each sub-layer map;
The said said sublayer linking relationship that obtains comprises:
Obtain the topic links relation, and/or the map linking relationship.
9. a linking relationship table management devices is characterized in that, comprising:
Acquiring unit is used for obtaining the subject document that linking relationship table state changes;
Search the unit, be used for searching all linking relationships relevant of said linking relationship table with said subject document;
Integral unit is used for upgrading said linking relationship according to the state variation of said subject document, and reintegrates said linking relationship table.
10. device according to claim 9 is characterized in that, said integral unit comprises:
Concern update module, be used for if said state variation for editor, judges then whether said editor has changed the file header of said subject document, if, then use the said file header after editing to upgrade said linking relationship, if not, then do not upgrade said linking relationship; If said state variation is then deleted all linking relationships relevant with said subject document for deletion;
Concern integrate module, be used to delete original integration linking relationship; Obtain said sublayer linking relationship, and said sublayer linking relationship is gone heavily to handle; Said sublayer linking relationship after going heavily to handle is copied in the linking relationship table, derive said linking relationship table.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2011/075688 WO2012171165A1 (en) | 2011-06-13 | 2011-06-13 | Method for managing link relationship table and related device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102369527A true CN102369527A (en) | 2012-03-07 |
| CN102369527B CN102369527B (en) | 2013-12-04 |
Family
ID=45761453
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2011800011458A Expired - Fee Related CN102369527B (en) | 2011-06-13 | 2011-06-13 | Management method of link relation table and correlative device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102369527B (en) |
| WO (1) | WO2012171165A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109857764A (en) * | 2017-08-17 | 2019-06-07 | 天津数观科技有限公司 | Method, device and system for updating cache corresponding to database |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10372744B2 (en) | 2016-06-03 | 2019-08-06 | International Business Machines Corporation | DITA relationship table based on contextual taxonomy density |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070266040A1 (en) * | 2006-05-15 | 2007-11-15 | Figlin Oleg V | Architecture solution map builder |
| CN101136034A (en) * | 2007-09-30 | 2008-03-05 | 中兴通讯股份有限公司 | Controller or quick-speed chaining and method thereof |
| WO2009025264A1 (en) * | 2007-08-20 | 2009-02-26 | Nec Corporation | File management device, file management system, file management method, and program |
| CN101706804A (en) * | 2009-12-01 | 2010-05-12 | 百兴科技（苏州）有限公司 | Method for associated management of files in computer |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5842221A (en) * | 1997-02-19 | 1998-11-24 | Wisdomware, Inc. | Dynamic frequently asked questions (FAQ) system |
| US7526458B2 (en) * | 2003-11-28 | 2009-04-28 | Manyworlds, Inc. | Adaptive recommendations systems |
| US9652456B2 (en) * | 2008-04-25 | 2017-05-16 | International Business Machines Corporation | Automated relationship management for darwin information typing architecture |
-
2011
- 2011-06-13 WO PCT/CN2011/075688 patent/WO2012171165A1/en active Application Filing
- 2011-06-13 CN CN2011800011458A patent/CN102369527B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070266040A1 (en) * | 2006-05-15 | 2007-11-15 | Figlin Oleg V | Architecture solution map builder |
| WO2009025264A1 (en) * | 2007-08-20 | 2009-02-26 | Nec Corporation | File management device, file management system, file management method, and program |
| CN101136034A (en) * | 2007-09-30 | 2008-03-05 | 中兴通讯股份有限公司 | Controller or quick-speed chaining and method thereof |
| CN101706804A (en) * | 2009-12-01 | 2010-05-12 | 百兴科技（苏州）有限公司 | Method for associated management of files in computer |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109857764A (en) * | 2017-08-17 | 2019-06-07 | 天津数观科技有限公司 | Method, device and system for updating cache corresponding to database |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2012171165A1 (en) | 2012-12-20 |
| CN102369527B (en) | 2013-12-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102609402B (en) | Device and method for generation and management of ontology model based on real-time strategy | |
| CN102915237B (en) | The method and system of rewrite data quality rule is required according to user application | |
| JP5147952B2 (en) | System model conversion method, computer program, and system model conversion apparatus | |
| Auer et al. | A versioning and evolution framework for RDF knowledge bases | |
| JP4796185B2 (en) | Business flow diagram generation program, business flow diagram generation device, and business flow diagram generation method | |
| JP5159713B2 (en) | Automatic design apparatus, automatic design method and automatic design program for automatically designing design architecture of system components | |
| KR20210025024A (en) | System and method for data flow graph optimization | |
| CN104412227A (en) | Query-based software system design representation | |
| CN108021632B (en) | Mutual conversion processing method for unstructured data and structured data | |
| CN112015412A (en) | Device and method for generating business model based on form engine | |
| CN110532019A (en) | A kind of method of software code fragment history retrospect | |
| Dhyani et al. | Big data analytics using Hadoop | |
| CN101710274A (en) | Method and system for generating help information of application software | |
| JP2006172446A (en) | Complex data access | |
| CN112256238B (en) | Modeled demand item management method based on FMEA | |
| CN111078094A (en) | Distributed machine learning visualization device | |
| CN108874671A (en) | Testing case management, device, system and storage medium | |
| Paulus et al. | PLASMA: Platform for Auxiliary Semantic Modeling Approaches. | |
| JP5639417B2 (en) | Information processing apparatus, information processing method, and program | |
| CN102369527B (en) | Management method of link relation table and correlative device | |
| US9732593B2 (en) | Systems, methods, and computer medium to optimize storage for hydrocarbon reservoir simulation | |
| JP2023553220A (en) | Process mining for multi-instance processes | |
| US20230229853A1 (en) | Systems and methods for translation comments flowback | |
| JP2003114881A (en) | System for controlling and monitoring process | |
| CN101017454A (en) | Editing device and method, program, and recording medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20131204 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |