JP3619015B2 - Structured document processing method - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a structured document processing method for processing a document having a structure, and in particular, when creating a structured document, not only a structured document input screen is generated from a document type definition but also input to a structured document. Restricting the value to be displayed, highlighting only the changed part when the structured document is changed, and changing another shared structured document when the structured document is changed The present invention relates to a structured document processing method that is made possible.
[0002]
[Prior art]
Conventionally, structured documents in which structured concepts are incorporated into documents are used, and structured document processing methods for handling these structured documents have been developed. As a typical international standard for structured documents, there is a document description language SGML (ISO 8879: Standard Generalized Markup Language).
[0003]
In such a structured document, restrictions on the structure of the document are described. In SGML, document type definition (DTD: Document)
This is referred to as Type Definition).
[0004]
As a technique for automatically generating a structured document from a document type definition, (1) Japanese Patent Laid-Open No. 9-128400 “Structured Document Generation Device”, (2) Japanese Patent Laid-Open No. 9-69101 “Structured Document Generation Method and Device” And (3) Japanese Patent Laid-Open No. 5-108631 "Document Processing Apparatus".
[0005]
Among these, (1) is a method of dividing the document image into regions based on the correspondence between the document image region described in the document type definition in advance and the document structure element, and the result of character recognition of each region is the contents of the document structure element Thus, the present invention relates to an apparatus for generating a structured document from a document type definition and a document image.
[0006]
(2) specifies the document structure element by pattern matching the text position, size and character string obtained by layout analysis and syntax analysis of the unstructured document with the structured document generation rule described in the document type definition. The present invention relates to a method and apparatus for generating a structured document by inference.
[0007]
(3) relates to a structured document editing apparatus that presents a minimum structure and possible structure candidates from a document type definition, and generates a structured document by interactively adding the structure.
[0008]
As a technique for checking the contents when inputting a structured document, there is (4) Japanese Patent Laid-Open No. 8-16589 “Structured Document Processing Device”. (4) relates to an apparatus for checking document contents by applying check conditions defined in advance for each document structure element to the document structure element contents.
[0009]
Further, as a technique for unifying contents among a plurality of documents, there is (5) Japanese Laid-Open Patent Publication No. 4-21865 “Standard Document Creation Support Method”. (5) In a document system in which a plurality of standard documents such as specifications and forms are related, the relationship is input and stored in a computer in advance, and the standard is created by referring to the relationship when creating the standard document. The present invention relates to a method of automatically updating an item associated with the item when the item of the document is updated.
[0010]
Further, as techniques for extracting and highlighting differences between a plurality of documents, (6) Japanese Patent Laid-Open No. 8-50590 “Document Processing Method and Apparatus” and (7) Japanese Patent Laid-Open No. 8-329079 “Structured”. Document difference extraction method and apparatus ".
[0011]
(6) relates to a method and an apparatus for presenting whether or not a document has been changed between a user's previous reference and this reference.
[0012]
(7) relates to a method and apparatus for comparing document structures between a plurality of structured documents to extract document structure differences and extracting document structure content differences when the document structures match.
[0013]
[Problems to be solved by the invention]
However, in the above-described technology for automatically generating a structured document from the document type definition, in (1) and (2), a paper document and an unstructured document that are the basis of the structured document exist, respectively, or in advance Must be created. Therefore, when creating a new structured document, a paper document or unstructured document that is the source of the structured document must be created in advance, and the structured document is converted from the paper document or unstructured document. There is a problem that the conversion error at the time of generation must be corrected and the efficiency is low.
[0014]
On the other hand, in (3), since the document creator must construct the document structure interactively, there is a problem that the document creator cannot use the document structure unless the document creator has acquired knowledge about the document structure in advance.
[0015]
Further, in the technique (4) for checking the contents when the structured document is input, an error in the contents of the document structure element can be detected for each document structure element, but a contradiction among a plurality of document structure element contents cannot be detected. was there.
[0016]
Further, in the technique (5) for unifying contents among a plurality of documents described above, by associating document structure elements of a plurality of structured documents, it is guaranteed that the contents of the related document structure elements are always the same. Yes, but there is a problem that the contents cannot be dealt with when the contents of the related document structure elements are not the same. Further, the related document structure elements must be one-to-one, and the object of association is limited to structured documents. That was the problem.
[0017]
In the technique for extracting and highlighting the differences between the plurality of documents, in (6), since the reference time and update time of the document are compared, it is determined that the document has been updated even if the document contents are the same. In addition, there is a problem that it is impossible to indicate which part of the document has been updated.
[0018]
In (7), since a difference in document structure and a difference in document structure element contents are extracted from a plurality of structured documents, it is possible to present which part of the document has been updated. There was a problem that it had to be specified every time.
[0019]
The present invention has been made to solve the above-described problems. A structured document can be defined for each job, and a structured document can be correctly input. It is another object of the present invention to provide a structured document processing method capable of easily referring to a document and sharing a plurality of structured documents.
[0020]
[Means for Solving the Problems]
A structured document processing method according to the present invention includes:Process structured documents with structureIn the structured document processing method, a structured document input step of generating a structured document input screen based on the document type definition and creating a structured document entity from the structured document input value input from the structured document input screen A structured document input value checking step for checking whether the structured document input value input from the structured document input screen satisfies a preset constraint, and the structured document entity is prepared in advance. A structured document change location display step for distinguishing and displaying the change location of the structured document entity by comparing with the compared structured document entity, and when the structured document entity is created or changed, Steps for linking shared structured documents that change related items of shared structured documents shared with users, Sharing data with the structured document entity, but not in a structured document format, sharing with a specified correspondence relationship with the structured document entity NDATA The entity is created or changed in accordance with the creation or change of the structured document entity, and the shared NDATA Sharing to create or change the structured document entity according to the creation or modification of the entity NDATA Change step andIt has.
[0021]
The structured document input step includes a structured document generation finite automaton creation step for creating a structured document generation finite automaton from a document type definition or a document type definition and a structured document entity, and a structured document generation finite automaton. By following the steps, a structured document input screen generation step for generating a structured document input screen, and a structured document creation step for generating a structured document entity from the structured document input value input to the structured document input screen And have.
[0022]
Also,Specified from structured document input screenInter-element relative positional relationship storage step for storing the relative positional relation between elements, and reading the relative positional relation between elements, and creating the element input positional relative data of the structured document input screen according to the relative positional relation between elements The structured document input screen generation step generates the structured document input screen based on the element input position arrangement data.
[0023]
Also,Pre-specified from the structured document input screenAn element selection value storage step for storing the element selection value; and an element selection value candidate creation step for creating an element selection value candidate for the structured document input screen according to the element selection value. The structured document input screen generation step includes: The structured document input screen including the element selection value candidates is generated.
[0024]
Also,Pre-specified from the structured document input screenAn element repetition number storage step for storing the element repetition number; and a repetition element creation step for generating a repetition element of the structured document input screen according to the element repetition number. The structured document input screen including the above is generated.
[0025]
Also,Requirement that is the orientation of the specified repeat elementA structured document input screen generating step, wherein the structured document input screen generating step includes the repeated element, the element repeated direction storing step storing the element repeating direction, and the element repeating element arranging step arranging the repeated element in the element repeating direction. Generate an input screen.
[0026]
Also,Key points in the previously specified structured document entityAn element constraint storage step for storing elementary constraints; and an element constraint check step for checking whether the structured document input value input to the structured document input screen in the structured document input step satisfies the element constraints; Have
[0027]
Also,Multiple elements of the structured document entity specified in advanceInter-element constraint check for checking whether the structured document input value input to the structured document input screen in the structured document input step at the inter-element constraint storing step for storing the inter-element constraint satisfies the above-mentioned inter-element constraint. Step andTheHave.
[0028]
Also,The element in the structured document entity specified in advanceIn the element discrete value constraint storage step for storing element discrete value constraints and the structured document input step, the structured document input value input to the structured document input screen is set to the closest value satisfying the element discrete value constraint. An element discrete value correction step to be corrected; andTheHave.
[0029]
Further, a structured document change location extraction step for extracting a difference between the structured document entities by comparing the structured document entity with the comparison target structured document entity, and adding the first highlight character control code to the difference A structured document change location highlighting step, and the structured document change location display step highlights and displays the difference on the structured document display screen based on the creation data of the structured document change location highlighting step.
[0030]
Also, the structured document entity before input is saved as a comparison target structured document entity, and the difference between the structured document entities is edited as a comparison portion by comparing the comparison target structured document entity with the structured document entity being input. There is a structured document editing part extracting step for extracting, and a structured document editing part highlighting step for adding the second highlight character control code to the editing part. Based on the data created in the document edit location highlighting step, the edit location is highlighted on the structured document display screen.
[0031]
Also, the structure document entity to be input and the version immediately before or the specified version of the structured document entity to be referenced are stored as a comparison target structured document entity, and the comparison target structured document entity and the structured document entity to be input are referred to. A structured document revision location extraction step for extracting a difference between structured document entities as a revised location by comparing the structured document entity, and a structured document revision that adds a third highlight character control code to the revised location A structured document change location display step that highlights and displays the revised location on the structured document display screen based on the creation data of the structured document revised location enhancement display step.
[0032]
Also,Create / change data of a shared structured document entity in which data is shared with the structured document entity and the correspondence between the elements is specified.Along with the creation or modification of the above structured document entitymake,The shared structured document entity has a shared structured document change step for creating the structured document entity creation / change data in accordance with the creation or change of the shared structured document entity. Based on the change data, the related items of the structured document entity and the shared structured document entity are changed.
[0034]
DETAILED DESCRIPTION OF THE INVENTION
Embodiment 1 FIG.
First, in the first embodiment of the present invention, a workflow document that inputs a structured document, checks a value input to the structured document, displays a changed portion of the structured document, and cooperates with other structured documents. The operation will be described with reference to the drawings. FIG. 1 is a flowchart for explaining the operation of the first embodiment of the present invention.
[0035]
First, in the structured document input step 1, the document type definition 5 and the structured document entity 8 are read, and a structured document input screen 6 is generated and presented to the document input person. Here, the structured document entity 8 is, for example, a structured document entity 8 in which a structured document input value for correcting and using an item has already been input.
[0036]
For example, FIG. 15 shows an example in which a document type definition 5 of a specification for building a house is described according to the SGML format. An example of the structured document entity 8 described according to the document type definition 5 is shown in FIG. The document type definition 5 is data defining the logical structure of the document. For example, <! ELEMENT Roof (roof shape, roof type, roof color)> is described in the document structure element “roof”, there are three document structure elements of “roof shape”, “roof type” and “roof color” Is shown.
[0037]
Then, the structured document input step 1 reads the document type definition 5 shown in FIG. 15 to obtain the logical structure of the document and the document structure element to be input. Further, the structured document entity 8 shown in FIG. By reading, the contents of the already input document structure element are acquired, and the structured document input screen 6 shown in FIG. 16 is generated.
[0038]
Then, when the document input person A inputs the structured document input value 7 to each input frame of the structured document input screen 6, the structured document input value 7 is sequentially checked and checked by the structured document input value check step 2. If it passes, the structured document entity 8 is updated or newly created. For example, when the structured document entity 8 shown in FIG. 18 is read and “delivery date” is changed to “1998/12/20” and “constructor” is changed to “Mitsubishi Shiro”, the structure shown in FIG. Updated to the documentized document entity 8.
[0039]
Next, in the structured document change location display step 3, the updated structured document entity 8 and the comparison target structured document entity 9 prepared in advance are read, and the changed location is highlighted on the structured document display screen 10. To display. That is, the changed part is displayed separately from other input items. The comparison target structured document entity 9 may be, for example, the structured document entity 8 before update. Here, when the structured document entity 8 before update shown in FIG. 18 is the comparison-target structured document entity 9, the updated structured document entity 8 is the one shown in FIG. The structured document display screen 10 shown in FIG. 19 is displayed with the “delivery date” and “constructor” highlighted.
[0040]
In the shared structured document interlinking step 4, the shared structured document entity 11 associated with the updated structured document entity 8 is updated according to the update result of the structured document entity 8. Here, FIG. 17 is the updated structured document entity 8, FIG. 20 is the associated shared structured document entity 11, and the document structure elements “order number”, “property address”, “current address”, “ “Name”, “Delivery”, and “Sales” are respectively associated with the document structure elements “Order Number”, “Property Address”, “Current Address”, “Name”, “Delivery”, and “Sales” in FIG. Then, since the “delivery date” has been updated, the document structure element “delivery date” in FIG. 20 is updated to 1998/12/20.
[0041]
In the structured document processing method having such a process, the workflow from the document input by the document input person A to the confirmation of the document content by the document checker C is performed using the structured document as a medium, and the document type definition 5 The structured document input screen 6 can be generated from the above, the input value 7 can be checked, and the changed part can be displayed. Further, when an incorrect input is made, it is possible to present to the document input person A that the input is incorrect and to correct the incorrect input again. Furthermore, when a document is shared with another user D, the update result of the document can be reflected in the shared document.
[0042]
In the structured document input step 1, when the structured document entity 8 which is the contents of the already input document structure element is not read, the structured document input screen 6 in which no input items are input is generated.
[0043]
Embodiment 2. FIG.
Next, in the second embodiment of the present invention, operations for inputting a document type definition, creating a structured document generation finite automaton, and generating a structured document input screen will be described with reference to the drawings. FIG. 2 is a flowchart for explaining the operation of the second embodiment of the present invention. Parts that are the same as or correspond to those in the first embodiment are given the same reference numerals, and descriptions thereof are omitted. In FIG. 2, a structured document generation finite automaton creation step 12 reads a document type definition 5 and creates a structured document generation finite automaton 15.
[0044]
Next, the structured document input screen generation step 13 generates the structured document input screen 6 by following the order of the structured document generation finite automaton 15. The document input person A inputs the structured document input value 7 on the structured document input screen 6, and the structured document generation step 14 creates a structured document entity 8 using the value. Further, in the document type definition 5, a document structure element content definition illustrated in FIG. 21 is described.
[0045]
The above-described document structure element content definition is data specifying the type of the input document structure element. In FIG. 21, for example, <! —CONTENT NUMBER (#NUMBER, N) — From the above, it can be seen that the type of the document structure element “floor” shown in FIG. 15 is a single-digit integer. The format of the document structure element content definition is <! -CONTENT Document structure element identifier LABEL (heading) TYPE (type name, type option)-> The heading of the input frame is specified by LABEL (heading). If omitted, the document structure element identifier is used as the heading.
[0046]
Also, type names in TYPE (type name, type option) are: #ORDERNUM is a text that specifies the character type in character units by type option, #ADDRESS is a text that inputs an address, #NAME is a text that inputs a name, # DATE specifies the format with the type option and enters the date, #NUMBER specifies the format with the type option and the numeric input text, #SELECT selects from the multiple candidates specified with the type option This indicates that the text, the text for inputting the file name of the external entity referenced by #LINK, and #TEXT are arbitrary text.
[0047]
In the type option of type name #ORDERNUM, A is one letter, N is one number, and the other symbols are one letter, and in the type option of type name #DATE, Y is one digit of the year, M Is the first digit of the month, D is the first digit of the day, and the other symbols are the same one character. The first type option of type name #NUMBER specifies that N is one digit and the period is the decimal point. The second type option specifies the unit, and the type option of type name #SELECT specifies a list of selectable text separated by commas and enclosed in parentheses, and the first type of type name #TEXT The option specifies the number of lines in the input box, the second type option specifies the number of digits in the input box, and the third type option specifies whether the input box scrolls. To.
[0048]
Then, as a result of reading the document type definition 5, the structured document generation finite automaton creation step 12 and the structured document input screen generation step 13 acquire the logical structure of the document and the type of the document structure element to be input. The structured document input screen 6 illustrated in FIG.
[0049]
In the structured document processing method having such steps, the document input person A may input the contents of each document structure element on the structured document input screen 6 in a specified format without being aware of the document structure. Therefore, it is possible to create a structured document entity 8 that has no document structure error and no document structure element content format error.
[0050]
Embodiment 3 FIG.
Next, a third embodiment of the present invention will be described with reference to the drawings. FIG. 3 is a flowchart for explaining the operation of the third embodiment of the present invention. Portions that are the same as or correspond to those in Embodiment 2 are given the same reference numerals, and descriptions thereof are omitted. In FIG. 3, in the inter-element relative positional relationship specifying step 16, the document manager B specifies the relative positional relationship between the elements on the structured document input screen 6 using the dialog interface illustrated in FIG.
[0051]
In FIG. 23, the document structure hierarchy display window 58 represents the hierarchical relationship of document structure elements with a line as shown between the document structure node icon 60 and the document structure node icon 63. When the document manager selects the document structure node icon 60 with a pointing device such as a mouse and moves it to the inter-element relative position designation window 59, the document structure node icon 61 is displayed. Similarly, when the document structure node icon 63 is moved to the element relative position relative designation window 59, the document structure node icon 64 is displayed.
[0052]
At this time, when the document structure node icon 64 is arranged so as to be positioned to the right of the document structure node icon 61 and an arrow from the document structure node icon 61 to the document structure node icon 64 is displayed, the document structure node icon 64 indicates. The input frame of the document structure element “designer” can be specified so as to be arranged relatively to the right when viewed from the input frame of the document structure element “sales person” indicated by the document structure node icon 61. Further, when the heading icon 62 is arranged on the document structure node icon 61 and the content of the heading icon 62 is “sales”, the heading icon 62 is relatively viewed from the input frame of the document structure element “business person” indicated by the document structure node icon 61. In particular, the heading “Sales” can be placed above.
[0053]
In the inter-element relative positional relationship storage step 17, the inter-element relative positional relationship 19 specified as described above in the inter-element relative positional relationship specifying step 16 is stored in a storage device such as a magnetic disk device.
[0054]
FIG. 24 shows an example of the relative positional relationship 19 between the elements. For example, in the description of LABEL (sales, U) for the document structure element “sales”, the heading of the document structure element “sales” is “sales” and the relative It is shown to be placed on the top. In addition, the description of LABEL (design, U) for the document structure element “designer” indicates that the heading of the document structure element “designer” is “design” and is positioned relatively above. The description of (sales, R) indicates that the document structure element “designer” is arranged relatively to the right as viewed from the document structure element “sales person”.
[0055]
Further, the element input position relative arrangement step 18 reads the relative positional relationship between the document structure elements specified by the inter-element relative positional relationship 19 from the storage device and transfers it to the structured document input screen generation step 13. Thus, the structured document input screen 6 shown in FIG. 25 is generated. In FIG. 25, the document structure elements “sales person”, “designer”, and “constructor” are arranged in the right direction in this order, respectively, and the headings “sales”, “design”, and “construction” are arranged above. I understand that
[0056]
In the structured document processing method having such steps, the document manager B can designate the relative positional relationship 9 between the elements, so that the document input person A is structured in which the input frame is optimally arranged according to the business. A structured document can be input using the document input screen 6.
[0057]
Embodiment 4 FIG.
Next, a fourth embodiment of the present invention will be described with reference to the drawings. FIG. 4 is a flowchart for explaining the operation of the fourth embodiment of the present invention. Portions that are the same as or correspond to those in Embodiment 2 are given the same reference numerals, and descriptions thereof are omitted. 4, in the element selection value designation step 20, the document manager B designates the selection value of the document structure element content using the dialog interface illustrated in FIG. In FIG. 26, an element selection value designation list 65 is an element selection value 23 designated by the document manager B as a content candidate for the document structure element “sales”.
[0058]
In the element selection value storage step 21, the element selection value 23 specified in the element selection value specification step 20 is stored in a storage device such as a magnetic disk device. FIG. 27 shows an example of the element selection value 23. The description of TYPE (#SELECT, (Mitsubishi Taro, Taro Shihishi, Taro Gohishi)) for the document structure element “sales” is the contents of the document structure element “sales”. Indicates one of the selection values of “Mitsubishi Taro”, “Taro Shihishi”, or “Taro Gohishi”.
[0059]
Further, in the element selection value candidate creation step 22, the selection value of the document structure element content designated by the element selection value 23 is read from the storage device to create an element selection value candidate, and this element selection value candidate is input to the structured document. Transfer to screen generation step 13. The structured document input screen generation step 13 generates the structured document input screen 6 shown in FIG. 28 including the element selection value candidates. In FIG. 28, when the document input person A tries to input the contents of the document structure element “sales person” with a pointing device such as a mouse, the element selection value candidates of the document structure element “sales person” are displayed by the pull-down menu. The
[0060]
In the structured document processing method having such a process, the element selection value 23 can be designated by the document manager B, so that the document input person A selects from among correct input value candidates determined according to the business. By doing so, a structured document can be input, and input errors can be prevented.
[0061]
Embodiment 5. FIG.
Next, a fifth embodiment of the present invention will be described with reference to the drawings. 5 and 6 are flowcharts for explaining the operation of the fifth embodiment of the present invention. Portions that are the same as or correspond to those in Embodiment 2 are given the same reference numerals, and descriptions thereof are omitted. In the figure, the element repetition number designation step 24 and the element repetition direction designation step 28 are performed by the document manager B in the repetition number designation box 66 using the dialog interface illustrated in FIG. The repeat number is designated, and the repeat direction is designated in the repeat direction designation box 67.
[0062]
In FIG. 29, “2” specified in the repetition number specification box 66 indicates that the number of repetitions of the document structure element “floor” is two, and “R” specified in the repetition direction specification box 67 is This indicates that the repetition direction of the document structure element “floor” is to the right. Here, the value of the repetition direction is “U” on the top, “D” on the bottom, “L2” on the left, and “R” on the right. Similarly, a repeat number designation box and a repeat direction designation box are also displayed for the document structure element “room”. According to FIG. 15, the document structure element “room” is a lower element of the document structure element “floor”. Therefore, two repetition number designation boxes for the document structure element “room” are displayed. The example of FIG. 29 shows that there are five rooms on the first floor and three rooms on the second floor.
[0063]
The element repetition number storage step 25 and the element repetition direction storage step 29 store the element repetition number 27 and the element repetition direction 31 in a storage device such as a magnetic disk device, respectively.
[0064]
Further, the repeated element creation step 26 and the repeated element placement step 30 respectively read the repeated element number 27 and the repeated element direction 31 from the storage device and transfer them to the structured document input screen generation step 13, so that FIG. A structured document input screen 6 including the repetitive element shown is generated.
[0065]
FIG. 30 shows an input screen for the document structure element “room type”. The document structure element “floor” is repeated twice in the right direction, and the document structure element “room” is repeated three times in the downward direction. There are five rooms on the first floor: “living room”, “reception”, “kitchen”, “bath” and “toilet” on the first floor, “living room”, “sleeping” and “ It is input that there are three rooms “sleep”.
[0066]
In the structured document processing method having such steps, the document manager B can specify the number of element repetitions and the element repetition direction on the structured document input screen 6, so that the document input person A can repeat document structure elements. Since the structured document can be referred to in the form of a meaningful table according to the business, the overall view is improved and the input is facilitated, and input errors can be prevented.
[0067]
Embodiment 6 FIG.
Next, a sixth embodiment of the present invention will be described with reference to the drawings. 7, 8 and 9 are flowcharts for explaining the operation of the sixth embodiment of the present invention. Parts that are the same as or correspond to those in the first embodiment are given the same reference numerals, and descriptions thereof are omitted. The element constraint specifying step 32, the inter-element constraint specifying step 36, and the element discrete value constraint specifying step 40 specify the element constraint 35, the inter-element constraint 39, and the element discrete value constraint 43, respectively, using the dialog interface. FIG. 31 is an example of the element constraint 35, FIG. 32 is an example of the inter-element constraint 39, and FIG. 35 is an example of the element discrete value constraint 43.
[0068]
In the element constraint 35 shown in FIG. 31, when the value indicated by each content of a plurality of document structure elements “room area” is changed, the value indicated by the content of the document structure element “building area” is not exceeded. If the element constraint that presents a message as shown in FIG. 33 to the document input person A when the constraint is violated and the value indicated by the content of the document structure element “roof type” is changed, the document structure Check the constraint that the element “roof shape” is not “triangular” and the document structure element “roof type” must not be “tile”, and if the constraint is violated, the content of the document structure element “roof shape” The element constraint is changed to “triangle” and presents a message “The roof shape is triangular” to the document input person A.
[0069]
Further, in the inter-element constraint 39 shown in FIG. 32, the sum of the values indicated by all the contents of each floor of the document structure element “room area” that is present does not exceed the value indicated by the contents of the document structure element “building area”. When the constraint is checked and the constraint is violated, the inter-element constraint that presents a message as shown in FIG. 34 to the document input person A and the number of document structure elements “rooms” that exist in plural are the document structure element “number of rooms” ”Is checked for a constraint that the content must match the value indicated, and when the constraint is violated, the document input person A is presented with a message“ The number of rooms does not match. ” .
[0070]
Furthermore, in the element discrete value constraint 43 shown in FIG. 35, the value indicated by each content of a plurality of document structure elements “floor height” is one of the discrete values “210, 220, 240, 270”. When the constraint is violated, a dialogue message as shown in FIG. 36 is presented to the document input person A when the restriction is violated, and when the document input person A requests, the current of the document structure element “floor height” is displayed. The element discrete value constraint for correcting the value indicated by the content to the nearest discrete value and the value indicated by each content of the plurality of document structure elements “room area” are discrete values “14.85, 19.8, 26.4. , 39.6 "is checked, and when the constraint is violated, a dialog message" Do you want to correct the room area to the standard value? " If A asks, sentence It represents an element discrete value constraints to correct the value indicated by the current contents of the structural element "Room Size" to the nearest discrete value.
[0071]
The element constraint storage step 33, the element constraint storage step 37, and the element discrete value constraint storage step 41 store the element constraint 35, the element constraint 39, and the element discrete value constraint 43 in a storage device such as a magnetic disk device, respectively. .
[0072]
Further, an element constraint check step 34, an inter-element constraint check step 38, and an element discrete value correction step 42 read the element constraint 35, the inter-element constraint 39, and the element discrete value constraint 43 from the storage device, respectively, and check the check for the constraint. .
[0073]
In the structured document processing method having such steps, the document manager B can specify element constraints, inter-element constraints, and element discrete value constraints, so that the document input person A can input values determined according to the business. Therefore, it is possible not only to prevent input errors, but also to use standard products by adopting designed discrete values, so that design costs and manufacturing costs can be reduced.
[0074]
Embodiment 7 FIG.
Next, a seventh embodiment of the present invention will be described with reference to the drawings. 10, 11 and 12 are flowcharts for explaining the operation of the seventh embodiment of the present invention. Parts that are the same as or correspond to those in the first embodiment are given the same reference numerals, and descriptions thereof are omitted. In the figure, a structured document change location extraction step 44 reads the structured document entity 8 and the comparison target structured document entity 9 and extracts a change location with the structured document entity 8 as positive. Further, the structured document change location highlighting step 45 adds a first highlight character modification control code for highlighting them to the change locations extracted by the structured document change location extraction step 44 to change the structured document. Passed to location display step 3.
[0075]
The structured document change location display step 3 interprets the highlighted character modification control code added by the structured document change location highlighting step 45, and the structured document highlights the changed location on the structured document display screen 10. Is displayed. For example, if the structured document entity 8 that is positive is FIG. 17 and the compared structured document entity 9 is FIG. 18, the document structure element “Delivery” and the document structure element “Constructor” are indicated in bold and underlined, for example. The structured document display screen 10 shown in FIG.
[0076]
Further, in the workflow from the document input by the document input person A to the confirmation of the document content by the document checker C, a structured document from which a change part is extracted can be defined according to the business. That is, in FIG. 11, when the document input person A inputs a document, the structured document edit location extraction step 46 saves the structured document before input as the comparison target structured document entity 9, and creates the structure created after the input. The changed document is extracted by passing the structured document as a positive structured document entity 8 to the structured document change location extraction step 44 after the input is completed or during the input, and the structured document edit location highlighting step 47 further includes: The highlighted character modification control code added in the structured document change location highlighting step 45 is changed to another second highlighted character modification control code indicating the edited location.
[0077]
In FIG. 12, the structured document revision location extraction step 48 saves the structured document confirmed by the document checker C in the past as the comparison target structured document entity 9, and corrects the structured document to be confirmed now. The revised document is extracted by passing it to the structured document change location extraction step 44 as the structured document entity 8 to be, and the structured document revision location highlighting step 49 is added in the structured document change location highlighting step 45. The highlighted character modification control code is changed to another third highlighted character modification control code indicating the revised location.
[0078]
In the structured document processing method having such a process, the changed part is highlighted and displayed, so that the document input person A and the document checker C can easily grasp the changed part of any two structured documents. can do. Furthermore, since the document manager B defines the structured document to be compared according to the business, the document input person A and the document checker C can easily grasp the edited part and the revised part, respectively.
[0079]
Embodiment 8 FIG.
Next, an eighth embodiment of the present invention will be described with reference to the drawings. 13 and 14 are flowcharts for explaining the operation of the eighth embodiment of the present invention. Parts that are the same as or correspond to those in the first embodiment are given the same reference numerals, and descriptions thereof are omitted. In FIG. 13, a shared structured document designation step 50 designates a plurality of structured documents to be shared. Also, in the correspondence specification step 51 between structured document elements, the correspondence between the document structure elements of a plurality of structured documents to be shared is specified. Furthermore, in the structured document element content correspondence specifying step 52, the correspondence relationship between the document structural elements of a plurality of structured documents to be shared is specified.
[0080]
Then, the shared structured document change step 53 acquires the shared structured document entity 11 shared with a certain structured document entity 8 from the specification of the shared structured document specification step 50 when a certain structured document entity 8 is changed, Further, the document structure element of the shared structured document entity 11 corresponding to the changed portion is acquired from the specification of the structured document element correspondence specifying step 51, and further the document structure element of the shared structured document entity 11 corresponding to the changed portion. Is changed in accordance with the specification in the structured document element content correspondence specifying step 52, and is passed to the shared structured document interlinking step 4.
[0081]
Here, FIG. 17 is the structured document entity 8 of the change source, FIG. 20 is the shared structured document entity 11 associated by the shared structured document specifying step 50, and the document structure element “order number” in FIG. “Property address”, “Current address”, “Name”, “Delivery date”, “Sales person” are respectively changed to the document structure elements of FIG. 20, “order number”, “Property address”, If it is associated with “current address”, “name”, “delivery date”, and “sales person”, the document structure element “delivery date” is updated, so that it is designated by the structured document element content correspondence designation step 52. The document structure element “Delivery date” in FIG. 20 is changed to “1998/12/20” based on the correspondence between the contents of the document structure elements.
[0082]
Further, the correspondence between document structure elements may be a correspondence between one document structure element and a plurality of document structure elements, and furthermore, a correspondence between a plurality of document structure elements and a plurality of document structure elements. Alternatively, the correspondence between the contents of the document structure elements may be different. For example, if "product name" is described in the source structured document and the structured document shared with it is a product specification, or if the "product name" in the source structured document is changed A plurality of product specification items of the structured document shared with it are changed to values specified by the product name.
[0083]
Further, the shared document may not be a structured document. Here, an entity that is not a structured document is called an NDATA entity. In FIG. 14, a shared NDATA specifying step 55 specifies a plurality of shared NDATA entities 54 to be shared with the structured document, and a shared inter-NDATA correspondence specifying step 56 is a content of the plurality of shared NDATA entities 54 to be shared with the structured document. Specify the correspondence of. In the shared NDATA changing step 57, when a certain structured document entity 8 is changed, the shared NDATA entity 54 shared with the entity is acquired from the specification in the shared NDATA specifying step 55, and the shared NDATA entity 54 corresponding to the changed part is obtained. The change method is acquired from the specification in the shared NDATA correspondence specifying step 56, and the shared NDATA entity 54 is changed. Conversely, when the shared NDATA entity 54 is changed, the contents of the document structure element corresponding to the changed portion of the structured document entity 8 shared with the shared NDATA entity 54 are changed. For example, when the change source structured document is a product specification and the shared NDATA entity shared with it is a drawing, when the case number of the specification of the change source product is changed, the case in the drawing shared with it is changed. The width, height, and depth of the body dimensions are changed to values specified by the housing number.
[0084]
In the structured document processing method having such a process, the document manager B designates the correspondence between the structured document and another structured document or another NDATA according to the business. Is changed, another structured document shared with it or another user D referring to another NDATA can refer to the result reflecting the change of the original structured document.
[0085]
【The invention's effect】
A structured document processing method according to the present invention includes:Process structured documents with structureIn the structured document processing method, a structured document input step for generating a structured document input screen based on the document type definition and creating a structured document entity from the structured document input value input from the structured document input screen; , A structured document input value check step for checking whether a structured document input value input from the structured document input screen satisfies a preset constraint, a structured document entity and a comparison target prepared in advance A structured document change location display step for distinguishing and displaying the change location of the structured document entity by comparing with the structured document entity, and sharing with other users when the structured document entity is created or changed A shared structured document interlinking step for changing a related item of the shared structured document to be performed;Sharing data with a structured document entity, but not a structured document format, but sharing with a specified relationship between structured document entities NDATA The entity is created or changed in accordance with the creation or change of the structured document entity, and the shared NDATA Sharing to create or modify structured document entities according to entity creation or modification NDATA Change step.Therefore, in the workflow using a structured document as a medium from the document input by the document input person to the confirmation of the document content by the document checker, the generation of the structured document input screen from the document type definition, the input value check, and the change location Display is possible. Furthermore, when an incorrect input is made, the fact that the input is incorrect is presented to the document input person, and the erroneous input can be corrected again. Furthermore, when a document is shared with other users, the update result of the document can be reflected in the shared document.In addition, document managers can use structured documents and other NDATA Specify a correspondence relationship with and, when a structured document is changed, NDATA Other users referring to can refer to the result reflecting the change of the original structured document.
[0086]
The structured document input step includes a structured document generation finite automaton creation step for creating a structured document generation finite automaton from a document type definition or a document type definition and a structured document entity, and a structured document generation finite automaton. By following the steps, a structured document input screen generation step for generating a structured document input screen, and a structured document creation step for generating a structured document entity from the structured document input value input to the structured document input screen And have. Therefore, the document input person need only input the contents of each document structure element on the structured document input screen in the specified format without being conscious of the document structure. A structured document entity 8 without a format error can be created.
[0087]
Also,Specified from structured document input screenInter-element relative positional relationship storage step for storing the relative positional relation between elements, and reading the relative positional relation between elements, and creating the element input positional relative data of the structured document input screen according to the relative positional relation between elements The structured document input screen generation step generates a structured document input screen based on the element input position arrangement data. As a result, the relative positional relationship between elements can be specified by the document administrator, so that the document input person inputs the structured document using the structured document input screen in which the input frame is optimally arranged according to the business. Can do.
[0088]
Also,Pre-specified element selection values from the structured document input screenAn element selection value storage step for storing, and an element selection value candidate creation step for creating an element selection value candidate for the structured document input screen according to the element selection value. The structured document input screen generation step includes an element selection value candidate. Generate a structured document input screen including As a result, since the element selection value can be specified by the document manager, the document input person can input the structured document by selecting from the correct input value candidates determined according to the business. Input errors can be prevented.
[0089]
Also,Pre-specified from the structured document input screenAn element repetition number storage step for storing the element repetition number; and a repetition element creation step for generating a repetition element of the structured document input screen according to the element repetition number. The structured document input screen generation step includes a repetition element. Generate a structured document input screen. As a result, the document manager can specify the number of element repetitions on the structured document input screen, so that the document input person can refer to the structured document in the form of a meaningful table according to the business of the repeated document structure elements. Therefore, the overall view is improved and not only the input becomes easy, but also an input error can be prevented.
[0090]
Also,The direction of the specified repeating elementA structured document input screen including a repeated element, the element repeated direction storing step storing an element repeated direction; and an element repeated element arranging step arranging a repeated element in the element repeated direction. Is generated. As a result, the document administrator can specify the element repetition direction on the structured document input screen, so that the document input person can refer to the structured document in the form of a meaningful table according to the business of the repeated document structure elements. Therefore, the overall view is improved and not only the input becomes easy, but also an input error can be prevented.
[0091]
Also,In a pre-specified structured document entityAn element constraint storage step for storing element constraints, and an element constraint check step for checking whether the structured document input value input to the structured document input screen in the structured document input step satisfies the element constraints. . As a result, element constraints can be specified by the document administrator, so the document input person can check the input value constraints determined according to the business, and not only can prevent input errors but also has been designed. Since standard products can be used by adopting the discrete values, design cost and manufacturing cost can be suppressed.
[0092]
Also,Multiple elements of a pre-specified structured document entityAn inter-element constraint storage step for storing inter-element constraints, and an inter-element constraint check step for checking whether the structured document input value input to the structured document input screen in the structured document input step satisfies the inter-element constraints. And have. As a result, since the document administrator can specify inter-element constraints, the document input user can check the input value constraints determined according to the business, and not only can prevent input errors but also design. Since standard products can be used by adopting already-discrete values, design costs and manufacturing costs can be reduced.
[0093]
Also,Of elements in a pre-specified structured document entityThe structured document input value input to the structured document input screen is corrected to the closest value satisfying the element discrete value constraint in the element discrete value constraint storing step for storing the element discrete value constraint and the structured document input step. And an element discrete value correcting step. As a result, the document administrator can specify element discrete value constraints, so the document input person can check the input value constraints determined according to the job, so not only can prevent input errors, Since standard products can be used by adopting designed discrete values, design costs and manufacturing costs can be reduced.
[0094]
Further, a structured document change location extraction step for extracting a difference between the structured document entities by comparing the structured document entity with the comparison target structured document entity, and adding the first highlight character control code to the difference A structured document change location highlighting step, and the structured document change location display step highlights and displays the difference on the structured document display screen based on the creation data of the structured document change location highlighting step. Therefore, the changed part is highlighted and displayed, and the document input person and the document confirmer can easily grasp the changed part of any two structured documents.
[0095]
Also, the structured document entity before input is saved as a comparison target structured document entity, and the difference between the structured document entities is edited as a comparison portion by comparing the comparison target structured document entity with the structured document entity being input. There is a structured document editing part extracting step for extracting, and a structured document editing part highlighting step for adding the second highlight character control code to the editing part. Based on the data created in the document edit location highlighting step, the edit location is highlighted on the structured document display screen. Therefore, the changed part is highlighted and displayed, and the document input person and the document confirmer can easily grasp the changed part of any two structured documents. Furthermore, since the document manager defines the structured document to be compared according to the business, the document input person can easily grasp the editing portion by distinguishing it.
[0096]
Also, the structure document entity to be input and the version immediately before or the specified version of the structured document entity to be referenced are stored as a comparison target structured document entity, and the comparison target structured document entity and the structured document entity to be input are referred to. A structured document revision location extraction step for extracting a difference between structured document entities as a revised location by comparing the structured document entity, and a structured document revision that adds a third highlight character control code to the revised location A structured document change location display step that highlights and displays the revised location on the structured document display screen based on the creation data of the structured document revised location enhancement display step. Therefore, the changed part is highlighted and displayed, and the document input person and the document confirmer can easily grasp the changed part of any two structured documents. Furthermore, since the document manager defines the structured document to be compared according to the business, the document checker can easily grasp the revised portion by distinguishing it.
[0097]
Also,Create / change data of a shared structured document entity in which data is shared with the structured document entity and the correspondence between elements is specified with the shared structured document entity.Along with the creation or modification of the above structured document entitymake,In addition, there is a shared structured document change step for creating structured document entity creation / change data as the shared structured document entity is created or changed. Based on this, the related items of the structured document entity and the shared structured document entity are changed. Therefore, the document administrator specifies the correspondence between the structured document and other structured documents according to the business, and when a certain structured document is changed, refers to the other structured document shared with it. Other users can refer to results reflecting changes in the original structured document.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating an example of a processing operation of a structured document processing method according to a first embodiment of the present invention.
FIG. 2 is a diagram illustrating an example of a processing operation of a structured document processing method according to a second embodiment of the present invention.
FIG. 3 is a diagram illustrating an example of a processing operation of a structured document processing method according to a third embodiment of the present invention.
FIG. 4 is a diagram showing an example of a processing operation of a structured document processing method according to a fourth embodiment of the present invention.
FIG. 5 is a diagram illustrating an example of a processing operation of a structured document processing method according to a fifth embodiment of the present invention.
FIG. 6 is a diagram showing an example of a processing operation of a structured document processing method according to a fifth embodiment of the present invention.
FIG. 7 is a diagram showing an example of a processing operation of a structured document processing method according to a sixth embodiment of the present invention.
FIG. 8 is a diagram showing an example of a processing operation of a structured document processing method according to a sixth embodiment of the present invention.
FIG. 9 is a diagram illustrating an example of a processing operation of a structured document processing method according to a sixth embodiment of the present invention.
FIG. 10 is a diagram illustrating an example of a processing operation of a structured document processing method according to a seventh embodiment of the present invention.
FIG. 11 is a diagram illustrating an example of a processing operation of a structured document processing method according to a seventh embodiment of the present invention.
FIG. 12 is a diagram showing an example of processing operation of the structured document processing method according to the seventh embodiment of the present invention;
FIG. 13 is a diagram illustrating an example of a processing operation of a structured document processing method according to an eighth embodiment of the present invention.
FIG. 14 is a diagram illustrating an example of a processing operation of a structured document processing method according to an eighth embodiment of the present invention.
FIG. 15 is a diagram illustrating an example of document type definition according to the first embodiment, the second embodiment, the third embodiment, the fourth embodiment, the fifth embodiment, the sixth embodiment, and the seventh embodiment of the present invention; It is.
FIG. 16 is a diagram showing an example of a structured document input screen according to the first embodiment of the present invention.
FIG. 17 is a diagram showing an example of a structured document entity according to the first embodiment, the seventh embodiment, and the eighth embodiment of the present invention;
18 is a diagram showing an example of a structured document entity according to the embodiment of the present invention and Embodiment 7. FIG.
FIG. 19 is a diagram showing an example of a structured document display screen according to the first embodiment and the seventh embodiment of the present invention.
FIG. 20 is a diagram showing an example of a shared structured document entity according to the first embodiment and the eighth embodiment of the present invention.
FIG. 21 is a diagram showing an example of document structure element content definition according to the second embodiment of the present invention.
FIG. 22 is a diagram showing an example of a structured document input screen according to the second embodiment of the present invention.
FIG. 23 is a diagram showing an example of an interactive interface for designating a relative positional relationship between elements according to the third embodiment of the present invention.
FIG. 24 is a diagram illustrating a description example of a relative positional relationship between elements according to the third embodiment of the present invention.
FIG. 25 is a diagram showing an example of a structured document input screen according to the third embodiment of the present invention.
FIG. 26 is a diagram showing an example of an interactive interface for designating element selection values according to the fourth embodiment of the present invention.
FIG. 27 is a diagram illustrating a description example of element selection values according to the fourth embodiment of the present invention.
FIG. 28 is a diagram showing an example of a structured document input screen according to the fourth embodiment of the present invention.
FIG. 29 is a diagram showing an example of an interactive interface for designating a repetition number and a repetition direction according to the fifth embodiment of the present invention.
FIG. 30 is a diagram showing an example of a structured document input screen according to the fifth embodiment of the present invention;
FIG. 31 is a diagram showing a description example of element constraints according to the sixth embodiment of the present invention.
FIG. 32 is a diagram illustrating a description example of inter-element constraints according to the sixth embodiment of the present invention.
FIG. 33 is a diagram showing a display example of a message due to an element constraint violation according to the sixth embodiment of the present invention.
FIG. 34 is a diagram showing a display example of a message due to an element constraint violation according to the sixth embodiment of the present invention.
FIG. 35 is a diagram illustrating a description example of element discrete value constraints according to Embodiment 6 of the present invention;
FIG. 36 is a diagram showing a display example of a dialog message due to element discrete value constraint violation according to the sixth embodiment of the present invention;
[Explanation of symbols]
1 structured document input step, 2 structured document input value check step, 3 structured document change location display step, 4 shared structured document linkage step, 5 document type definition, 6 structured document input screen, 7 structured document Input value, 8 structured document entity, 9 comparison target structured document entity, 10 structured document display screen, 11 shared structured document entity, 12 structured document generation finite automaton creation step, 13 structured document input screen generation step, 14 structured document creation step, 15 structured document generation finite automaton, 16 element relative positional relationship designation step, 17 element relative positional relationship storage step, 18 element input position relative positioning step, 19 element relative positional relationship, 20 element Selection value designation step, 21 element selection value storage step, 2 Element selection value candidate creation step, 23 element selection value, 24 element repetition number designation step, 25 element repetition number storage step, 26 repetition element creation step, 27 element repetition number, 28 element repetition direction designation step, 29 element repetition direction storage step 30 element repetition element placement step, 31 element repetition direction, 32 element constraint designation step, 33 element constraint storage step, 34 element constraint check step, 35 element constraint, 36 interelement constraint designation step, 37 interelement constraint storage step, 38 Inter-element constraint check step, 39 Inter-element constraint, 40-element discrete value constraint specification step, 41-element discrete value constraint storage step, 42-element discrete value correction step, 43-element discrete value constraint, 44 Structured sentence Document change location extraction step, 45 structured document change location highlighting step, 46 structured document edit location extraction step, 47 structured document edit location highlighting step, 48 structured document revision location extraction step, 49 structured document revision location Highlighting step, 50 Shared structured document designation step, 51 Structured document element correspondence designation step, 52 Structured document element content correspondence designation step, 53 Shared structured document modification step, 54 Shared NDATA entity, 55 Shared NDATA designation 56, a shared NDATA correspondence specifying step, 57 a shared NDATA changing step.

Claims (13)

In a structured document processing method for processing a structured document having a structure ,
A structured document input step for generating a structured document input screen based on the document type definition and creating a structured document entity from the structured document input value input from the structured document input screen;
A structured document input value check step for checking whether the structured document input value input from the structured document input screen satisfies a preset constraint;
A structured document change location display step for distinguishing and displaying a change location of the structured document entity by comparing the structured document entity with a comparison target structured document entity prepared in advance;
A shared structured document interlinking step for changing related items of the shared structured document shared with other users when the structured document entity is created or changed ;
Create a shared NDATA entity that shares data with the structured document entity but is not in a structured document format and that specifies the corresponding relationship with the structured document entity as the structured document entity is created or changed or changed, the structured document processing method characterized by comprising a <br/> shared NDATA changing step of creating or modifying the structured document entity according creating or modifying the shared NDATA entity. The structured document input step includes a document type definition or a structured document generation finite automaton creation step for creating a structured document generation finite automaton from a document type definition and a structured document entity;
A structured document input screen generation step for generating the structured document input screen by following the order of the structured document generation finite automaton;
2. The structured document processing method according to claim 1, further comprising a structured document creation step of creating a structured document entity from the structured document input value input on the structured document input screen. An inter-element relative positional relationship storage step for storing the relative positional relationship between elements designated from the structured document input screen ;
An element input position relative arrangement step of reading the element relative position relation and creating element input position arrangement data of the structured document input screen according to the element relative position relation;
3. The structured document processing method according to claim 2, wherein the structured document input screen generating step generates the structured document input screen based on the element input position arrangement data. An element selection value storage step for storing an element selection value designated in advance from the structured document input screen ;
An element selection value candidate creation step for creating an element selection value candidate for the structured document input screen according to the element selection value,
3. The structured document processing method according to claim 2, wherein the structured document input screen generating step generates the structured document input screen including the element selection value candidates. An element repetition number storage step for storing an element repetition number designated in advance from the structured document input screen ;
A repeating element creation step for creating a repeating element of the structured document input screen according to the number of element repetitions,
3. The structured document processing method according to claim 2, wherein the structured document input screen generation step generates the structured document input screen including the repetitive element. And elements repeat direction storage step of storing the elements repeatedly in a certain direction in the specified orientation of the repeating element,
An element repeating element arranging step of arranging the repeating element in an element repeating direction,
6. The structured document processing method according to claim 5, wherein the structured document input screen generating step generates the structured document input screen including the repetitive element. And element constraint storage step of storing the elements constrained in a pre-specified the structured document entity,
2. The element constraint check step of checking whether the structured document input value input to the structured document input screen in the structured document input step satisfies the element constraint. The structured document processing method described. An inter-element constraint storage step for storing inter-element constraints of a plurality of elements in the structured document entity designated in advance ;
An inter-element constraint check step for checking whether the structured document input value input on the structured document input screen in the structured document input step satisfies the inter-element constraint;
Structured document processing method according to claim 7, wherein a. An element discrete value constraint storing step for storing element discrete value constraints of elements in the structured document entity designated in advance ;
An element discrete value correction step for correcting the structured document input value input to the structured document input screen in the structured document input step to the nearest value satisfying the element discrete value constraint;
Structured document processing method according to claim 7, wherein a. A structured document change location extraction step for extracting a difference between the structured document entities by comparing the structured document entity with the comparison target structured document entity;
A structured document change location highlighting step of adding a first highlighting character control code to the difference,
2. The structure according to claim 1, wherein the structured document change location display step highlights and displays the difference on the structured document display screen based on the data generated in the structured document change location highlighting step. Document processing method. The structured document entity before input is stored as the above-mentioned comparison target structured document entity, and the difference between the structured document entities is edited as a comparison portion by comparing the compared structured document entity with the structured document entity being input. A step of extracting a structured document editing part to be extracted
A structured document editing part highlighting step for adding a second highlight character control code to the editing part,
11. The structured document change location display step emphasizes and displays the edited location on the structured document display screen based on the creation data of the structured document edit location highlighting step. Structured document processing method. The structured document entity to be input and the immediately preceding version or the specified version of the referenced structured document entity are stored as a comparison-target structured document entity, and the structured document entity to be input and the structure to be referenced A structured document revision location extraction step for extracting a difference of the structured document entity as a revision location by comparing with the structured document entity;
A structured document revision location highlighting step for adding a third highlight character control code to the revision location,
11. The structured document change location display step highlights and displays the revised location on the structured document display screen based on the creation data of the structured document revision location highlighting step. Structured document processing method. Create / change shared shared document entity data that shares data with the structured document entity and that specifies the correspondence between elements between the structured document entity and create or change the structured document entity created with the, also with the creation or modification of the shared structured document entity has a shared structured document changing step of creating a creation or change data in the structured document entity,
2. The structured document according to claim 1, wherein the shared structured document interlinking step changes items related to the structured document entity and the shared structured document entity based on the creation / change data. Processing method.

Images