JP3772142B2 - Structured document update management device, structured document update management method, computer-readable recording medium storing program, and program - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
Annotation system that supports document editing, etc., allows editing contents to be reflected in documents with the same structure, manages multiple stages of update instructions, and provides instructions for update at each stage in processing such as display It relates to the technology to distinguish.
[0002]
[Prior art]
A conventional document editing apparatus uses the number of characters, the number of lines, and the like as a method for specifying an editing portion. This method is based on the premise that the document that is premised on editing and the document that reflects the editing completely match.
[0003]
Therefore, if the document premised on editing does not match the document reflecting the editing, the editing result cannot be reflected even if the document structure (chapter or paragraph) is similar. For example, when editing is started on the premise of editing a document that is not the latest, the editing result cannot be reflected in the latest document.
[0004]
In addition, when multiple revisions are generated in a structured document and a plurality of versions are generated, the update instruction for the prerequisite version and the update instruction for the latest version are distinguished from each other, including the mode in which the update parts overlap. It's inconvenient if you can't. In particular, if the two cannot be distinguished from each other in the display, the viewer is prevented from understanding the significance of overlapping revisions.
[0005]
[Patent Document 1]
Japanese Patent Laid-Open No. 9-167158
[Patent Document 2]
JP 2001-51932 A
[Patent Document 3]
JP 2001-195438 A
[0006]
[Problems to be solved by the invention]
The present invention has been made in order to eliminate the above-described drawbacks of the prior art. The object of the present invention is to edit a document that does not completely match if the document has the same document structure. It is an object of the present invention to provide a structured document update management apparatus capable of reflecting a plurality of update instructions and distinguishing update instructions at each stage in processing such as display.
[0007]
[Means for Solving the Problems]
The structured document update management apparatus according to the present invention is:
Structured document update management device that converts a structured document containing multiple stages of update instructions into a display document and outputs the display document And has the following elements: It is characterized by
(1) an original structured document described using a document structure tag that identifies the structure of the document;
An update instruction for the original structured document, a first update instruction including an edit position specified by a document structure tag and a position specifying character string extracted from the original structured document;
An update instruction for the structured document in which the first update instruction is inserted at the editing position in the original structured document using the first update instruction tag, and the document structure tag and the first update instruction are inserted. Document database for storing the second update instruction including the editing position designated by the position designation character string extracted from the structured document, and the original structured document from the document database. The first update instruction and the second update instruction corresponding to the original structured document are acquired, and the first update instruction tag is added to the edit position in the acquired original structured document. Insert with
Further, an edit document generation for generating an edit document by inserting the acquired second update instruction into an edit position in the structured document in which the first update instruction is inserted using the second update instruction tag Part
(3) The first update instruction tag in the edited document is converted into the first display decoration tag, and the second update instruction tag in the edited document is converted into the second display decoration tag, thereby displaying the display document. Display document generator for generating
(4) A document output unit for outputting the generated display document.
[0008]
The display document generation unit includes a first update instruction tag sandwiched between a start tag and an end tag of the first update instruction tag among the first update instruction tags in the edited document. Only the first update instruction tag at least partially overlapping with the second update instruction region sandwiched between the start tag and the end tag is converted into the first display decoration tag.
[0009]
The display document generation unit performs a non-reflecting process for displaying a state in which there is no update instruction for the first update instruction that is not converted into the first display decoration tag.
[0010]
The first update instruction and the second update instruction each include at least an edit type including deletion and insertion, and a first delete display decoration tag converted from the first update instruction tag whose edit type is deletion, The first insertion display decoration tag converted from the first update instruction tag whose edit type is insertion and the second deletion display decoration converted from the second update instruction tag whose edit type is deletion The tag and the second insertion display decoration tag converted from the second update instruction tag whose edit type is insertion are different decoration tags that can be distinguished from each other on display.
[0011]
The document output unit transmits to a device including a browser for displaying a structured document.
[0012]
The structured document update management method according to the present invention includes:
An original structured document described using a document structure tag that specifies the structure of the document, and an update instruction for the original structured document, the document structure tag and a position-specified character string extracted from the original structured document The first update instruction including the edit position designated by the above and the update instruction for the structured document in which the first update instruction is inserted at the edit position in the original structured document using the first update instruction tag The document structure tag and the second update instruction including the editing position designated by the position designation character string extracted from the structured document in which the first update instruction is inserted are stored in association with each other. Structured Document Update Management Method Using Structured Document Update Management Device Accessible to Document Database And has the following elements: It is characterized by that.
(1) The edit document generation unit provided in the structured document update management device The original structured document, the first update instruction and the second update instruction corresponding to the original structured document are acquired from the document database, and the acquired first update instruction is edited in the acquired original structured document. In the location using the first update instruction tag,
Furthermore, a step of generating an edited document by inserting the acquired second update instruction into an edit position in the structured document in which the first update instruction has been inserted, using the second update instruction tag.
(2) The display document generation unit provided in the structured document update management device A first update instruction tag in the edited document is converted into a first display decoration tag, and a second update instruction tag in the edited document is converted into a second display decoration tag, thereby generating a display document. Process
(3) The document output unit provided in the structured document update management device A step of outputting the generated display document.
[0013]
A computer-readable recording medium on which a program according to the present invention is recorded,
An original structured document described using a document structure tag that specifies the structure of the document, and an update instruction for the original structured document, the document structure tag and a position-specified character string extracted from the original structured document The first update instruction including the edit position designated by the above and the update instruction for the structured document in which the first update instruction is inserted at the edit position in the original structured document using the first update instruction tag The document structure tag and the second update instruction including the editing position designated by the position designation character string extracted from the structured document in which the first update instruction is inserted are stored in association with each other. A computer-readable recording medium recording a program for causing a computer to be a structured document update management apparatus accessible to a document database to execute the following processing:
(1) The edit document generation unit provided in the structured document update management device The original structured document, the first update instruction and the second update instruction corresponding to the original structured document are acquired from the document database, and the acquired first update instruction is edited in the acquired original structured document. In the location using the first update instruction tag,
Further, a process for generating an edited document by inserting the acquired second update instruction into the edit position in the structured document in which the first update instruction has been inserted, using the second update instruction tag.
(2) The display document generation unit provided in the structured document update management device A first update instruction tag in the edited document is converted into a first display decoration tag, and a second update instruction tag in the edited document is converted into a second display decoration tag, thereby generating a display document. processing
(3) The document output unit provided in the structured document update management device Processing to output the generated display document.
[0014]
The program according to the present invention is:
An original structured document described using a document structure tag that specifies the structure of the document, and an update instruction for the original structured document, the document structure tag and a position-specified character string extracted from the original structured document The first update instruction including the edit position designated by the above and the update instruction for the structured document in which the first update instruction is inserted at the edit position in the original structured document using the first update instruction tag The document structure tag and the second update instruction including the editing position designated by the position designation character string extracted from the structured document in which the first update instruction is inserted are stored in association with each other. A program for causing a computer, which is a structured document update management apparatus capable of accessing a document database for execution, to execute the following procedure:
(1) The edit document generation unit provided in the structured document update management device The original structured document, the first update instruction and the second update instruction corresponding to the original structured document are acquired from the document database, and the acquired first update instruction is edited in the acquired original structured document. In the location using the first update instruction tag,
Further, a procedure for generating an edited document by inserting the acquired second update instruction into the edit position in the structured document in which the first update instruction has been inserted, using the second update instruction tag.
(2) The display document generation unit provided in the structured document update management device A first update instruction tag in the edited document is converted into a first display decoration tag, and a second update instruction tag in the edited document is converted into a second display decoration tag, thereby generating a display document. procedure
(3) The document output unit provided in the structured document update management device A procedure for outputting the generated display document.
[0015]
DETAILED DESCRIPTION OF THE INVENTION
Embodiment 1 FIG.
Hereinafter, the present invention will be described based on embodiments shown in the drawings. FIG. 1 is a diagram showing a network environment of the annotation system. A terminal 1 used by a document editor is configured to be able to access the annotation system 1 via a network 3. The network 3 is, for example, the Internet or an intranet. The terminal 2 includes a browser.
[0016]
FIG. 2 is a diagram illustrating a configuration example of the annotation system.
201 is a document database, 202 is an edited document selection unit, 203 is an edited document generation unit, 204 is an updated document storage unit, 205 is a display document generation unit, 206 is a document transmission unit, and 207 is An update instruction generation program distribution unit (an example of an update instruction generation program output unit), 208 an update instruction generation program storage unit, 209 an update instruction reception unit, 210 an update instruction storage unit, and 211 an update instruction execution unit , 212 are update confirmation processing units.
[0017]
FIG. 3 is a diagram illustrating a configuration example of the management table in the document database.
A record is provided for each document, and includes items of a document ID, a document name, an XML file name, a DTD file name, a style sheet file name, the number of update instructions, and each update instruction file name. The document database 201 may be provided outside the annotation system 1 so that the annotation database 1 can access the document database 201 via a network or the like.
[0018]
FIG. 4 is a diagram showing an overall processing flow of the document editing process.
The edited document selection unit 202 performs an edited document selection process (S401). When a request for an edited document selection screen is received from the editor's terminal 2, a document list is acquired from the document database 201 and transmitted to the terminal 2 as an edited document selection screen.
FIG. 5 is a diagram showing a display example of the edited document selection screen.
[0019]
The editor selects a document (edited document) to be edited from the edited document selection screen, and transmits the selected content to the annotation system 1. The edited document selection unit 202 specifies an edited document ID according to the received selection content.
[0020]
The edited document generation unit 203 acquires an edited document corresponding to the edited document ID from the document database 201 by the edited document generation process (S402). The edited document includes (XML (extensible Markup Language) document file, DTD (Document Type Definition) file, style sheet)). An XML document is an example of a structured document described using a document structure tag that specifies the structure of the document.
In the case of a document that has already been updated, an update instruction file is further included, and the update instruction in the update instruction file is inserted into the editing position in the XML document using the update instruction tag. Thus, an edited document to be edited is generated, and the generated edited document is stored in the updating document storage unit 204 as an updating document in an initial state.
FIG. 6 is a diagram illustrating an example of an XML document that is an edited document. This document shows an example that has not been updated.
[0021]
The display document generation unit 205 performs display document generation processing (S403). As a result, the updating document stored in the updating document storage unit 204 (in the initial state, the same as the edited document described above) is acquired, the updating document is converted according to the display format, and the display document is converted. Generate.
Regarding display document generation processing by conversion of a document under update performed according to the display format, there are four methods: an update instruction display method, a full update instruction reflection method, a multiple update instruction display method, a latest update instruction, and a related update instruction display method. It will be described later.
[0022]
The document transmission unit 206 performs document transmission processing (S404). As a result, a document display screen for displaying the generated display document (frame data including an area for displaying the image of the document developed by the browser and a scroll bar) is generated, and the display document and the document display screen are displayed. Is transmitted to the terminal 2.
FIG. 7 is a diagram illustrating a display example of a document display screen based on an updating document in an initial state. The display document is expanded by the browser as shown in the figure, and an image of the expanded document is displayed in the display area in the frame of the document display screen. In the figure, the scroll bar and the like are omitted, and only the image of the document that can be viewed in the display area is shown. In this example, the XML document shown in FIG. 6 is used as it is as a display document without being converted.
[0023]
In this state, the annotation system 1 waits for instruction reception (S405). On the other hand, an update instruction, an update confirmation instruction, or an end instruction can be transmitted from the document display screen displayed on the terminal 2.
[0024]
The operation in which the editor instructs to update the edited document on the terminal 2 is executed by the update instruction generation program. In this example, the update instruction generation program is provided from the annotation system 1 in response to a request from the terminal 2. Specifically, it is provided as a JAVA (registered trademark) applet. The timing at which the terminal 2 requests the JAVA applet may be at the time of initialization or at the timing of instructing the update.
[0025]
When the editor clicks an update location on the document display screen, the update instruction generation program displays a window for selecting the type of update (deletion or insertion). When deletion is selected, the operation is performed so that a range to be deleted (deletion character string) is designated. For example, the first character and the last character in the range to be deleted are designated. Further, in the case of insertion, the operation is performed so that the insertion position is designated and the insertion character string is input. When the editor instructs to determine the update instruction, the update instruction generation program generates an update instruction and transmits it to the annotation system 1. In the case of deletion, the structural unit (for example, chapter or item) on the document including the deletion character string is specified by the document structure tag, the character string before the deletion character string is extracted, and the character after the deletion character string is extracted. Extract columns and create update instructions. In the case of insertion, the structural unit (for example, chapter or section) on the document including the insertion position is specified by the document structure tag, the character string before the insertion position is extracted, and further the character string after the insertion position is extracted. The update instruction is created together with the input insertion character string.
[0026]
If the instruction received on the annotation system 1 side is an update instruction, the update instruction receiving unit 209 performs an update instruction reception process (S406). In this example, the update instruction receiving unit 209 is configured by a JAVA servlet. The update instruction receiving unit 209 stores the received update instruction in the update instruction storage unit 210. The update instruction storage unit 210 receives the update confirmation instruction (S408), and performs the update instruction received sequentially until the update confirmation process (S409) is performed or the termination instruction is received (S410) and the process is terminated. As (stage) update instructions, all update instructions are stored as a group.
[0027]
Here, the update instruction will be described. The update instruction includes an edit position, an edit type, and a character string corresponding to the edit type. An update instruction for the display example of the document under update in the initial state shown in FIG. 7 will be described as an example. For convenience of explanation, a display example of a document display screen by an update instruction display method described later is shown. FIG. 8 is a diagram illustrating a display example (update instruction display method) of the document display screen after the first update instruction is input. In this example, the character string that has been subjected to a strikethrough is a character string that has been instructed to be deleted by an update instruction, and the character string that has been underlined is a character string that has been instructed to be inserted by an update instruction.
[0028]
FIG. 9 is a diagram illustrating an example of a first update instruction for the item 1.1. The editing position is specified by a tag (document structure tag that specifies the structure of the document) included in the XML file, a preceding character string, and a following character string. Deletion is designated as the editing type. The front character string and the rear character string are examples of position specifying character strings. This means that the character string from the character after the last character of the previous character string to the character before the first character of the subsequent character string is deleted. In this example, the character string “general” between the character string “701” in the character string 701 shown in FIG. Indicates instructions.
The number of characters in the preceding character string and the succeeding character string is sufficient to specify the editing position, and is not particularly limited. For example, a method of setting a predetermined number of characters such as 15 characters or 30 characters, a method of determining the number of characters by combining the minimum number of characters and sentence or phrase delimiters, and the like can be considered.
[0029]
FIG. 10 is a diagram illustrating an example of a first update instruction for the item 1.2. As described above, the editing position is specified by a tag (document structure tag for specifying the structure of the document), the preceding character string, and the following character string included in the XML file. Then, insertion is designated as the editing type, and an insertion character string is designated. The previous character string and the subsequent character string are examples of position designation character strings, as described above. This means that an insertion character string is inserted between the last character of the preceding character string and the first character of the subsequent character string. In this example, a character string of “standard creation” is inserted between the preceding character string “This standard is” and the subsequent character string “created based on the standard” of the character string 702 in FIG. Indicates instructions.
[0030]
11 to 16 show examples of the first update instruction configured in the same manner as described above. FIG. 11 is a diagram illustrating an example of a first update instruction for the item 1.3. FIG. 12 is a diagram illustrating an example of a first update instruction for the item 1.4. FIG. 13 is a diagram illustrating an example of a first update instruction for the item 1.5. FIG. 14 is a diagram illustrating an example of a first update instruction for the item 1.6. FIG. 15 is a diagram illustrating an example of the first update instruction (deletion) for the item of 1.7. FIG. 16 is a diagram illustrating an example of the first update instruction (insertion) for the item of 1.7.
[0031]
As shown in FIG. 4, when the update instruction reception process is completed, the update instruction execution unit 211 performs an update instruction execution process (S407). The update instruction execution unit 211 acquires an update instruction from the update instruction storage unit 210. The contents of the document storage unit 204 that is being updated are updated according to the editing position, editing type, and inserted character string when the editing type is inserted in the update instruction. At this time, the update instruction execution unit 211 compares the document structure tag for designating the editing position with the document structure tag included in the updating document stored in the updating document storage unit, thereby editing the item ( Identify structural unit on document). In this example, an item to be edited can be specified by searching the document structure tag designating the editing position downward in order from the top of the document being updated.
[0032]
When the edit type is deletion as shown in FIG. 9, the update instruction execution unit 211 further identifies the deletion part by comparing the sentence before update of the specified term with the previous character string and the subsequent character string. can do. Then, the update instruction execution unit 211 inserts a deletion start tag <deleteX> and a deletion end tag </ deleteX> before and after that. X is replaced with a number indicating the update stage (times). The update stage is obtained by adding 1 to the number of update instructions acquired from the document database 201. The update stage is an example of an update instruction stage identifier that identifies the context of the update instruction.
[0033]
When the edit type is insertion as shown in FIG. 10, the insertion location can be specified by comparing the sentence before the update of the specified term with the previous character string and the subsequent character string. Then, the update instruction execution unit 30 inserts an insertion start tag <insertX> and an insertion end tag </ insertX> before and after that, and adds an insertion character string between them. X is the same as described above.
The deletion tag (deletion start tag <deleteX> and deletion end tag </ deleteX>) and the insertion tag (insertion start tag <insertX> and insertion end tag </ insertX>) are examples of update instruction tags.
[0034]
An example of a document that is being updated when the update instruction execution process (S407) is performed for the first update instruction in FIGS. FIG. 17 is a diagram illustrating an example of an XML document in which the first update instruction tag is inserted.
[0035]
In this way, the updating document is updated, and the updated updating document is processed into a display document by the display document generation process (S403) of the display document generation unit 205. In this process, a display document in a form corresponding to the update type (delete or Insert) included in the update instruction tag and the update stage (the subsequent number in this example) is generated based on the display method.
[0036]
Hereinafter, the display document generation processing (S403) for each display method will be described. First, display document generation processing in the case of the update instruction display method will be described. FIG. 8 described above is a display example according to this display method.
In this method, the latest update instruction is reflected on the document, and the latest update instruction is displayed on the document. The reflection here is to delete the character string of the deleted portion and insert the character string of the inserted portion, and the display is a display decoration (in this example, indicating deletion) (Strikethrough) is applied, and a display decoration (in this example, underline) indicating insertion is applied to the character string of the insertion portion to indicate the record of the update instruction content.
[0037]
FIG. 18 is a diagram showing a display document generation processing flow based on the update instruction display method. The display document generation unit 205 acquires the update instruction count N from the document database 201 (S1801). When the number of update instructions N = 0 (S1802), the process proceeds to a process for displaying an update instruction (S1807).
When the number of update instructions N ≧ 1 (S1803), update instruction reflection processing (S1804) for sequentially reflecting the update instructions from the first time to the Nth time is performed. The update instruction reflection process (S1804) will be described later with reference to FIG.
The display document generation unit 205 has two or more document storage buffers therein, and uses one as an original document storage buffer and the other as a destination document storage buffer in one reflection process or display process. In the reflection process or display process, conversely, the process is repeated by using the other buffer that was the previous document storage buffer as the original document storage buffer and one as the previous document storage buffer. That is, processing is performed while data is transferred between the document storage buffers. Data migration is repeated in order from the beginning to the end of the document in units of characters or tags, as will be described later. The document storage buffer is used in the same way in other reflection processing and display processing of the display document generation unit 205.
When all the update instructions up to N have been processed (S1805), the update instruction display process (S1807) is performed for the N + 1 update instruction (S1806). The update instruction display process (S1807) will be described later with reference to FIG.
[0038]
FIG. 19 is a diagram showing an update instruction reflecting process flow.
Character or tag units are sequentially read from the original document storage buffer (S1901), and the following processing is repeated. If a character has been read (S1902), the read character is copied to the previous document storage buffer (S1903). If the tag is read, it is determined whether the read tag is a deletion start tag <deleteX> (S1904). In this case, X (update instruction stage identifier) after delete in the tag is converted to the value of the update instruction time (update instruction stage) X specified in S1803 of FIG. For example, in the case of the first update instruction, the deletion start tag is determined as <delete1>. The same applies to X (update instruction stage identifier) after insertion, which will be described later. The same applies to each end tag, and the same applies to other reflection processing and display processing.
If the read tag is the deletion start tag <deleteX>, the deletion mode reflection process (S1905) is performed. This process will be described later with reference to FIG.
It is determined whether the read tag is an insertion start tag <insertX> (S1906). If the tag is an insertion start tag <insertX>, an insertion mode reflection process (S1907) is performed. This process will be described later with reference to FIG.
If the read tag is another tag, the read tag is copied to the previous document storage buffer (S1908).
The process ends when all character or tag units are read (S1909).
[0039]
FIG. 20 is a diagram showing a deletion mode reflection processing flow.
The read deletion start tag <deleteX> is copied to the previous document storage buffer (S2001), and the next character or tag unit is read from the original document storage buffer (S2002). When a character is read (S2003), the read character is not copied (S2004), and the process proceeds to the next reading (S2002).
When the deletion end tag </ deleteX> is read (S2005), the deletion end tag </ deleteX> is copied to the previous document storage buffer (S2006), and the process ends.
When another tag is read, the read tag is copied to the previous document storage buffer (S2007), and the process proceeds to the next reading (S2002).
[0040]
FIG. 21 is a diagram showing an insertion mode reflection processing flow.
The read insertion start tag <insertX> is copied to the previous document storage buffer (S2101), and the next character or tag unit is read from the original document storage buffer (S2102). If a character is read (S2103), the read character is copied to the previous document storage buffer (S2104), and the process proceeds to the next reading (S2102).
When the insertion end tag </ insertX> is read (S2105), the insertion end tag </ insertX> is copied to the previous document storage buffer (S2106), and the process ends.
When another tag is read, the read tag is copied to the previous document storage buffer (S2107), and the process proceeds to the next reading (S2102).
[0041]
Next, the update instruction display process (S1808) in FIG. 18 will be described in detail. FIG. 22 is a diagram showing an update instruction display processing flow.
Characters or tag units are sequentially read from the original document storage buffer (S2201), and the following processing is repeated. If a character has been read (S2202), the read character is copied to the destination document storage buffer (S2203). When the tag is read, it is determined whether the read tag is a deletion start tag <deleteX> (S2204). In the case of the deletion start tag <deleteX>, a deletion mode display process (S2205) is performed. This process will be described later with reference to FIG.
It is determined whether the read tag is an insertion start tag <insertX> (S2206). If it is an insertion start tag <insertX>, an insertion mode display process (S2207) is performed. This process will be described later with reference to FIG.
If the read tag is another tag, the read tag is copied to the previous document storage buffer (S2208).
The process ends when all character or tag units are read (S2209).
[0042]
FIG. 23 is a diagram showing a deletion mode display processing flow.
The read deletion start tag <deleteX> is copied to the previous document storage buffer, and subsequently inserted into the strikethrough start tag <STRIKE> (S2301). Then, the next character or tag unit is read (S2302). When a character is read (S2303), the read character is copied (S2304), and the process proceeds to the next reading (S2302).
When the deletion end tag </ deleteX> is read (S2305), the strikethrough end tag </ STRIKE> is inserted into the previous document storage buffer, and then the deletion end tag </ deleteX> is copied to the previous document storage buffer. (S2306).
When another tag is read, the read tag is copied to the previous document storage buffer (S2307), and the process proceeds to the next reading (S2302).
[0043]
FIG. 24 is a diagram showing an insertion mode display processing flow.
The read insertion start tag <insertX> is copied to the previous document storage buffer, and then the underline start tag <U> is inserted (S2401). Then, the next character or tag unit is read (S2402). When a character is read (S2403), the read character is copied (S2404), and the process proceeds to the next reading (S2402).
When the insertion end tag </ insertX> is read (S2405), the underline end tag </ U> is inserted into the previous document storage buffer, and then the insertion end tag </ insertX> is copied to the previous document storage buffer. (S2406).
When another tag is read, the read tag is copied to the previous document storage buffer (S2407), and the process proceeds to the next reading (S2402).
[0044]
FIG. 17 shows a display document that is a result of processing for generating a display document by the update instruction display method for the document being updated in FIG. FIG. 25 is a diagram showing a display document related to the first update instruction by the update instruction display method.
As shown in the figure, a strikethrough start tag <STRIKE> and a strikethrough end tag </ STRIKE> are inserted inside a deletion start tag <deleteX> and a deletion end tag </ deleteX>, and an insertion start tag <insertX> The underline start tag </ U> and the underline end tag </ U> are inserted inside the insertion end tag </ insertX>. However, these update instruction tags and display decoration tags corresponding to the update instruction tags need only be continuous, and the front and back may be reversed.
[0045]
Here, switching of the display method of the display document generation process will be described. FIG. 26 is a diagram illustrating an example of a component related to a change in display method.
Reference numeral 213 denotes a display method input unit. The display method input unit 213 receives a display method designated by the editor from the terminal 2. The display document generation unit 205 performs display document generation processing according to the received display method.
[0046]
Next, display document generation processing in the case of the all update instruction reflection method will be described. This method is a process of reflecting all the update instructions including the input undecided update instruction.
[0047]
FIG. 27 is a diagram showing a display document generation processing flow according to the all update instruction reflection method. The display document generation unit 205 acquires the update instruction count N from the document database 201 (S2701).
Thereafter, an update instruction reflection process (S2703) for sequentially reflecting the update instructions from the first time to the (N + 1) th time is performed. The update instruction reflecting process is the same as the process described above (FIG. 19 and the like).
When all the update instructions up to N have been processed (S2704), the process ends.
[0048]
A display document, which is a result of the display document generation processing by the all update instruction reflection method for the updating document of FIG. 17, is shown in the figure. FIG. 28 is a diagram showing a display document related to the first update instruction by the all update instruction reflection method.
As shown in the figure, the character string between the deletion start tag <deleteX> and the deletion end tag </ deleteX> is deleted.
An example in which this display document is displayed on a document display screen is shown. FIG. 29 is a diagram illustrating a display example (all update instruction reflecting method) of the document display screen after the first update instruction is input. This display example represents an image of a document in which all update instructions are reflected.
[0049]
Next, a process for confirming an update instruction and registering it in the document database 201 in a state where the update instruction is input in this way will be described.
In the state of waiting for reception (S405) shown in FIG. 4, when the update confirmation processing unit 212 receives an update confirmation instruction from the terminal 2 (S408), the update confirmation processing unit 212 performs the update confirmation processing (S409). Do. A series of update instruction groups (for example, the first update instruction from FIG. 9 to FIG. 16 or the second update instruction from FIG. 33 to FIG. 40) stored in the update instruction storage unit 210 are updated together. It is stored in the document database 201 as an instruction file. At this time, the update instruction count of the new document on the management table in the document database 201 is set to the number obtained by adding 1 to the update instruction count of the original document. Further, the file name of the generated update instruction file is stored in the item of update instruction file name corresponding to the number of updates on the management table in the document database 201.
FIG. 30 is a diagram illustrating a configuration example of the management table in the document database after the first update instruction is registered. In this example, KOU. In the UPI file, the first update instruction from FIG. 9 to FIG. 16 is stored.
When the end instruction is received as shown in FIG. 4 (S410), the process is ended.
[0050]
Hereinafter, an example will be described in which a document (in this example, xx standard (Draft)) by a first update instruction is selected and a second update instruction is input. The editor who gives the second update instruction may be the same as or different from the first editor. Also, the terminal 2 may be the same or different. When an update instruction is input for the second time, the process of FIG. 4 is performed again.
[0051]
FIG. 31 is a diagram illustrating a display example of an edit document selection screen including a document according to the first update instruction. This screen is displayed based on the management table in the document database 201 of FIG.
On this screen, XX standard (Draft) is selected, and a display document (similar to FIG. 28) is generated by the update instruction display method of FIG. 18 according to the processing of FIG. indicate.
[0052]
In this state, the editor transmits a second update instruction from the terminal 2. When the annotation system 2 receives a new update instruction, the annotation system 2 newly generates a display document by the update instruction display method shown in FIG. A display example at that time is shown. FIG. 32 is a diagram illustrating a display example (update instruction display method) of the document display screen after the second update instruction is input. For the state reflecting the first update instruction, the second update instruction is displayed.
[0053]
33 to 41 are diagrams showing examples of the second update instruction for each item. The configuration is the same as the first update instruction. However, since the update instruction is generated on the terminal 2 side in the state where the display document similar to FIG. 28 is displayed, the first update instruction tag may be included in the preceding character string or the succeeding character string.
[0054]
The updating document after the update instruction execution process (S407) for the second update instruction is illustrated. FIG. 41 is a diagram illustrating an example of an XML document in which a second update instruction tag is inserted.
[0055]
When the update instruction reflection method is instructed for the document being updated, a display document is generated by the processing of FIG. 27 and displayed as shown in FIG. FIG. 42 is a diagram illustrating a display example of the document display screen after the second update instruction is input (all update instruction reflecting method).
[0056]
When the editor transmits an update confirmation instruction from the terminal 2, the second update instruction is registered in the document database 201 according to the above-described processing. FIG. 43 is a diagram illustrating a configuration example of the management table in the document database after the second update instruction is registered. In this example, OTSU. The UPI includes the second update instruction shown in FIGS.
[0057]
Embodiment 2. FIG.
In the following, display processing of a document including an update instruction twice (in this example, xx standard (better)) will be described. When the edited document is selected in the state shown in FIG. 43, an edited document selection screen shown in FIG. 44 is displayed. FIG. 44 is a diagram illustrating a display example of an edit document selection screen including a document according to the second update instruction.
[0058]
When the editor selects the xx standard (end plan) from the terminal 2, the edited document generation unit 203 updates the XML file, DTD file, style sheet file, and update corresponding to the selected edited document ID from the document database 201. The update instruction file for the number of times is acquired, and an edited document is generated. In order from the first time, the update instruction in each update instruction file is inserted into the edit position in the XML document using the update instruction tag. As a result, an editing document similar to that shown in FIG. 41 is generated and stored as an initial updating document.
[0059]
In the present embodiment, a description will be given of a form in which a display document is generated by the multiple update instruction display method based on the document being updated in the state of FIG.
FIG. 45 is a diagram showing a display example (multiple update instruction display method) of a document display screen of an XML document including first and second update instructions. This method is a method of displaying a plurality of update instructions using different display decorations. In this example, the display decoration for the first update instruction is different from the display decoration for the second update instruction. The first update instruction in which the edit type is deletion is displayed as a subscript, and the first update instruction in which the edit type is insertion is displayed as a superscript. In addition, the second update instruction whose edit type is deletion is displayed with a strike-through line, and the second update instruction whose edit type is insertion is displayed with an underline. Other than this form, any display decoration that can be distinguished from each other is acceptable. For example, it is also effective to color-code the update stage (times) and update type (deletion, insertion), or to change the font or character size.
[0060]
Next, a display document generation process using the multiple update instruction display method will be described. FIG. 46 is a diagram showing a display document generation processing flow based on the multiple update instruction display method. In this method, a process for displaying a precondition update instruction (first update instruction in the above example) and a process for displaying the latest update instruction (second update instruction in the above example) Do.
The display document generation unit 205 acquires the update instruction count N from the document database 201 (S4601). If the update instruction count N = 0 (S4602), the process ends. When the update instruction count N = 1 (S4603), the update instruction reflection process and the premise update instruction display process are omitted, and the latest update instruction display process is performed. When the number of update instructions N> 2 (S4604), the update instruction reflection process (S4606) is repeated from the first update instruction to the N-2th (S4605). The update instruction reflecting process is as shown in FIG. However, if there is no further update instruction, update instruction tags that do not affect the display (deletion start tag <deleteX>, deletion end tag </ deleteX>, insertion start tag <insertX>, insertion end tag </ insertX >) Without copying.
Thereafter, for the N-1th update instruction (S4608), an update instruction display (update instruction stage) X = N-1 is performed, and a premise update instruction display process (S4609) is performed. This process will be described later with reference to FIG.
Finally, for the Nth update instruction (S4610), the update instruction display (update instruction stage) X = N is performed, and the latest update instruction display process (S4611) is performed. This process will be described later with reference to FIG.
In this example, the processing flow in which the premise update instruction is the N-1th update instruction and the latest update instruction is the Nth update instruction has been described, but for example, N-3 to N-1, or 1 to N As in -1, processing may be performed using update instructions for a plurality of times as precondition update instructions. In that case, a prerequisite update instruction display process is performed for each update instruction in each update stage. Further, as in N-1 and N, the processing may be performed using update instructions for a plurality of times as the latest update instructions. In this case, the latest update instruction display process is performed for each update instruction at each update stage.
In this way, it is also effective to freely set the premise update instruction and the latest update instruction stage (times) as long as the premise update instruction stage (times) and the latest update instruction stage (times) do not overlap. It is.
[0061]
FIG. 47 is a diagram showing a premise update instruction display processing flow.
Character or tag units are sequentially read from the original document storage buffer (S4701), and the following processing is repeated. If a character has been read (S4702), the read character is copied to the destination document storage buffer (S4703). If a tag has been read, it is determined whether the read tag is a deletion start tag <deleteX> (S4704). In the case of the deletion start tag <deleteX>, a precondition deletion mode display process (S4705) is performed. The precondition deletion mode display process will be described later with reference to FIG.
It is determined whether the read tag is an insertion start tag <insertX> (S4706). If the inserted tag is an insertion start tag <insertX>, a prerequisite insertion mode display process (S4707) is performed. This process will be described later with reference to FIG.
If the read tag is another tag, the read tag is copied to the previous document storage buffer (S4708).
The process ends when all the characters or tag units are read (S4709).
[0062]
FIG. 48 is a diagram showing a premise deletion mode display processing flow.
The deletion start tag <deleteX> is changed to a subscript start tag <SUB>, written to the destination document storage buffer (S4801), and the next character or tag unit is read from the original document storage buffer (S4802). If a character has been read (S4803), the read character is copied to the previous document storage buffer (S4804).
When the deletion end tag </ deleteX> has been read (S4805), the deletion end tag </ deleteX> is changed to a subscript end tag </ SUB> and written to the destination document storage buffer (S4806), and the processing ends. .
When another tag is read, the read tag is copied to the previous document storage buffer (S4807), and the process proceeds to the next reading (S4802).
[0063]
FIG. 49 is a diagram showing a premise insertion mode display processing flow.
The read insertion start tag <insertX> is changed to a superscript start tag <SUP>, written to the destination document storage buffer (S4901), and the next character or tag unit is read from the original document storage buffer (S4902). If a character has been read (S4903), the read character is copied to the previous document storage buffer (S4904).
When the insertion end tag </ insertX> has been read (S4905), the insertion end tag </ insertX> is changed to a superscript end tag </ SUP>, written to the destination document storage buffer (S4906), and the process ends. .
When another tag is read, the read tag is copied to the previous document storage buffer (S4907), and the process proceeds to the next reading (S4902).
[0064]
Next, the latest update instruction display process (S4611) of FIG. 46 will be described in detail. FIG. 50 is a diagram showing the latest update instruction display processing flow.
Character or tag units are sequentially read from the original document storage buffer (S5001), and the following processing is repeated. If a character is read (S5002), the read character is copied to the destination document storage buffer (S5003). When the tag is read, it is determined whether the read tag is a deletion start tag <deleteX> (S5004). In the case of the deletion start tag <deleteX>, the latest deletion mode display process (S5005) is performed. This process will be described later with reference to FIG.
It is determined whether the read tag is an insertion start tag <insertX> (S5006). If it is an insertion start tag <insertX>, the latest insertion mode display process (S5007) is performed. This process will be described later with reference to FIG.
If the read tag is another tag, the read tag is copied to the previous document storage buffer (S5008).
The process ends when all character or tag units are read (S5009).
[0065]
FIG. 51 is a diagram showing the latest deletion mode display processing flow.
The read deletion start tag <deleteX> is changed to a strikethrough start tag <STRIKE>, written to the previous document storage buffer (S5101), and the next character or tag unit is read from the original document storage buffer (S5102). If a character has been read (S5103), the read character is copied to the destination document storage buffer (S5104).
In the processing from S5105 to S5110, the latest update instruction to delete the character string before and after the character string deleted by the premise update instruction is executed, as in the sentence 4501 in FIG. 45 (corresponding to the item 4101 in FIG. 41). This is a process for displaying. If a strike-through line is drawn as the latest update instruction display for the part deleted by the premise update instruction, such as the “general” part of the 4501 sentence, that part (“general”) is displayed as the latest update instruction. Give the impression of deleting. Therefore, in this example, processing for canceling the strikethrough mode is performed on the subscript character string.
When the subscript start tag <SUB> is read (S5105), the strikethrough end tag </ STRIKE> is written in the destination document storage buffer (S5106), and then the subscript start tag <SUB> is copied. (S5107).
When the subscript end tag </ SUB> is read (S5108), the subscript end tag </ SUB> is copied to the destination document storage buffer (S5109), and then a strikethrough start tag <STRIKE> is written ( S5110).
If the deletion end tag </ deleteX> has been read (S5111), the deletion end tag </ deleteX> is changed to a strikethrough end tag </ STRIKE>, written to the destination document storage buffer (S5112), and the processing ends. .
When another tag is read, the read tag is copied to the previous document storage buffer (S5113), and the process proceeds to the next reading (S5102).
[0066]
FIG. 52 is a diagram showing the latest insertion mode display processing flow.
In this process, as in the sentence 4502 in FIG. 45 (corresponding to the item 4102 in FIG. 41), the latest update instruction for inserting a new character string into the character string inserted in the premise update instruction is displayed. It is processing of. When the character string “standard class” inserted in the latest update instruction is displayed as an underline with the superscript, for the part inserted in the premise update instruction as in the “standard creation” part of the 4502 sentence, the part ( "Standards") gives the impression that it was inserted in the premise update instruction. Therefore, in this example, when the superscript mode is in effect, processing for canceling the superscript mode is performed.
The superscript start tag <SUP> or superscript end tag </ SUP> that is closest to the read insertion start tag <insertX> is searched from the original document storage buffer (S5201). If the search result is the superscript start tag <SUP>, it is determined that the superscript mode is in progress (S5202). For example, the insertion start tag <insert1> of 4102 in FIG. 41 is converted to <SUP> in the premise insertion mode display process (FIG. 49), and the insertion end tag </ insert1> is also converted to </ SUP>. Assuming a state, when the insertion start tag <insert2> is read, if there is a superscript start tag <SUP> instead of a superscript end tag </ SUP>, it is in superscript mode. It can be seen that it is.
If it is in the superscript mode, the superscript end tag </ SUP> is written in the destination document storage buffer (S5203).
Thereafter, the insertion start tag <insertX> is changed to an underline start tag <U> (S5204), written to the previous document storage buffer, and the next character or tag unit is read from the original document storage buffer (S5205). If a character is read (S5206), the read character is copied to the destination document storage buffer (S5207).
If a tag other than the insertion end tag </ insertX> is read (S5208), the read tag is copied to the previous document storage buffer (S5209), and the process proceeds to the next reading (S5205).
When the insertion end tag </ insertX> is read (S5208), the insertion end tag </ insertX> is changed to the underline end tag </ U> and written to the previous document storage buffer (S5210).
If the superscript mode is in effect (S5211), the superscript start tag <SUP> is written in the previous document storage buffer (S5212), and the process ends.
[0067]
In the above-described example, the processing is performed so as to remove the update instruction tag that does not affect the display, but the processing may be performed so that the update instruction tag is left as in the first embodiment. This is effective in that a further update instruction can be input.
[0068]
Embodiment 3 FIG.
In the second embodiment, all the update instructions included in the update instruction file are displayed for the update instruction that is a prerequisite. In the present embodiment, in addition to the latest update instruction, a description will be given of a form in which only those related to the latest update instruction among the premise update instructions are displayed. That is, in the present embodiment, the update instructions that are not related to the latest update instruction are not displayed.
Specifically, in the second embodiment, processing for displaying all the update instructions in FIGS. 9 to 16 included in the first update instruction file (KOU.UPI) is performed. In contrast, in the third embodiment, among the update instructions in FIGS. 9 to 16 included in the first update instruction file (KOU.UPI), a figure included in the second update instruction file (OTSU.UPI). Processing for display is performed only for the update portion (FIGS. 9 to 14) in which at least a part of the update portion according to the update instruction from 33 to FIG. 40 overlaps.
[0069]
The example of a display by the latest update instruction | indication and related update instruction | indication display system which concerns on this Embodiment is shown. FIG. 53 is a diagram showing a display example (latest update instruction and related update instruction display method) of an XML document including the first and second update instructions.
Compared with the display example of the second embodiment (FIG. 45), the deletion of “others” by the first update instruction (FIG. 15) is not displayed, and the update instruction is ignored and treated as having been absent ( 4507, 5307). Also, the insertion of “document” by the first update instruction (FIG. 16) is not displayed, and the update instruction is ignored and treated as having not been present (4507, 5307).
By handling in this way, it is possible to confirm only the contents of the latest update instruction, and it is also possible to confirm related update instructions necessary for grasping the latest update instruction. In addition, it ignores the premise update instructions unrelated to the latest update instructions and shows the contents before the premise update instructions for that part, so when checking only the contents of the latest update instructions, no extra update instructions are displayed. Is particularly good.
[0070]
Display document generation processing by the latest update instruction and related update instruction display method will be described. FIG. 54 is a diagram showing a display document generation processing flow based on the latest update instruction and related update instruction display method.
The display document generation unit 205 acquires the update instruction count N from the document database 201 (S5401). If the update instruction count N = 0 (S5402), the process ends. When the update instruction count N = 1 (S5403), the update instruction reflection process and the related update instruction display process are omitted, and the latest update instruction display process is performed. If the number of update instructions N> 2 (S5404), the update instruction reflection process (S5406) is repeated from the first update instruction to the N-2th (S5405). The update instruction reflecting process is as shown in FIG. However, if there is no further update instruction, update instruction tags that do not affect the display (deletion start tag <deleteX>, deletion end tag </ deleteX>, insertion start tag <insertX>, insertion end tag </ insertX >) Without copying.
Thereafter, for the N-1th update instruction (S5408), the update instruction display (update instruction stage) X = N-1 is performed, and related update instruction display processing (S5409) is performed. This process will be described later with reference to FIG.
Finally, for the Nth update instruction (S5410), the update instruction display (update instruction stage) X = N is performed, and the latest update instruction display process (S5411) is performed. This process is the same as that in FIG.
[0071]
FIG. 55 is a diagram showing a related update instruction display processing flow.
Character or tag units are read sequentially from the original document storage buffer (S5501), and the following processing is repeated. If a character has been read (S5502), the read character is copied to the destination document storage buffer (S5503). If the tag is read, it is determined whether the read tag is a deletion start tag <deleteX> (S5504). In the case of the deletion start tag <deleteX>, the related deletion mode display process (S5505) is performed. The prerequisite deletion mode display process will be described later with reference to FIG.
It is determined whether the read tag is an insertion start tag <insertX> (S5506). If the tag is an insertion start tag <insertX>, a related insertion mode display process (S5507) is performed. This process will be described later with reference to FIG.
If the read tag is another tag, the read tag is copied to the previous document storage buffer (S5508).
The process ends when all character or tag units have been read (S5509).
[0072]
FIG. 56 is a diagram showing a related deletion mode display processing flow.
Deletion start tag <delete (X + 1)> or deletion end tag </ delete (X + 1)> of the latest update instruction closest to the read start tag <deleteX> in the original document storage buffer Is searched (S5601). If the search result is the deletion start tag <delete (X + 1)>, it is determined that the latest update instruction is in the delete mode (S5602). When the deletion start tag <delete1> of the sentence 4101 of the document under update shown in FIG. 41 is read, if there is a deletion start tag <delete2> instead of the deletion end tag </ delete2> in front of it It can be seen that the latest update instruction deletion mode is in progress. On the other hand, when the deletion start tag <delete1> of the sentence 4107 of the document being updated shown in FIG. 41 is read, there is neither a deletion start tag <delete2> nor a deletion end tag </ delete2> in front of it. It can be seen that there is no update instruction deletion mode.
When the latest update instruction deletion mode is in progress (an example in which at least a part of the update part according to the latest update instruction overlaps with the update part), delete mode display processing (S5603) is performed. This process will be described later with reference to FIG. On the other hand, when it is not in the delete mode of the latest update instruction (example in which the update part by the latest update instruction and the update part do not overlap at all), the deletion mode non-reflecting process (S5604) is performed. This process will be described later with reference to FIG.
[0073]
FIG. 57 is a diagram showing a deletion mode display processing flow.
The read deletion start tag <deleteX> is changed to a subscript start tag <SUB>, written to the destination document storage buffer (S5701), and the next character or tag unit is read from the original document storage buffer (S5702). If a character has been read (S5703), the read character is copied to the previous document storage buffer (S5704).
When the deletion end tag </ deleteX> is read (S5705), the deletion end tag </ deleteX> is changed to a subscript end tag </ SUB> and written to the destination document storage buffer (S5706), and the processing ends. .
If another tag is read, the read tag is copied to the previous document storage buffer (S5707), and the process proceeds to the next reading (S5702).
[0074]
FIG. 58 is a diagram showing a deletion mode non-reflecting process flow.
The read deletion start tag <deleteX> is not copied to the previous document storage buffer (S5801), but the next character or tag unit is read from the original document storage buffer (S5802). If a character has been read (S5803), the read character is copied to the previous document storage buffer (S5804).
If the deletion end tag </ deleteX> has been read (S5805), the read deletion end tag </ deleteX> is not copied to the previous document storage buffer (S5807), and the process ends.
If another tag is read, the read tag is copied to the previous document storage buffer (S5807), and the process proceeds to the next reading (S5802).
[0075]
The related insertion mode display process (S5507) shown in FIG. 55 will be described. FIG. 59 is a diagram showing a related insertion mode display processing flow.
The latest update instruction insertion start tag <insert (X + 1)> is searched between the read insertion start tag <insertX> and the corresponding insertion end tag </ insertX> in the original document storage buffer (S5901). ). If there is an insertion start tag <insert (X + 1)>, it is determined that the insertion mode of the latest update instruction is included (S5902). When the insertion start tag <insert1> of the sentence 4102 of the document being updated shown in FIG. 41 is read, the insertion start tag <insert2> of the latest update instruction is inserted between the corresponding insertion end tags </ insert1>. Since there is, it can be seen that the insertion mode of the latest update instruction is included. On the other hand, when the insertion start tag <insert1> of the sentence 4107 of the document being updated shown in FIG. 41 is read, the insertion start tag <insert2 of the latest update instruction is inserted between the corresponding insertion end tags </ insert1>. Since there is no>, it is understood that the insertion mode of the latest update instruction is not included.
When the insertion mode of the latest update instruction is included (an example in which the update part according to the latest update instruction and at least a part of the update part overlap), the insertion mode display process (S5907) is performed. This process will be described later with reference to FIG.
[0076]
Next, the deletion start tag <delete (X + 1)> or the deletion end tag </ delete (X +) of the latest update instruction closest to the read insertion start tag <insertX> in the original document storage buffer. 1)> is searched (S5903). If the search result is the deletion start tag <delete (X + 1)>, it is determined that the latest update instruction is in the delete mode (S5904). When the delete insertion tag <insert1> of the sentences 4103 and 4105 of the document being updated shown in FIG. 41 is read, there is a deletion start tag <delete2> instead of the deletion end tag </ delete2> in front of it. It can be seen that the deletion mode of the latest update instruction is in progress. On the other hand, when the insertion start tag <insert1> of the sentence 4107 of the document being updated shown in FIG. 41 is read, there is neither a deletion start tag <delete2> nor a deletion end tag </ delete2> in front of it. It can be seen that there is no update instruction deletion mode.
When the latest update instruction deletion mode is in progress (an example in which the update part according to the latest update instruction overlaps at least part of the update part), the insertion mode display process (S5907) is performed.
[0077]
A deletion start tag <delete (X + 1)> of the latest update instruction is searched between the read insertion start tag <insertX> and the corresponding insertion end tag </ insertX> in the original document storage buffer (S5905). ). If there is a deletion start tag <delete (X + 1)>, it is determined that the deletion mode of the latest update instruction is included (S5906). When the insertion start tag <insert1> of the sentences 4104 and 4106 of the document being updated shown in FIG. 41 is read, the deletion start tag <delete2 of the latest update instruction is inserted between the corresponding insertion end tags </ insert1>. >, It is understood that the deletion mode of the latest update instruction is included. On the other hand, when the insertion start tag <insert1> of the sentence 4107 of the document being updated shown in FIG. 41 is read, the deletion start tag <delete2 of the latest update instruction is inserted between the corresponding insertion end tags </ insert1>. Since there is no>, it can be seen that the latest update instruction deletion mode is not included.
When the deletion mode of the latest update instruction is included (an example in which the update part by the latest update instruction and at least a part of the update part overlap), the insertion mode display process (S5907) is performed.
[0078]
If none of the above determinations (S5902, S5904, S5906) is applicable (an example in which the update part by the latest update instruction and the update part do not overlap at all), the insertion mode non-reflecting process (S5908) is performed. Do. This process will be described later with reference to FIG.
[0079]
FIG. 60 is a diagram showing an insertion mode display processing flow.
The read insertion start tag <insertX> is changed to a superscript start tag <SUP>, written to the destination document storage buffer (S6001), and the next character or tag unit is read from the original document storage buffer (S6002). If a character is read (S6003), the read character is copied to the previous document storage buffer (S6004).
When the insertion end tag </ insertX> is read (S6005), the insertion end tag </ insertX> is changed to a superscript end tag </ SUP>, written to the destination document storage buffer (S6006), and the process ends. .
When another tag is read, the read tag is copied to the previous document storage buffer (S6007), and the process proceeds to the next reading (S6002).
[0080]
FIG. 61 is a diagram showing an insertion mode non-reflecting process flow.
The read insertion start tag <insertX> is not copied to the previous document storage buffer (S6101), and the next character or tag unit is read from the original document storage buffer (S6102). If a character is read (S6103), the read character is not copied to the previous document storage buffer (S6104), and the process proceeds to the next reading (S6102).
When the insertion end tag </ insertX> is read (S6105), the read insertion end tag </ insertX> is not copied to the previous document storage buffer (S6106), and the process ends.
When another tag is read, the read tag is copied to the previous document storage buffer (S6107), and the process proceeds to the next reading (S6102).
[0081]
In the above-described example, the processing is performed so as to remove the update instruction tag that does not affect the display, but the processing may be performed so that the update instruction tag is left as in the first embodiment. This is effective in that a further update instruction can be input.
[0082]
Embodiment 4 FIG.
The editing position described above is obtained by sequentially extracting tags for specifying the document structure from the beginning of the document. As an editing position specifying method, identification information (for example, a chapter or a section) of sentence structure units (in this example) Then “ It is also effective to use <no> ”and“ 1.1 ”.
For example, the editing position (tag) in FIG. <section><ss1><p>, editing position: <section><no> 1. <ss1><no> 1.1 <p> and the editing position (tag) in FIG. 13: <section><ss1><p><ss1><p><ss1><p><ss1><p><ss1><p>, editing position: <section><no> 1. <ss1><no> 1.5 It can be expressed as <p>. The same applies to the second and subsequent update instructions. As described above, the update instruction execution unit 211 performs editing by comparing the document structure tag that designates the editing position with the document structure tag included in the document being updated stored in the document document being updated. Specify a term (an example of a structural unit on a document). In this example, the identification information of the structural unit of the document structure tag that specifies the editing position (for example, By searching for <no> 1.1), the item to be edited can be specified.
[0083]
An annotation system 1 (an example of a structured document update management device) is a computer, and each element can execute processing by a program. Further, the program can be stored in a storage medium so that the computer can read the program from the storage medium.
[0084]
【The invention's effect】
From the document database, the original structured document (XX standard in the example), the first update instruction (KOU.UPI in the example) corresponding to the original structured document, and the second update instruction (OTSU. In the example). UPI), and an edit document (FIG. 41 in the example) is generated by using the second update instruction tag at the edit position in the structured document in which the first update instruction has been inserted, Since the first update instruction tag is converted into the first display decoration tag (the premise update instruction display processing in S4609 in the example), the second update instruction tag in the edited document is converted into the second display decoration tag. (The latest update instruction display process of S4611), the update instruction contents for each update stage can be identified and confirmed.
[0085]
The display document generation unit includes a first update instruction tag sandwiched between a start tag and an end tag of the first update instruction tag among the first update instruction tags in the edited document. Since only the first update instruction tag that overlaps at least partly with the second update instruction region sandwiched between the start tag and the end tag is converted into the first display decoration tag (related update instruction display processing in S5409), Only information necessary for grasping the intention of the latest update instruction can be displayed.
[0086]
The display document generation unit performs a non-reflection process for displaying a state in which there is no update instruction for the first update instruction that is not converted to the first display decoration tag (the deletion mode non-reflection process of S5604, Since the deletion mode non-reflecting process in S5908), an update instruction unnecessary for grasping the intention of the latest update instruction can be eliminated.
[0087]
Since each display decoration tag is a tag with a different decoration that can be distinguished from each other for display, there is no confusion between the premise update instruction and the latest update instruction.
[Brief description of the drawings]
FIG. 1 is a diagram showing a network environment of an annotation system.
FIG. 2 is a diagram illustrating a configuration example of an annotation system.
FIG. 3 is a diagram illustrating a configuration example of a management table in a document database.
FIG. 4 is a diagram showing an overall processing flow of document editing processing.
FIG. 5 is a diagram showing a display example of an edited document selection screen.
FIG. 6 is a diagram illustrating an example of an XML document that is an edited document.
FIG. 7 is a diagram illustrating a display example of a document display screen based on an initial document being updated.
FIG. 8 is a diagram illustrating a display example (update instruction display method) of a document display screen after a first update instruction is input.
FIG. 9 is a diagram illustrating an example of a first update instruction for a term of 1.1.
FIG. 10 is a diagram illustrating an example of a first update instruction for a term of 1.2.
FIG. 11 is a diagram illustrating an example of a first update instruction for a term of 1.3.
FIG. 12 is a diagram illustrating an example of a first update instruction for a term of 1.4.
FIG. 13 is a diagram illustrating an example of a first update instruction for a term of 1.5.
FIG. 14 is a diagram illustrating an example of a first update instruction for a term of 1.6.
FIG. 15 is a diagram illustrating an example of a first update instruction (deletion) for the item of 1.7;
FIG. 16 is a diagram illustrating an example of a first update instruction (insertion) for a term of 1.7.
FIG. 17 is a diagram illustrating an example of an XML document in which a first update instruction tag is inserted.
FIG. 18 is a diagram illustrating a display document generation processing flow according to an update instruction display method.
FIG. 19 is a diagram showing an update instruction reflecting process flow;
FIG. 20 is a diagram showing a deletion mode reflection processing flow;
FIG. 21 is a diagram showing an insertion mode reflection processing flow;
FIG. 22 is a diagram showing an update instruction display processing flow.
FIG. 23 is a diagram showing a deletion mode display processing flow;
FIG. 24 is a diagram showing an insertion mode display processing flow.
FIG. 25 is a diagram illustrating a display document related to a first update instruction according to an update instruction display method.
FIG. 26 is a diagram illustrating an example of a configuration part related to a change in display method.
FIG. 27 is a diagram showing a display document generation processing flow based on the all update instruction reflection method;
FIG. 28 is a diagram showing a display document related to a first update instruction by the all update instruction reflection method;
FIG. 29 is a diagram showing a display example (all update instruction reflecting method) of the document display screen after the first update instruction is input.
FIG. 30 is a diagram showing a configuration example of a management table in a document database after a first update instruction is registered.
FIG. 31 is a diagram showing a display example of an edit document selection screen including a document in response to a first update instruction.
FIG. 32 is a diagram illustrating a display example (update instruction display method) of a document display screen after a second update instruction is input.
FIG. 33 is a diagram illustrating an example of a second update instruction for the item 1.1.
FIG. 34 is a diagram illustrating an example of a second update instruction for a term of 1.2.
FIG. 35 is a diagram illustrating an example of a second update instruction for the item of 1.3.
FIG. 36 is a diagram illustrating an example of a second update instruction for the item of 1.4.
FIG. 37 is a diagram illustrating an example of a second update instruction for a term of 1.5.
FIG. 38 is a diagram illustrating an example of a second update instruction for a term of 1.6.
FIG. 39 is a diagram illustrating an example of a second update instruction (insertion) for the item of 1.7.
FIG. 40 is a diagram illustrating an example of a second update instruction (deletion) for the item of 1.7.
FIG. 41 is a diagram illustrating an example of an XML document in which a second update instruction tag is inserted.
FIG. 42 is a diagram illustrating a display example (all update instruction reflecting method) of a document display screen after a second update instruction is input.
FIG. 43 is a diagram showing a configuration example of a management table in a document database after registering a second update instruction.
FIG. 44 is a diagram showing a display example of an edited document selection screen including a document according to a second update instruction.
FIG. 45 is a diagram illustrating a display example (multiple update instruction display method) of a document display screen of an XML document including first and second update instructions.
FIG. 46 is a diagram illustrating a display document generation processing flow based on a multiple update instruction display method.
FIG. 47 is a diagram illustrating a premise update instruction display processing flow.
FIG. 48 is a diagram showing a precondition deletion mode display processing flow.
FIG. 49 is a diagram showing a precondition insertion mode display processing flow.
FIG. 50 is a diagram illustrating a latest update instruction display processing flow.
FIG. 51 is a diagram showing a latest deletion mode display processing flow;
FIG. 52 is a diagram showing a latest insertion mode display processing flow.
FIG. 53 is a diagram showing a display example (latest update instruction and related update instruction display method) of an XML document including first and second update instructions.
FIG. 54 is a diagram showing a display document generation processing flow based on a latest update instruction and related update instruction display method.
FIG. 55 is a diagram showing a related update instruction display processing flow.
FIG. 56 is a diagram showing a related deletion mode display processing flow;
FIG. 57 is a diagram showing a deletion mode display processing flow;
FIG. 58 is a diagram showing a deletion mode non-reflecting process flow;
FIG. 59 is a diagram showing a related insertion mode display processing flow.
FIG. 60 is a diagram showing an insertion mode display processing flow.
FIG. 61 is a diagram showing an insertion mode non-reflection process flow;
[Explanation of symbols]
201 Document Database, 202 Edited Document Selection Unit, 203 Edited Document Generation Unit, 204 Updating Document Storage Unit, 205 Display Document Generation Unit, 206 Document Transmission Unit, 207 Update Instruction Generation Program Distribution Unit, 208 Update Instruction Generation Program Storage Unit 209 Update instruction reception unit 210 Update instruction storage unit 211 Update instruction execution unit 212 Update confirmation processing unit 213 Display method input unit

Claims (8)

A structured document update management apparatus for converting a structured document including a plurality of stages of update instructions into a display document and outputting the display document, the structured document update management apparatus having the following elements: (1) an original structured document described using a document structure tag that identifies the structure of the document;
An update instruction for the original structured document, a first update instruction including an edit position specified by a document structure tag and a position specifying character string extracted from the original structured document;
An update instruction for the structured document in which the first update instruction is inserted at the editing position in the original structured document using the first update instruction tag, and the document structure tag and the first update instruction are inserted. Document database for storing the second update instruction including the editing position designated by the position designation character string extracted from the structured document, and the original structured document from the document database. The first update instruction and the second update instruction corresponding to the original structured document are acquired, and the first update instruction tag is added to the edit position in the acquired original structured document. Insert with
Further, an edit document generation for generating an edit document by inserting the acquired second update instruction into an edit position in the structured document in which the first update instruction is inserted using the second update instruction tag (3) The first update instruction tag in the edited document is converted into a first display decoration tag, and the second update instruction tag in the edited document is converted into a second display decoration tag. Display document generation unit for generating a document (4) Document output unit for outputting the generated display document.   The display document generation unit includes a first update instruction tag sandwiched between a start tag and an end tag of the first update instruction tag among the first update instruction tags in the edited document. The first update instruction tag that is at least partially overlapped with the second update instruction area sandwiched between the start tag and the end tag is converted into the first display decoration tag. 1. The structured document update management device according to 1.   The display document generation unit performs a non-reflecting process for displaying a state in which there is no update instruction for the first update instruction that is not converted to the first display decoration tag. Structured document update management device.   The first update instruction and the second update instruction each include at least an edit type including deletion and insertion, and a first delete display decoration tag converted from the first update instruction tag whose edit type is deletion, The first insertion display decoration tag converted from the first update instruction tag whose edit type is insertion and the second deletion display decoration converted from the second update instruction tag whose edit type is deletion The tag and a second insertion display decoration tag converted from a second update instruction tag whose edit type is insertion are different decoration tags that can be distinguished from each other on display. Structured document update management device described in 1.   2. The structured document update management apparatus according to claim 1, wherein the document output unit transmits to a device having a browser for displaying the structured document. An original structured document described using a document structure tag that specifies the structure of the document, and an update instruction for the original structured document, the document structure tag and a position-specified character string extracted from the original structured document The first update instruction including the edit position designated by the above and the update instruction for the structured document in which the first update instruction is inserted at the edit position in the original structured document using the first update instruction tag The document structure tag and the second update instruction including the editing position designated by the position designation character string extracted from the structured document in which the first update instruction is inserted are stored in association with each other. Structured document update management method using a structured document update management apparatus capable of accessing a document database for the purpose, comprising the following elements: (1) Structured document update management apparatus Prepare for Collecting document generation unit, from the document database, and the original structured document, to obtain a first update instruction and a second update instruction corresponding to the original structured document, the first update instruction obtained, and acquisition source Insert the first update instruction tag at the editing position in the structured document,
Further, a step (2) of generating an edited document by inserting the acquired second update instruction into an edit position in the structured document in which the first update instruction is inserted using the second update instruction tag. ) The display document generation unit provided in the structured document update management device converts the first update instruction tag in the edited document into the first display decoration tag, and converts the second update instruction tag in the edited document to the second (3) A step in which the document output unit provided in the structured document update management device outputs the generated display document. An original structured document described using a document structure tag that specifies the structure of the document, and an update instruction for the original structured document, the document structure tag and a position-specified character string extracted from the original structured document The first update instruction including the edit position designated by the above and the update instruction for the structured document in which the first update instruction is inserted at the edit position in the original structured document using the first update instruction tag The document structure tag and the second update instruction including the editing position designated by the position designation character string extracted from the structured document in which the first update instruction is inserted are stored in association with each other. the document database to the computer to be accessible structured document updating management device for the following processes a computer-readable recording medium storing a program for executing the (1) structured document updating management instrumentation Editing document generator that comprises, from the document database, and the original structured document, to obtain a first update instruction and a second update instruction corresponding to the original structured document, the first update instruction obtained, obtains Inserted at the editing position in the original structured document using the first update instruction tag,
Further, a process of generating an edited document by inserting the acquired second update instruction into the editing position in the structured document in which the first update instruction is inserted using the second update instruction tag (2 ) The display document generation unit provided in the structured document update management device converts the first update instruction tag in the edited document into the first display decoration tag, and converts the second update instruction tag in the edited document to the second (3) A process in which the document output unit included in the structured document update management device outputs the generated display document. An original structured document described using a document structure tag that specifies the structure of the document, and an update instruction for the original structured document, the document structure tag and a position-specified character string extracted from the original structured document The first update instruction including the edit position designated by the above and the update instruction for the structured document in which the first update instruction is inserted at the edit position in the original structured document using the first update instruction tag The document structure tag and the second update instruction including the editing position designated by the position designation character string extracted from the structured document in which the first update instruction is inserted are stored in association with each other. the document database to the computer to be accessible structured document updating management apparatus for, edit document generation unit included in the program (1) structured document updating management apparatus for executing the following steps, the document database The original structured document, the first update instruction and the second update instruction corresponding to the original structured document are acquired, and the acquired first update instruction is set to the editing position in the acquired original structured document. , Insert using the first update instruction tag,
Further, a procedure (2) for generating an edited document by inserting the acquired second update instruction into the edit position in the structured document in which the first update instruction has been inserted, using the second update instruction tag. ) The display document generation unit provided in the structured document update management device converts the first update instruction tag in the edited document into the first display decoration tag, and converts the second update instruction tag in the edited document to the second (3) A procedure in which the document output unit provided in the structured document update management device outputs the generated display document.

Images