JPH0863462A - Method and device for document processing - Google Patents

Abstract

PURPOSE: To easily discriminate whether document information is altered by partial data of a document from when one user confirms the document information last until when the user confirms it this time. CONSTITUTION: A document information group 61 holding plural pieces of document information and update time information and pieces of confirmation time information by users of the pieces of document information held in the document information group 61 are stored in user-distinctive confirmation time information 621. When a user specifies and reads out document information held in the document information group 61, the update time information of the read document information is read out, it is judged whether or not the update time information of the document information is included in the confirmation time information by the users, and the document information is displayed distinctively at a display part 4 according to the judgement.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a document processing method and apparatus for electronically handling a document.

[0002]

2. Description of the Related Art Document information is a group of data that can be expressed as a document, as shown in FIG. 2, and can be described as structured document data defined by SGML (ISO8879). As shown in FIG. 3, the structured document data can be stored in units of structure, for example, by using a conventional file directory structure.
The stored structured data group is information that can be recognized by humans as one document. To recognize it, means such as "display", "print" or "listen" are applied. Further, for example, it is possible to share data from other document information by using a conventional technique such as a link. A group of structured data as shown in FIG. 4 provides a document format and forms one document information. This document information can be displayed as a document by using a conventional hypertext system as shown in FIG. To handle the documents, I used something like a document editor to edit them.
Conventionally, when a document confirmed in the past is changed, in order to confirm the information, for example, remember the date and time of the last reference, and look at the update date and time of the current document,
It was necessary to check whether it was newer than the time of the previous confirmation, and to check if there were any unconfirmed parts. At this time, if there is no memory or record of the date and time when the document information was confirmed last time, it was necessary for a human to read each document and check whether or not the information was confirmed. There was also a method of always saving the entire document checked last time and comparing it with the current document, but it is inefficient in terms of storage capacity. On the other hand, like SCCS and RCS in UNIX systems, only the information updated by editing the document in use is saved, and the previous information is known by comparing with the current document. There is a system that can. In this system, since only updated information is stored, the problem of the storage capacity can be solved. However, in these systems, the target of processing is the entire document and the unit of comparison is a line, and processing cannot be performed in the structural unit of the structured document. In some systems for structured documents, the whole document is processed, but there is a system in which the unit of comparison is each structure and only updated information is stored. In this system, as shown in FIG. 6, by changing the display attribute such as displaying a black line indicating the update in the vicinity, the unconfirmed information updated from the previously confirmed document is expressed in structural units. I was able to. Display example 7 in the figure
This is an unconfirmed part where the information has been updated from the document at the time of the previous confirmation.

[0003]

When the information is used by a plurality of persons, especially in the case of document information whose contents are frequently updated, the same document data is maintained by a plurality of persons or a specific person with time. It will be updated and updated. However, as a user who refers to a document, there is a demand that he always wants to see and check the latest document information. Therefore, the document information whose contents are frequently updated is shared and referred to by a plurality of users. In this way, when a certain document information is shared by a plurality of users and the content is updated particularly frequently, the information is updated without notice to the user who is referring to the document information, The problem occurs that there are unconfirmed parts. Therefore, each user has a request to check the shared document for the unconfirmed information that has been updated since the last confirmation by the user. That is, although the document information is shared and used by a plurality of people, there arises a problem that the information requested by the user at the time of reference and the information to be confirmed is different for each user. Therefore, in a structured document of such a form, even if the user tries to obtain the latest information for each user, it becomes difficult for the user to know which information in the document has been confirmed and which information has not been confirmed. There was a problem to say. In addition, there is no guarantee that all changed parts will be confirmed at each reference time of the document, and there will be a problem that it will not be known whether unconfirmed parts have been confirmed. That is, even if the unconfirmed part is displayed, there is a problem that it is not synonymous with the confirmation of the unconfirmed part.

[0004]

In order to solve the above problems, the present invention provides a holding means for holding a plurality of pieces of document information and update time information, and a document information held by the holding means. Storage means for storing confirmation time information for each user, reading means for reading out the document information held in the holding means by specifying the user, and update time information for the document information read by the reading means Is a control unit that determines whether or not it is included in the confirmation time information for each user, and controls to display the determination result in a distinguishable manner,
There is provided a document processing device having: In order to solve the above-mentioned problems, the present invention is preferably characterized in that document information is handled in units of parts. In order to solve the above-mentioned problems, the present invention is preferably characterized in that the confirmation information at the time of confirming a document in units of readers is held for each update time. In order to solve the above problems, the present invention is preferably characterized in that the confirmation information when the document is confirmed for each reader in document element units is compressed and held. In order to solve the above problems, the present invention is preferably
It is characterized in that the confirmation information at the time of confirming a document in units of readers is compressed and retained by utilizing a continuous time range. In order to solve the above-mentioned problems, the present invention is preferably characterized in that the confirmation information at the time of confirming a document for each reader on a partial basis is retained for each document element. In order to solve the above problems, the present invention preferably holds, for each document element, confirmation information when a document is confirmed in partial units for each reader, and the confirmation information uses a partial structure of the document. It is characterized by compressing and holding. In order to solve the above-mentioned problem, the present invention is preferably characterized in that the present confirmation status is extracted based on the confirmation information that is compressed and held. In order to solve the above-mentioned problems, the present invention preferably confirms the current confirmation based on the confirmation information stored in a compressed manner when the comparison result of the document confirmation information and the document update information is displayed in a distinguishable manner. It is characterized by extracting the situation.

In order to solve the above problems, the present invention is a document processing method for reading and processing desired document information from a document file storing a plurality of document information, which is stored in the document file. Storing the confirmation time information for each user of the document information stored therein, the step of identifying the user and reading the desired document information from the document file, and the update time information of the read document information is the user And a step of determining whether or not each confirmation time is included in the confirmation time information and displaying the information in a distinguishable manner according to the determination. In order to solve the above-mentioned problems, the present invention is preferably characterized in that document information is handled in units of parts. In order to solve the above problems,
The present invention is preferably characterized in that the confirmation information at the time of confirming the document in units of readers is held for each update time. In order to solve the above problems, the present invention is preferably characterized in that the confirmation information when the document is confirmed for each reader in document element units is compressed and held. In order to solve the above-mentioned problems, the present invention is preferably characterized in that the confirmation information at the time of confirming a document in units of readers is compressed and held by utilizing a continuous time range. To do. In order to solve the above-mentioned problems, the present invention is preferably characterized in that the confirmation information at the time of confirming a document for each reader on a partial basis is retained for each document element. In order to solve the above-mentioned problems, the present invention preferably holds confirmation information for each document element when confirming a document for each reader in partial units.
It is characterized in that the confirmation information is compressed and held by utilizing the partial structure of the document. In order to solve the above problems,
The present invention is preferably characterized in that the current confirmation status is extracted based on the confirmation information that is compressed and held. In order to solve the above-mentioned problems, the present invention preferably confirms the current confirmation based on the confirmation information stored in a compressed manner when the comparison result of the document confirmation information and the document update information is displayed in a distinguishable manner. It is characterized by extracting the situation.

In a document processing apparatus that handles document information as structured data, a means for holding information at the time of confirmation for each reader and a means for holding updated information at the time of updating the document are provided to confirm the previous time for each reader. The above problem is solved by extracting and clarifying unconfirmed information whose information has been updated since the point of time, and confirming the unconfirmed information.

[0007]

【Example】

(First Embodiment) A preferred embodiment of the present invention will be described below with reference to the accompanying drawings.

FIG. 1 is a block diagram showing the schematic arrangement of the document processing apparatus of this embodiment.

In FIG. 1, 1 is a keyboard (KB), 2
Is a pointing device such as a mouse, and is a CRT.
It is used to move a cursor or the like on the screen of the display unit 4 such as to input a desired command or data. Reference numeral 3 is a CPU for controlling the entire apparatus, 4 is a display unit such as a liquid crystal display or CRT, and 5 is a program for holding data and programs according to the present embodiment.
It is a storage unit for executing control by the PU 3. Reference numeral 6 denotes an auxiliary storage device for holding programs and various data in a nonvolatile manner. The storage unit 5 and the auxiliary storage device 6 may be used as a program / data holding storage device as a whole without making a distinction.

Reference numeral 7 denotes a timer, which measures a predetermined time according to an instruction from the CPU 3, and has a function of measuring the current time and a calendar function. Also, in the document processing device of the present embodiment,
When reading or saving the document data, it is necessary for the user (user) to specify the password and ID code without fail.

As shown in FIG. 1, the storage unit 5 stores a document display program 511, a document change program 521, and a document confirmation program 531. The auxiliary storage device 6 stores current document information 61 and user-specific confirmation time information 621.

In this embodiment, the document is treated as structured document data composed of document elements having the update time Time as an attribute as shown in FIG. The user-specific confirmation time information 621 holds the already-confirmed document update time for each user, for example, in the form shown in FIG. The confirmed document update time is the time of the update time attribute Time of the already confirmed document element.
In the present embodiment, it is assumed that the same update time does not exist in the update time attributes of the document element.

FIG. 9 shows a flowchart of the entire system of this embodiment. When the system is started by a certain user, an event is waited for in the event loop of step S901.
When the display operation is performed, the document is displayed in step S902. When the editing operation is performed, the document is changed in step S903. When the end operation is performed, the system ends. When an editing event occurs, editing is performed according to the flowchart of FIG. The operation procedure is shown below. In step S1001, the current document information 61 is extracted from the auxiliary storage device 6. The document editing process of step S1002 is performed according to the flowchart of FIG. The operation procedure is shown below. In step S1101, the document information is edited in document element units. The update time attribute Time of the document element updated in step S1102 is set to the current time as the update time of the document element. Further, in step S1103, the fact that editing has been performed is the same as the confirmation regarding that document element, so document confirmation processing is performed. As described above, in this embodiment, the same time is not recognized as the update time when the document is edited. This can be achieved, for example, by using a conventional UNIX system such as time display by integrating from a specific day.

Subsequently, document confirmation processing is performed according to the flow chart of FIG. Step S1201
If the document element to be confirmed has a child element whose parent is the element, it is considered that the child element has also been confirmed. Therefore, in step S1202, the document confirmation process is recursively performed on the child element. To do. Then, step S1
At 203, the update time of the update time attribute Time of the document element to be confirmed is added to the table of the confirmation time information for each user 621. At this time, if the time indicated by the update time attribute is already included in the user-specific confirmation time information, the update time need not be newly added to the user-specific confirmation time information. By doing so, the document confirmation program 531 is realized. When all editing is completed in step S1104, the document element editing process is completed. The edited document is stored in the current document information 61 in step S1003. This current document information 61 is obtained in step S1002.
Thus, it may be stored every time the document element is edited.

The case of displaying step S902 in FIG. 9 will be described below.
It shows according to the flow chart of FIG. When a document is to be displayed, the current document information 61 is extracted from the auxiliary storage device 6 in step S1301. Then step S1302
Then, the document is displayed on the CRT 4 for each document element according to the structure. The document element display process will be described below according to the flowchart of FIG. First, in step S1401, the current display attributes are saved. In step S1402, if the time of the update time attribute Time of the document element is not included in the confirmation time information 621 of the user who is currently displaying, it means that the update of the document element has not been confirmed yet. In step S1403, the display attribute of the document element is changed. To change the display attribute, as shown in FIG. 15, for example, the changed portion is shaded and its color is changed, or the standard of the display attribute is set to a light color, and the change is made darker each time. Things can be considered. Then, in step S1404, the head of the document element is displayed according to the determined display attribute. Next step S1405
Then, the contents of the document element are displayed, but step S1
If it is determined in 406 that there is a document element in the content, the document element display processing is recursively performed in step S1407. The content is displayed until the content of the document is completed. If it is determined in step S1408 that the contents are complete, the end of the document element is displayed in step S1409. Finally, in step S1410, the stored display attributes are restored, and the document element display processing ends.
In step S1303, this document element display processing is performed until the display of all the document elements in the document is completed.

By the above processing, a display example as shown in FIG. 16 can be realized.

Next, in step S1304, if a conventional pointer such as a cursor or a mouse for designating a position is moved, the pointer is moved in step S1305. In step S1306, by clicking the mouse as usual, or pressing a button on the screen,
If confirmation processing is requested, in step S1307, confirmation processing is performed on the document element having the pointer that currently specifies the position of the cursor or the like. This confirmation processing is the same as the confirmation processing shown in FIG. 12 of the present embodiment. When the confirmation process is completed in step S1308, the document display process ends and the process returns to the event loop.

The document display program 511 is realized by these. The document element display process may be performed each time the document element is confirmed. By doing so, the confirmation information for each user is always held in the confirmation time information 621 for each user when the user confirms the document element, and the update time of the update time attribute Time of the document element is recorded in the confirmation time information 621 for each user. By checking if
Unconfirmed information of each user can be known in units of document elements. Although the present embodiment is realized by event driving, each event driven process may be performed by an independent program sharing document information. Further, in the present embodiment, the display program and the editing program are separated, but a program in which display and editing are integrated may be used as the editing program, and the display program may be omitted. According to the present embodiment, it is possible to extract and identify unconfirmed information for each user from a document in document element units. Therefore, there is an advantage that the document information that each user needs to confirm can be easily obtained. Further, no matter how many times the entire document is displayed, unconfirmed document elements are clearly shown as unconfirmed until confirmation processing is performed.

(Second Embodiment) In the first embodiment, when the document element is confirmed, the child element having the element as the parent is also confirmed, but the invention is not limited to this. In this embodiment, it is assumed that only the designated document element is confirmed,
A case will be described below in which the child element having the document element subjected to the confirmation processing as a parent is separately confirmed. Embodiments of the present invention will be described below with reference to the drawings. In the block diagram of the present embodiment, the document confirmation program 531 of FIG. 1 is changed to another document confirmation program 532 (not shown). The document in this embodiment is the same as that in FIG. 7 of the first embodiment. The flowchart of the entire system of this embodiment is similar to that of FIG. When the display operation is performed, it is the same as in the first embodiment.
When the editing operation is performed, it is the same as in the first embodiment. When the end operation is performed, the system ends. When the document confirmation process is performed during the display or edit process, the document confirmation process is performed according to the flowchart of FIG. Only the update time of the update time attribute Time of the document element confirmed in step S1701 is
It is added to the table of the confirmation time information 621 for each user. That is, even if the document element to be confirmed has a child element whose parent is the element, the child element is not considered to be confirmed. In this case, the child element whose parent is the document element subjected to the confirmation processing needs to be separately confirmed. When the update time is added to the table, the update time attribute T
If the time indicated by ime is included in the confirmation time information for each user, it is not necessary to newly add the update time to the confirmation time information for each user. By doing so, the document confirmation program 532 is realized. By using this document confirmation program 532, when there is a document element such as mixed content in SGML, a child element whose parent is the element to be confirmed and a character string of the direct content of the parent element are distinguished, The effect is that you can check each.
Further, there is an effect that the document confirmation processing itself becomes simple.

(Third Embodiment) In the first and second embodiments, all the confirmation times when the user has confirmed in the past are added to the confirmation time information 621 for each user, but the present invention is not limited to this. Absent. In the present embodiment, a case will be described in which, when all the updates before a certain time have been confirmed, the confirmation time information before that time is deleted. Also, if the update time Time existing in the document information has confirmed all update times between two points in time, the confirmation information is compressed by using the time range between those two points in time. The case will be described.
Embodiments of the present invention will be described below with reference to the drawings. In the block diagram of this embodiment, the document display program 511 of FIG. 1 is changed to another document display program 513, the document confirmation program 531 is changed to another document confirmation program 533, and the confirmation information compression program 543 is stored in the storage device 5. In addition (not shown). Further, the confirmation time information 621 for each user is changed to the confirmation time information 623 for each user. The user-specific confirmation time information 623 holds the already-confirmed document update time for each user in time order, for example, as shown in FIG. At this time, when two times are in the column, the time between the two times, that is, a time range is shown, and when one time is in the column, the time itself is shown. However, the time in the first column is considered to indicate that the time before that time has been confirmed. The document in this embodiment is the same as that in FIG. 7 of the first embodiment. The flowchart of the entire system of this embodiment is similar to that of FIG. When the display operation is performed, the document is displayed. When the editing operation is performed, it is the same as in the first embodiment. When the end operation is performed, the system ends. When a display event occurs, the same processing as in FIG. 13 is performed. Step S13
The document element display process of steps equivalent to 02 is shown according to the flowchart of FIG. First, in step S1901, the current display attributes are saved. Document element update time attribute Tim
If the time e is included in the confirmation time information 623 of the user who is currently displaying, that is, step S1
If it is determined in 902 that the time of the update time attribute Time is listed in 623, or the range specified by the two times, or the range before the first time includes the time, the update occurs. If not, go to the next display step. If not, it means that the update of the document element has not been confirmed yet, and thus step S1
In 903, the display attribute of the document element is changed. The change of the display attribute is the same as that in the first embodiment. Then, step S1904
Then, the top of the document element is displayed according to the determined display attribute. Next, the contents of the document element are displayed in step S1905, but if it is determined in step S1906 that there is a document element in the contents, step S1907.
The document element display processing is performed recursively with. The content is displayed until the content of the document is completed. Step S1
If the contents are completed in 908, the end of the document element is displayed in step S1909. Finally, in step S1910,
The display attributes are restored to the saved display attributes, and the document element display processing ends. The display example by the above processing is, for example, as shown in FIG. 16, as in the first embodiment. If the document confirmation process is performed during the display or edit process,
Document confirmation processing is performed according to the flowchart of 20. The update time of the update time attribute Time of the document element confirmed in step S2001 is the confirmation time information for each user.
If not within the confirmation time range of 623, step S2002
Then, the update time is added to the table of the confirmation time information 621 for each user. By doing so, the document confirmation program 533 is realized. When the system is shut down, see Figure 2.
Confirmation time information for each user according to the flowchart in 1 6
21 are compressed. First, the current document information 61 is read, and a list of the update times Time of each current document element is shown in FIG.
In step S2101, the files are sorted and created in the order of update time, as shown in FIG. For each update time listed in the Time list table, if it is listed in the confirmation time range of the user-specific confirmation time information 623, in step S2102,
Add a check mark in the column of the time list table. Update time of each checked document element Tim
In the list of e, if there are a plurality of columns for which the check is continuous in step S2103, the oldest update time and the latest update time of the column for which the check is continuous are combined in step S2104. With respect to those that are provided and scattered, the user-specific confirmation time information 623 is reconstructed in such a manner that one update time is placed in one column. At this time, in step S2105, if the column having the oldest update time has two times, step S210
In step 6, put only one newer time in the box.
By doing so, the confirmation information compression program 543 is realized. In this embodiment, the confirmation time information 623 for each user is set to 2
Although it is treated as a table having one time column, it may be realized as having only one time column. In this case, it is realized that only the confirmation information before the start time is compressed. By using the document confirmation program 533 and the confirmation information compression program 543, there is an advantage that the amount of confirmation time information that must be saved for each user can be reduced.

(Fourth Embodiment) In the first, second, and third embodiments, the auxiliary storage device 6 uses only the update time as confirmation information for each user.
However, it is not limited to this. In this example,
The document update information and the user confirmation information are held by using the document element ID and the update time attribute of the document element. Embodiments of the present invention will be described below with reference to the drawings. In the block diagram of the present embodiment, the document display program 511 of FIG. 1 is changed to another document display program 514 and the document confirmation program 531 is changed to another document confirmation program 534 (not shown). Also, the confirmation time information 621 for each user is changed to the confirmation document element information 624 for each user.
(Not shown). In this embodiment, the document is as shown in FIG.
It is treated as structured document data that has the unique ID given to the document element and the update time information Time of the document element as attributes. User-specific confirmation document element information 624
For example, in the form as shown in FIG. 24, a set of the ID of the document element already confirmed and the update time of the document element is held for each user. In the present embodiment, the user-specific confirmation document element information 624 holds, for example, a document element ID and a set of a counter or a comment that is update information of the document element. In the flowchart of the entire system of this embodiment, the document display processing step S902 in FIG. 9 is changed to another document display processing (not shown). When the system is activated by a certain user, an event is waited for in an event loop equivalent to step S901. When the display operation is performed, the document is displayed. When an edit operation is performed, the document is changed. When the end operation is performed,
The system ends. When an editing event occurs, the same process as the flowchart of FIG. 10 is performed. The document is edited in the same process as step S1002. The document editing process is the same as that shown in FIG. The document information is edited in units of document elements in a step equivalent to step S1101. At this time, if a new document element is created by insertion or the like, the column of the ID is added to the user-specific confirmation document element information 624. In addition, since the fact that editing is performed is equivalent to the confirmation regarding the document element, the document element confirmation processing is performed according to the flowchart of FIG. 25 in the step equivalent to step S1103. The description will be given below. The update time Time set in the document element to be confirmed is calculated in step S2501.
It is also set in the column of the user-specific confirmation document element information 624 corresponding to the ID of the document element to be confirmed. At this time, if a new document element is generated by insertion or the like, the document element update (generation) time is the document element confirmation in the column of the user-specific confirmation document element information 624 corresponding to the inserted document element ID. It is set as the time. With these, the document confirmation program 534 is realized. When all editing is completed, the document element editing process is completed in a step equivalent to step S1104. The difference from Example 1 is that
In the document confirmation process of FIG. 25, the stored information is not only time information but also a set of document element ID and update time information. When a display event occurs, the same processing as the flowchart of FIG. 13 is performed. In the step equivalent to step S1302, the document element display process is performed according to the flowchart of FIG. The flowchart of FIG. 14 and the flowchart of FIG. 26 differ in the step S2602. The time of the update time attribute Time of the document element is
If it is determined in step S1402 that it is newer than the confirmation time in the column of the corresponding ID in the confirmation document element information 624 of the user who is currently performing display, it means that the update of that document element has not been confirmed yet. , Step S26
In 03, the display attribute of the document element can be changed. With the above processing, for example, the display example as shown in FIG. 16 can be realized. In this case, the document element ID, status update time attribute,
The form update time attribute is a set of update information. Step S
In the same step as 1306, by clicking the mouse as usual, pressing buttons on the screen, etc.
When the confirmation process is requested, the document confirmation process of FIG. 25 is performed in a step equivalent to step S1307. At this time, as in the second embodiment, only the update time attribute of the document element where the cursor is currently placed may be set in the user-specific document element confirmation time history information. In this case, the child element whose parent is the document element subjected to the confirmation processing needs to be separately confirmed. ID of the document element already confirmed
However, if it exists in the user-specific document element confirmation time history information, that column is considered to be overwritten. The document display program 514 is realized by these. In the user-specific confirmation document element information 624, the confirmation information of the ID that is deleted and does not exist in the current document 61 can be ignored. That is,
The current document 61 even if you checked it before it was deleted.
ID does not exist in, so user-specific confirmation document element information 624
Even if the update information remains in, it will not be used for display.
If the ID is not present in the current document 61 if the confirmation is not performed before the deletion, the update information is not registered in the user-specific confirmation document element information 624. When the document element is deleted, the column of the user-specific confirmation document element information 624 corresponding to the corresponding ID may be deleted. The document display process may be performed every time the document element is confirmed. By doing so, the confirmation information for each user is always held in the confirmation document element information for each user 624 when the user confirms the document element, and the document element confirmation time having the same ID as the document element and the document element confirmation time Update time attribute held by Tim
By comparing e, it is possible to know the unconfirmed information of each user in units of document elements. Although the present embodiment is realized by event driving, each event driven process may be performed by an independent program sharing document information. Further, in the present embodiment, the display program and the editing program are separated, but a program in which display and editing are integrated may be used as the editing program, and the display program may be omitted. According to the present embodiment, it is possible to extract and identify unconfirmed information for each user from a document in document element units. Therefore, there is an advantage that the document information that each user needs to confirm can be easily obtained. In addition, no matter how many times the entire document is displayed, unconfirmed document elements are clearly marked as unconfirmed until confirmation processing is performed. Also, by giving each document element a unique ID and managing update information for each ID,
There is an advantage that the update history information to be managed can be limited to the number of document elements existing in the past at most.

(Fifth Embodiment) In the fourth embodiment, the update time information of all the document elements is held as the confirmation information for each user, but the present invention is not limited to this. In this embodiment, the confirmation information for each user is compressed and held using the structure of the structured document, and the volume of the confirmation information to be saved is reduced. Further, when an unconfirmed part is created by the update, the information to that effect is restored to the confirmation information for each user. Embodiments of the present invention will be described below with reference to the drawings. In the block diagram of the present embodiment, the document display program 511 of FIG. 1 is another document display program 515, the document editing program 521 is another document editing program 525, the document confirmation program 531 is another document confirmation program 535, respectively. It has been changed (not shown). Further, the confirmation time information 621 for each user is changed to the confirmation document element information 625 for each user (not shown). In this embodiment, as in the case of the fourth embodiment, the document is unique I attached to the document element as shown in FIG.
It is treated as structured document data having D and the update time information Time of the document element as attributes. The user-specific confirmation document element information 625 holds a set of the ID of the already confirmed document element and the update time of the document element, like the fourth embodiment, but holds the update time for all the document elements. Not do. That is, when the structured document is regarded as a tree structure, only the confirmation information obtained by branching the confirmed elements is held (details will be described later). The flowchart of the entire system of this embodiment is the document edit processing step S903 in FIG.
Is changed to another document editing process, and the document display process step S902 is changed to another document display process.
(Not shown). When the system is activated by a certain user, an event is waited for in an event loop equivalent to step S901. When the display operation is performed, the document is displayed.
When an edit operation is performed, the document is changed. When the end operation is performed, the system ends. When an editing event occurs, the same process as the flowchart of FIG. 10 is performed. The document is edited in the same process as step S1002 of the first embodiment. The document information is edited in units of document elements in a step equivalent to step S1101. At this time, if a new document element is generated by insertion or the like, the column of the ID is displayed in the user-specific confirmation document element information 62.
Add to 5. In addition, since the fact that editing has been performed is the same as the confirmation regarding the document element, the confirmation processing is performed in a step equivalent to step S1103. The confirmation process will be described below with reference to the flowchart of FIG. If it is determined that the document element to be confirmed in step S2701 has a child element whose parent is the element, it means that the parent element has been confirmed, which means that the child element has also been confirmed, and thus step S2702.
Performs child element confirmation processing for the corresponding child element. The child element confirmation process will be described below with reference to the flowchart of FIG. If the child element to be confirmed in step S2801 has a grandchild element (child of child) whose parent is the element, it is considered that the grandchild element has also been confirmed in step S2802. The child element confirmation processing is recursively performed for. Then, step S280.
In 3, the information in the user-specific confirmation document element information 625 corresponding to the ID of the grandchild element (child of child) is deleted. The child element confirmation processing is performed as described above. At the end of the confirmation process, step 2
In the column of the table of the user-specific confirmation document element information 625 corresponding to the ID of the document element to be confirmed in 703, the time of the update time attribute Time of the document element to be confirmed is set. Through the above processing, the confirmation time information of the partial structure having the confirmed document element as a parent is branched, and the user-specific confirmation document element information 625 is stored in the auxiliary storage device 6. When all editing is completed, the document element editing process is completed in a step equivalent to step S1104. When a display event occurs, the same processing as in FIG. 13 is performed. The document element display process of the step equivalent to step S1302 is shown in FIG.
It shows according to the flow chart of. First, step S2901
Save the current display attributes. ID of the corresponding document element
Of the user-specific confirmation document element information 625, the time of the update time attribute Time of the document element in step S statement 2902 is the document element confirmation time of the confirmation document element information 625 of the user who is currently trying to display. If the document element is newer, it means that the update of the document element has not been confirmed yet, so that the display attribute of the document element is changed in step S2903.
User-specific confirmation document element information 62 of the corresponding document element ID
If there is no 5, or if the time of the update time attribute of the document element is older than the check time of the confirmation document element information 625 of the user who is currently trying to display, the document element has already been confirmed, so continue. Go to the display step. The change of the display attribute is the same as that in the first embodiment. Furthermore, since there is a possibility that a child element whose parent is an unconfirmed document element is unconfirmed, the reconstruction process of the user-specific confirmed document element information 625 (s2
904) is performed. Below, user-specific confirmation document element information 62
The reconstruction process of 5 is shown according to the flowchart of FIG. First, in step S3001, the contents of the corresponding document element are read. If the child element having the corresponding document element as a parent is included, and the update time attribute Time of the child element is newer than the document element confirmation time of the parent element in step S3002, the ID of the child element is added in step S3003. With the same column, the confirmation time column is the same as the document element confirmation time of the parent element, and the confirmation document element information for each user 625
Add to Then, regarding this contained child element,
In step S3004, the reconstruction process of the user-specific confirmation document element information 625 is recursively performed. When all the contents of the document element are read in step S3005, the user confirmation time information 62
The reconstruction process of 5 ends. Then, in step S2905,
The top of the document element is displayed according to the determined display attribute. Next, in step S2906, the content of the document element is displayed, but if it is determined in step S2907 that the content has a document element, step S2908.
The document element display processing is performed recursively with. Until the content of the document is completed, the content is displayed in step S2909. If the contents are completed in step S2910, the end of the document element is displayed in step S2910. Finally, in step S2911, the display attributes saved are restored, and the document element display processing ends.

By the above processing, as in the first embodiment,
For example, the display example shown in FIG. 16 can be realized. In a step equivalent to step S1307, confirmation processing is performed on the document element having the pointer that currently specifies the position of the cursor or the like. This confirmation processing is shown in FIG. 27 of the present embodiment,
It is the same as the confirmation process. When the document display process ends, the process returns to the event loop. Document display program by these
515 is realized. The document element display process may be performed each time the document element confirmation process is performed. By doing so, the confirmation information for each user is always held in the confirmation document element information for each user 625 when the user confirms the document element, and the update time of the update time attribute Time of the document element,
By comparing the document element confirmation times of the user-confirmed document element information 625, it is possible to know the unconfirmed information of each user in units of document elements. Although the present embodiment is realized by event driving, each event driven process may be performed by an independent program sharing document information. Further, in the present embodiment, the display program and the editing program are separated, but a program in which display and editing are integrated may be used as the editing program, and the display program may be omitted. According to the present embodiment, it is possible to extract and identify unconfirmed information for each user from a document in document element units. Therefore, there is an advantage that the document information that each user needs to confirm can be easily obtained. In addition, no matter how many times the entire document is displayed, unconfirmed document elements are clearly marked as unconfirmed until confirmation processing is performed. Further, there is an advantage that the structure of the structured document is used to compress the confirmation information for each user to be saved, and the memory to be used can be reduced.

(Sixth Embodiment) In the fifth embodiment, as shown in FIG.
Although the reconstruction process of the confirmation document element information 625 for each user is distinguished from the document element display process, it is not limited to this. In this embodiment, a case will be described in which the confirmation information for each user is reconstructed in the document element display processing.

Embodiments of the present invention will be described below with reference to the drawings.

In the block diagram of the present embodiment, the document display program 511 of FIG. 1 is changed to another document display program 516 (not shown). In this embodiment, the document is shown in FIG.
The same as Example 5 of. User confirmation document element information 625
Is the same as in Example 5. In the flowchart of the entire system of this embodiment, the document display processing step S902 in FIG. 9 is changed to another document display processing (not shown). When the system is started by a certain user, an event is waited for in an event loop equivalent to step S901. When the display operation is performed, the document is displayed. When an edit operation is performed, the document is changed. When the end operation is performed, the system ends. When an editing event occurs, it is the same as in the fifth embodiment. When a display event occurs, the same processing as in FIG. 13 is performed. Step S
A document element display process of steps equivalent to 1302 is shown according to the flowchart of FIG. First, in step S3101,
Save the current display attributes. Of the corresponding document element ID,
When there is the user-specific confirmation document element information 626, the time of the update time attribute Time of the document element in step S3102 is
If it is determined that the document element confirmation time of the confirmation document element information 625 of the user who is currently displaying is newer than the document element confirmation time, it means that the update of the document element has not been confirmed yet, so that the document element is displayed in step S3103. Attributes can be changed. If there is no user-specific confirmation document element information 625 of the corresponding document element ID, or the time of the update time attribute Time of the document element is the confirmation of the user who is currently trying to display the document element confirmation of the document element information 625. If it is older than the time, the document element has already been confirmed, and the process proceeds to the subsequent display step. The change of the display attribute is the same as that in the first embodiment. Furthermore, when a child element having the corresponding document element as a parent is included in step S3104 and it is determined that the update time attribute Time of the child element is newer than the document element confirmation time of the parent element, the ID of the child element The same column as the confirmation time column is set to be the same as the document element confirmation time of the parent element, and is added to the user-specific confirmation document element information 625 in step S3105. Then, in step S3106, the head of the document element is displayed according to the determined display attribute. Next, the content of the document element is displayed in step S3107, but if it is determined in step S3108 that there is a document element in the content, the document element display processing is recursively performed in step S3109. At this time, the unconfirmed document element is recursively subjected to the document element display processing with the same document element confirmation time as the parent element, so that the confirmation information for each user can be reconstructed. The content is displayed until the content of the document is completed. Step S3110
If it is determined that the contents are completed in step S311
1 displays the end of the document element. Finally, step S31
At 12, the document attributes display processing is finished by returning to the saved display attributes. With the above processing, as in the first embodiment, for example, the display example shown in FIG. 16 can be realized. By doing so, the confirmation information for each user is always held in the confirmation document element information 625 for each user when the user confirms the document element, and the update time of the update time attribute Time of the document element and the user who has the corresponding ID Separate confirmation document element information 62
By comparing the document element confirmation times of 5, it is possible to know the unconfirmed information of each user in units of document elements. According to the present embodiment, it is possible to extract and identify unconfirmed information for each user from a document in document element units. Therefore, there is an advantage that the document information that each user needs to confirm can be easily obtained. In addition, no matter how many times the entire document is displayed, unconfirmed document elements are clearly marked as unconfirmed until confirmation processing is performed. Further, there is an advantage that the structure of the structured document is used to compress the confirmation information for each user to be saved, and the memory to be used can be reduced. Further, since the confirmation information for each user is reconstructed together with the display, there is an advantage that the document can be displayed in batch and the document can be handled in a stream.

[0027]

According to the present invention, unconfirmed information updated after the last confirmation time can be displayed in a distinguishable manner and can be confirmed. Therefore, until the user can easily obtain the latest information to be confirmed by each user, the effect obtained in the form of a document, and the unconfirmed part, even if the corresponding document is displayed many times, the unconfirmed part Has the effect of continuing to specify. Also, when there is a document element such as mixed content in SGML, it is possible to distinguish between the child element whose parent is the element to be confirmed and the character string of the direct content of the parent element, and to confirm each. Also, the document confirmation process itself
It has the effect of being easy. Further, when an unconfirmed portion in the vicinity of a certain update is confirmed, the amount of confirmation information of that portion can be compressed using information of consecutive times. Also, by assigning a special ID to the document element and managing the update history information for each ID, the update history information to be managed can be limited to the number of document elements that existed in the past at most. Further, when the partial structure is confirmed, the amount of confirmation information of the part can be compressed using the structure information. Further, when the structure of the structured document is utilized and a partial structure is confirmed, the amount of confirmation information of the part can be compressed and the document information can be handled in a stream.

[Brief description of drawings]

FIG. 1 is a block diagram showing the configuration of a document processing apparatus according to an embodiment of the present invention.

FIG. 2 is a diagram showing an example of general structured document data.

FIG. 3 is a diagram illustrating an example of conventional document data storage.

FIG. 4 is a diagram illustrating an example of providing a document from conventional document data.

FIG. 5 is a diagram showing an example of a conventional document display.

FIG. 6 is a diagram showing a conventional display example of changed document information.

FIG. 7 is a diagram showing an example of structured document data having update time information according to the present embodiment.

FIG. 8 is a diagram illustrating an example of user-specific confirmation time information according to the present embodiment.

FIG. 9 is a flow chart showing processing in the document processing apparatus of this embodiment.

FIG. 10 is a flowchart showing a document editing process in the document processing apparatus of this embodiment.

FIG. 11 is a flowchart showing a document element editing process according to the first embodiment of this invention.

FIG. 12 is a flowchart showing a document confirmation process according to the first embodiment of this invention.

FIG. 13 is a flowchart showing a document display process according to the first embodiment of this invention.

FIG. 14 is a flowchart showing document element display processing according to the first embodiment of this invention.

FIG. 15 is a diagram showing a display example of a changed portion according to the first embodiment of this invention.

FIG. 16 is a diagram showing a document display example according to the first embodiment of this invention.

FIG. 17 is a flowchart showing a document confirmation process according to the second embodiment of the present invention.

FIG. 18 is a diagram showing an example of user-specific confirmation document element information according to the second embodiment of this invention.

FIG. 19 is a flowchart showing document element display processing according to the third embodiment of this invention.

FIG. 20 is a flowchart showing a document confirmation process according to the third embodiment of the present invention.

FIG. 21 is a flowchart showing confirmation information compression processing according to the third embodiment of this invention.

FIG. 22 is a diagram showing an example of an update time list according to the third embodiment of this invention.

FIG. 23 is a diagram showing an example of a document having an ID and update time information according to the fourth embodiment of this invention.

FIG. 24 is a diagram showing an example of document element confirmation time information for each user according to the fourth embodiment of the present invention.

FIG. 25 is a flowchart showing a document confirmation process according to the fourth embodiment of the present invention.

FIG. 26 is a flowchart showing document element display processing according to the fourth embodiment of this invention.

FIG. 27 is a flowchart showing document element confirmation processing according to the fifth embodiment of this invention.

FIG. 28 is a flowchart showing a child element confirmation process according to the fifth embodiment of the present invention.

FIG. 29 is a flowchart showing document element display processing according to the fifth embodiment of this invention.

FIG. 30 is a flowchart of a reconstruction process of user-specific confirmation document element information according to the fifth embodiment of this invention.

FIG. 31 is a flowchart showing document element display processing according to the sixth embodiment of this invention.

[Explanation of symbols]

 1 Keyboard 2 Mouse 3 CPU 4 CRT 5 Storage Device such as Memory 6 Auxiliary Storage Device such as Hard Disk 511 Document Display Program 521 Document Change Program 61 Current Document Information 621 Document Confirmation Time Information for Each User 8 Timer

─────────────────────────────────────────────────── ─── Continuation of the front page (51) Int.Cl. ⁶ Identification code Internal reference number FI technical display location 9194-5L G06F 15/419 320

Claims (18)

[Claims] 1. A holding unit for holding a plurality of pieces of document information and update time information, a storage unit for storing confirmation time information for each user of the document information held in the holding unit, and the holding unit. A reading unit that reads out the document information held by the user by identifying it, and determines whether the update time information of the document information read by the reading unit is included in the confirmation time information for each user, A document processing apparatus, comprising: a control unit that controls to display the determination result in a distinguishable manner. 2. The document processing apparatus according to claim 1, wherein the document information is handled in units of parts. 3. The document processing apparatus according to claim 1, wherein confirmation information at the time of confirming a document in partial units for each reader is held at each update time. 4. The document processing apparatus according to claim 1, wherein the confirmation information when the document is confirmed for each reader for each document element is compressed and held. 5. The document processing apparatus according to claim 1, wherein the confirmation information when the document is confirmed in units of readers for each reader is compressed and held by utilizing a continuous time range. 6. The document processing apparatus according to claim 1, wherein confirmation information, which is obtained when a document is confirmed in units of readers, is held for each document element. 7. Confirmation information for each reader is stored for each document element when the document is confirmed for each reader, and the confirmation information is compressed and stored by using the partial structure of the document. The document processing apparatus according to claim 1, wherein the document processing apparatus is a document processing apparatus. 8. The document processing apparatus according to claim 1, wherein the current confirmation status is extracted based on the confirmation information that is compressed and held. 9. When presenting the comparison result of the document confirmation information and the document update information in a distinguishable manner, the current confirmation status is extracted based on the confirmation information that is compressed and retained. The document processing apparatus according to Item 1. 10. A document processing method for reading and processing desired document information from a document file storing a plurality of document information, the confirmation of the document information stored in the document file for each user. Storing time information, reading out desired document information from the document file by specifying a user, and updating time information of the read document information is included in the confirmation time information for each user. A document processing method, comprising the steps of: deciding whether or not it is displayed, and displaying in a distinguishable manner according to the decision. 11. The document processing method according to claim 10, wherein the document information is handled in partial units. 12. The document processing method according to claim 10, wherein the confirmation information at the time of confirming the document in partial units for each reader is held for each update time. 13. The document processing method according to claim 10, wherein the confirmation information when the document is confirmed for each reader for each document element is compressed and held. 14. The document processing method according to claim 10, wherein the confirmation information when the document is confirmed in a unit of a unit for each reader is compressed and held by utilizing a continuous time range. 15. The document processing method according to claim 10, wherein the confirmation information when the document is confirmed by the reader for each partial unit is held for each document element. 16. Confirmation information for each reader is stored for each document element when the document is confirmed for each reader, and the confirmation information is stored by being compressed by using a partial structure of the document. The document processing method according to claim 10, which is characterized in that. 17. Based on the confirmation information compressed and stored,
11. The present confirmation condition is extracted, and
Document processing method described. 18. The present confirmation condition is extracted based on the confirmation information stored in a compressed manner when the comparison result of the document confirmation information and the document update information is displayed in an identifiable manner. Item 10. The document processing method according to Item 10.