JPH04286062A - Device and method for processing document - Google Patents

Abstract

PURPOSE:To confirm justness for respective document elements without designation on extraction at every document registration time and justness recognition time by previously preparing extraction information on the document elements in a document. CONSTITUTION:When there is a second document element in a noticed first document element, the content of the second document element concerned is extracted or not extracted as a part of the noticed document element based on information in extraction information 22 which is previously set from a console 1. Then, a code is generated from the extracted content and a password inputted from the console 1. Then, the code is stored in accordance with the first document element.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a document processing apparatus and method, and more particularly to a document processing apparatus and method capable of creating, editing, and storing documents.

0002

[Background Art] Conventionally, when a document file created on a computer is the subject of collaborative work by multiple users, an operating system allows the file to be shared among the multiple users. However, other users were prohibited from accessing the file.

[0003] For example, in the UNIX operating system (developed and licensed by AT&T in the United States, hereinafter the same applies), write, reference (read), and execution permissions are granted to file owners, groups, and others. can be given to users of

[0004] In such a system, a file is shared within a group (allowing not only reading but also writing), and users outside the group are not allowed to modify the file. If not, you can share the document only within the group by setting ``Allow groups to write files, but do not allow users outside the group to write files.'' can.

[0005] In addition, in a single document, each person has a scope of responsibility, and in order to prevent writing from each other, it is necessary to divide the document into separate files for each part of the document (for each management target). , was managing.

[0006]

[Problem to be Solved by the Invention] However, in the above-mentioned conventional technology, each person's area of responsibility in one document is
If writing by others was not allowed, this document could not be combined into one file. In addition, in the previously filed Japanese Patent Application No. 3-32897, the applicant has made it possible to confirm that the content is valid (has not been changed by another person), instead of preventing the content from being changed. A method is proposed in which such a plurality of document areas can be collectively combined into one file by allowing this confirmation to be performed for each document area.

However, in this method, each document area is allowed to have a nested structure, and the case where one document area contains another document area is not considered. Therefore, let us consider a system that allows the existence of other document elements within one document element. In this case, since the extraction format is different for each document element, the user must maintain and input the information for extraction for each document element to be extracted, making the work extremely complicated. There was a problem.

[0008] The present invention has been made in view of the above prior art, and by preparing extraction information regarding document elements within a document in advance, specifications related to extraction can be made each time a document is registered or verified. It is an object of the present invention to provide a document processing device and a method therefor that can confirm the validity of each document element.

[0009]

[Means for Solving the Problems] A document processing device of the present invention that solves this problem has the following configuration.

[0010] In a document processing device that handles document data composed of a plurality of document elements, attention is focused on a setting means for setting extraction conditions for the contents of each document element. When there is a second document element in the first document element, extracting means for extracting the content of the first document element based on the content set by the setting means; a password setting means for setting a password, a code generation means for generating a corresponding code based on the character string extracted by the extraction means and the password set by the password setting means; and storage means for storing the code in association with the first document element.

Further, the document processing method of the present invention includes the following steps. In other words, it is a document processing method that handles document data composed of multiple document elements, and includes a setting step in which extraction conditions are set for the content of each document element, and a step in which extraction conditions are set for the contents of each document element. 2nd document element in 1st document element
an extraction step of extracting the content of the first document element based on the content set by the setting means; and a password setting step of setting a password for the first document element. , a code generation step of generating a corresponding code based on the character string extracted in the extraction step and the password set in the password setting step, and a code generated in the code generation step to the first document element. and a storage step of storing the information in association with each other.

0012

[Operation] In this configuration and process, the conditions under which the content of each document element is to be extracted are set in advance. Then, depending on the set content, part or all of the content of the document element of interest is extracted. Then, a code is generated based on the extracted content and the set password, and is stored in association with the document element of interest.

[0013]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. [Description of Document Elements] First, "document elements" and "document element names" will be explained and defined using FIG.

The document data of the embodiment is composed of a plurality of partial documents. This partial document consists of a start symbol consisting of the symbol "<", a word, and the symbol ">", and the corresponding end symbol "</>" ((However, along with "/", the word used for the start symbol For example,
The end symbol “</a> corresponds to the start symbol “<a>”
>”). Note that “corresponding” here has the same meaning as the correspondence between parentheses in a mathematical formula. The start symbol acts as an opening parenthesis, and the end symbol acts as a closing parenthesis.

[0015] Information such as the meaning and nature of a partial document is added to the word in the start symbol. It is also possible to create a nesting structure between a start symbol and an end symbol, including a plurality of pairs of start symbols and end symbols. That is, if the start symbol appears again before the end symbol corresponding to the start symbol appears, this indicates the beginning of the second nested document element.

[0016] Here, the word in the start symbol is
The character string from the start symbol with the "document element name" to the corresponding end symbol is collectively referred to as the "document element." Furthermore, the portion between the start symbol and the corresponding end symbol is referred to as the "content of the document element." For example, the entire document data in FIG. 2 is a document element with a document element name "a", and the content of this document element is a document element with a document element name "b".
” (Hereinafter, the document element with the document element name “a” will be simply referred to as the document element “a”).

Furthermore, since the start symbol and the end symbol are delimiters for one document element, these symbols cannot be used for purposes other than delimiting document elements in the content of one document element.

Incidentally, although a document format as shown in FIG. 2 was used to explain this embodiment, the document format of the document data can form a nesting structure and distinguishable partial document data. This does not apply if the document format can be divided into

Furthermore, in the following explanation, when a document element is "valid", it means that the contents of the document element have not changed since the time when the document element was registered. In other words, even if a document element is changed, if it is restored to its original state, the document element is considered valid. Further, when a first document element includes a second document element in a nested manner, the second document element is referred to as a "child document element" with respect to the first document element. [Description of Device Configuration] FIG. 1 is a block diagram of the document processing device of this embodiment. As shown in the figure, a bus 4 includes a console 1, a CPU 2, an output device 3, and main memories 10 and 3.
0, the data memory 20 is connected. In addition, although each memory is shown separately in the illustration, these may be located on one memory. The components in each memory will be revealed in turn in the following description.

[0020] The console 1 refers to a device for inputting data to a computer (for example, a keyboard) and a device for displaying responses from the computer (for example, a CRT).
is a device that prints out or displays on a screen.

Next, the flow of processing in this embodiment will be explained. The process is broadly divided into two parts. There are two parts: a part for document creation and registration, and a part for verifying validity.

First, the flow of document creation and registration processing will be explained with reference to the flowchart shown in FIG.

First, in step S31, the document creator uses the existing editor (document editing program) from the console 1.
The document data 21 is created using, for example. The document data created here is a document composed of document elements and structured by them. An example of document data is shown in FIG.

Next, in step S32, the document creator creates extracted information data 22. This is also step S31
Similarly, this is generally done by a document creation/editing device called an editor. The extraction information data created here specifies a document element name whose entire content is to be extracted. An example of this is shown in FIG.

The illustration shows that all character strings from immediately after the start symbol to immediately before the end symbol of document elements "b" and "d" are to be extracted. At this point, the document data 21 created in step S31 and the extracted information data 22 created in step S32 are recognized as related data. For example, if the file name of the document data 21 is "report", the file name of the extracted information data 22 is "report.info".
” and associate it with the convention of the file name.

Next, in step S33, a signed document 23 for validation is created from the document data 21 and the extracted information data 22 by using the signed document data creation process for validation. This completes the document data creation (registration) process.

The details of the process of creating the signed document data for validity confirmation in step S33 will be explained in accordance with the flowchart shown in FIG.

First, in step S69, the document data 21
, extracted information data 22, document data with validation code 2
Enter the storage location (file name, etc.) for each of 3.
Determine the processing target. Next, in step S68, the user inputs the name of the document element to be justified, and this is stored as the target document element name 39. Subsequently, in step S60, the document data 21 is sequentially searched for the same document element name as the target document element name 39 from the beginning.

Next, in step S61, the document data 21
Check whether it has finished, and if it has not finished, proceed to step S
Execute 62. If the process has been completed, the document data 21 is stored in the data memory 20 as the signed document data 23 for checking validity, and the process of creating document data with signs for checking validity is ended.

Now, when the process proceeds to step S62, the extraction method determination program 14 is used to determine the target document element name 3.
9 is included in the extracted information data 22. If it is not included, "1" is stored in the extraction method determination 37, and if it is included, "2" is stored in the extraction method determination 37.

Next, in step S63, the document data 21
From there, the content of the target document element is extracted using the character string extraction program 12 based on the content of the extraction method determination 37, and this result is used as the encrypted document data 31. The character string extraction program 13 operates in the following first and second methods depending on the method of character string extraction.

The first method of processing operates when the extraction method determination 37 is "1".

For example, if there is document data as shown in FIG. 4, and only "d" is included in the extracted information data 22, when an attempt is made to extract document element "b" using the first method, as shown in FIG. The part surrounded by the broken line shown in is the extraction target.

That is, the delimiter of a child document element is subject to code generation processing, but its contents are not subject to the code generation process. Therefore, in this case, the extracted character string is as shown in FIG.

Furthermore, the second method of processing operates when the extraction method determination 37 is "2".

For example, in the case where the document data is shown in FIG. 4, if the extracted information data 22 includes "b" and "d", when an attempt is made to extract document element "b" using the second method, the data shown in FIG. The part surrounded by the broken line shown in is the extraction target.

That is, all of the child document elements including the delimiters are subject to extraction. In this case, the extracted character string is as shown in FIG.

[0038] However, when extracting the contents of a document element, character strings other than the document element name in the start symbol and character strings other than the "/" and document element name in the end symbol are not extracted, and are not extracted at all. ignore.

Returning to FIG. 6, in step S64, a process for creating and storing a validation code is performed. Here, an authentication code is created based on the character string in the encrypted document data 31 (in which the character string extracted in step S64 described above is stored), and it is stored in the document data 21. Then, this process of creating signed document data for validity confirmation is completed.

The document creation and registration process shown in FIG. 3 ends at the time when the process of creating document data with a code for verifying validity shown in FIG. 6 is completed. Incidentally, by repeating this process, it is possible to attach validity confirmation codes to a plurality of document elements.

The validity check code creation and storage process in step S64 in FIG. 6 will be explained in more detail with reference to FIG.

First, in step S110, the document creator inputs a password from the console 1 (the input password is stored in the password 32). Next, in step S111, the contents of the encrypted document data 31 (in which the character string extracted in step S64 is stored) are combined with the password input in step S110 (
The character string (connection) is encoded using the character string conversion program 19 and stored in the validity confirmation code 33. Here, it is assumed that the encrypted document data 31 and the password 32 are character strings, but they may be simply a byte string. This encoding method can be realized, for example, by an algorithm similar to the encryption of user passwords in UNIX (an operating system developed and licensed by AT&T Corporation in the United States). In other words, one character string is converted into another character string using a method that practically cannot be reversely converted. However, you must ensure that the converted string does not contain blank characters, "<", or ">".

[0043] By encoding the character code in this manner, a coded character string unique to the document can be obtained. Note that this encoding means is not limited to input/output to character strings, and may be one that can handle just a byte string.

Next, in step S112, the association program 18 is used to store the code stored in the validation code 33 at an appropriate location in the document data 21 of interest. Here, it is stored separated by a space after the document element name in the end symbol of the document element to be extracted.

FIG. 12 shows document element "a" in the first method,
An example of the document data 21 at the time when the second document element "b" has been extracted by the second method and the validation code has been created and associated is shown.

Here, the validation code is stored in the end symbol after the document element name, separated by spaces. However, if a validity check code is stored in advance, it will be replaced with a new validity check code.

[0047] With this, the process of creating and storing a code for validation is completed.

Incidentally, when the target document element name 39 is set to "b" regarding the document data in FIG. 4 and the extracted information data in FIG. become that way.

[Description of Validity Confirmation Processing] Next, a process of confirming the validity of the document data registered through the above-described process will be explained.

FIG. 14 is a flowchart for explaining the operation of this process. However, when performing this process,
The coded document data 23 for validation is already in the memory.
and extracted information data 22 are stored.

Note that step S149 is the same as step S in FIG.
69, step S148 is step S68 in FIG.
Step S140 is the same as step S60 in FIG. 6, step S141 is the same as step S61 in FIG. 6, and step S142
is step S62, and step S143 is step 63.
The step S144 is the same as the step S144 in FIG.
110 and step S145 are the same as step 111, so detailed description thereof will be omitted. However, in this process, the processing target is not the document data 21 but the document data 23 with a validity check code.

Now, when the process of step S145 is completed, the validity confirmation code 33 of the document element whose validity is to be confirmed has been created.

Next, in step S146, the contents of the validity check code created in advance and stored in the same file as the document data are compared with the contents of the validity check code 33 created in step S145. and if there is a match “
“yes”, “no” if they do not match, validity judgment 36
Store in. This process will be explained in more detail using FIG. 15.

First, in step S151, the validation code stored in the end symbol of the document element having the same document element name as the target document element name 39 is extracted from the validation code attached document data 23, and the validation code is extracted. is stored in the comparison code 35. In step S152, the comparison code 35 and the validity confirmation code 33 are compared by the character string comparison program 18, and if they match, "yes", and if they do not match, "n".
o” is stored in the validity determination 36. With the above, step S
146 comparison processing is completed.

Returning to FIG. 14. When the determination process in step S146 is completed, the process proceeds to step S147, and the validity determination 36 is output as the extraction result of this process.

[0056] Furthermore, the validity determination result may be input to a certain process. When this step S147 ends, this validity confirmation process ends. This concludes the explanation of the process for verifying validity.

[0057] Through the processing described above, by preparing information regarding the extraction method of document elements in advance, even if the document data has a nested structure, it is possible to add a validity check code to each document element. It is possible to create document data with the following information, and to confirm the validity of each document data. [Description of Second Embodiment] In the first embodiment described above, only document element names are used as extraction information. The second embodiment is characterized in that it uses information regarding the structure of document elements in document data as extraction information, and has means for associating each document element with a processing method based on this information.

FIG. 16 shows a block diagram of the document processing apparatus according to the second embodiment. The flow of processing in this apparatus is almost the same as that in the first embodiment, but the parts related to the extracted information data 23 are different.

In the second embodiment as well, the process is divided into two parts: a part for document creation/registration, and a part for verifying validity.

FIG. 17 explains the flow of document creation and registration processing.

Note that step S171 is the same as step S in FIG.
31, the document creator creates a document from the console 1 and registers it as document data 21.

Next, in step S172, extracted information data 22 is created. The extracted information created here includes:
Contains information about the structure of document elements in document data and the extraction method for each document element.

When the document data 21 is as shown in FIG. 18, an example of extracted information data created by this extracted information creation program 16 is shown in FIG.

FIG. 19 shows the structure of document elements using all the start symbols and end symbols of the document data of FIG. 18. Also, after the start symbol “1” or “2”
” means that if it is “1”, the content of the document element will be extracted using the first method, and if it is “2”, the content of the document element will be extracted using the second method. are doing.

Next, in step S173, the document data 21
From the extracted information data 22, a coded document data creation process for checking validity is performed, and a signed document 23 for checking validity is created.

[0066] The process of creating the signed document data for validity confirmation in step S173 will now be described in detail with reference to the flowchart of FIG.

First, in step S209, document data 2
1. Input the storage location (file name, etc.) of each of the extracted information data 22 and the document data with validation code 23, and determine the processing target. Next, in step S208, the user inputs the name of the document element to be justified, and this is stored as the target document element name 39. S201 is S6 in FIG.
0 and S202 are the same as S61 in FIG. 6, so a description thereof will be omitted. Next, in S203, the extraction information search and extraction program 17 is used to search the extraction information data for a start symbol with the same text element name as the target text element name 39, and to find a document element written immediately after the start symbol. The information regarding the extraction method is extracted and stored in the extraction method determination 37.

[0068] In step S204, the character string extraction program 12 is used to extract the character string of the content of the target document element from the document data 21 based on the extraction method determination 37, and the result is converted into an encrypted It is stored in the document data 31. This character string extraction program 13 is as shown in FIG. 6 of the first embodiment.
This is similar to step S63.

Next, step S206 is similar to step S64 in FIG. 6, and a code is generated based on the extracted character string and the password from the user, and it is stored in the validation code 33. When this step S206 is completed, the process of creating the coded document data for validity verification is completed.

Next, the validity confirmation process in the second embodiment will be explained according to the flowchart of FIG. However, the coded document data 23 for checking validity is stored in the memory.
and extracted information data 22 are stored.

In the illustration, step S220 is shown in FIG.
Step S209, step S221 is the same as step S208 in FIG. 20, step S211 is the same as step S201 in FIG. 20, and step S212 is the same as step S20 in FIG.
202 and step S214 are step S20 in FIG.
It is the same as 4. Further, step S216 is the same as step S110 in FIG. 11, and step S217 is the same as step S11.
Since these are the same as 1, detailed descriptions of these will be omitted.

[0072] Through the above processing, the character string for the document element of interest is extracted and the password is input, and a code generated based on these is generated in the validation code 33. It turns out.

[0073] In step S218, the corresponding validation code in the document data with validation code created in advance is compared with the content in the validation code 33 generated in step S217, and a match is made. “yes” if
”, and if they do not match, “no” is stored in the validity determination 36 (this step S218 is similar to step S1 in FIG. 14).
46). Next, proceed to step S219,
As a result of this processing, a validity determination 36 is output.

[0074] Furthermore, the validity determination result may be input to a certain process. And when this process is finished,
This validity confirmation process ends. This concludes the explanation of the process for verifying validity.

The second embodiment has the advantage that the extraction method can be freely set for each document element in a form that matches the structure of the document data. [Third
Description of Embodiments] In the first and second embodiments described above, data related to extracted information existed separately from document data.

The third embodiment is characterized in that it includes means for providing extraction information in document data and thereby associating individual document elements with processing methods.

FIG. 22 is a block diagram of the document processing apparatus according to the third embodiment. The processing flow of this embodiment is almost the same as that of the first and second embodiments described above, but the portion of the document data having extracted information is different.

First, similar to the embodiment described above, the flow of document creation/registration processing will be explained using FIG. 23.

In step S231, step S in FIG.
31, a document to be registered is inputted using the console 1, and is stored as document data 21. Next, in step S232, the document creator incorporates the extraction information into the document data 21, and creates and stores this as the extraction information attached document data 24. The extraction information is incorporated for each document element in the document data, and includes information regarding the extraction method for each document element.

[0080] Document data with extraction information 2 created here
4 is as shown in FIG. 24 when the target document data is shown in FIG. 18.

In FIG. 24, a character string “gr
oup” and “=", and “1” or “ as the attribute value
Enter the character "2". "1" means that the content of the document element is extracted using the first method, and "2" means that the content of the document element is extracted using the second method. .

Specifically, the start symbol of the document data is searched, and information regarding the selection of the extraction method for each document element is obtained by searching for the start symbol of the document data.
It is stored in the start symbol along with the attributes "group" and "=". It is also possible to use a document creation/editing device generally called an editor to directly write in the document data shown in FIG. 18 to create document data with extracted information as shown in FIG. 24.

Next, in step S233, signed document data 23 for validation is created from the document data 24 with extracted information using the signed document data creation process for validation.

[0084] Details of the process of creating the signed document data for validity confirmation in step S233 will be explained using the flowchart of FIG. In the illustration, step S
259 is the same as step S69 in FIG. 6, and step S258 is the same as step S68 in FIG. 6, so their description will be omitted. However, the difference is that instead of the document data 21, the extraction information-attached document data 24 is specified as the processing target. Next, in step S251, the extraction information search and retrieval program 45 is used to search for a start symbol having the same document element name as the target document element name 39 from the beginning of the extraction information attached document data 24, and when found, the document Information regarding the element extraction method is extracted and stored in the extraction method determination 37.

Next, in step S252, it is checked whether the document data with extraction information has been completed, and if it has not been completed, step S254 is executed. If the document data 21 has been completed, the document data 21 is converted to the document data 23 with a code for verifying validity.
Then, the process of creating signed document data for validity confirmation ends.

In step S254, the character string extraction program 13 is used to extract target document elements from the extraction information attached document data 24 based on the extraction method determination 37.
This result is stored in the encrypted document data 31. this,
The character string extraction program 13 is similar to step S63 in FIG. 6 of the first embodiment.

Next, in step S256, similar to step S64 in FIG. Store in.

[0088] When this step S256 is completed, the process of creating the signed document data for validity confirmation is completed. With this, the document creation and registration process shown in FIG. 23 is completed. Incidentally, Figure 2
When the target document element name is set to "b" using the extraction information-added document data of No. 4, the resulting document data with a code for verifying validity is as shown in FIG.

Next, the validity confirmation process will be explained according to the flowchart of FIG. Note that already in the memory, the signed document data 23 for verifying validity and the extracted information data 22 are stored in the memory.
The following explanation assumes that .

Step S280 is step S6 in FIG.
9, step S281 is step S68 in FIG.
Step S271 is the same as step S251 in FIG. 25, step S272 is the same as step S252 in FIG. 25, and step S274 is the same as step S254 in FIG. 25, so a description thereof will be omitted. However, instead of the document data 21, the coded data 23 for checking validity is designated as the processing target.

[0091] Thereafter, the process proceeds to step S276, where the document verifier is asked to input a password corresponding to the corresponding document element, and this is stored in the password 32.

[0092] In the next step S277, a code is generated from the extracted encrypted document data 31 and the input password 32, and is stored in the authenticity verification code 33.

[0093] In step S278, the validation code in the end symbol of the corresponding document element and step S2
77 and the validity check code 33 generated in step 77, and the result is sent to the validity determination 36. Similarly to the first and second embodiments, a character string such as "yes" or "no" is input to the validity determination code 36. Store.

[0094] Then, in step S279, the contents of the validity determination 36 are output.

[0095] Furthermore, the validity determination result may be input to a certain process. When this step S ends, this validity confirmation process ends. This concludes the explanation of the process for verifying validity.

In the third embodiment, the extraction method can be freely set for each document element and the validity can be confirmed.
It is possible to obtain the effect that document data and extracted information data can be stored in one file.

The present invention may be applied to a system made up of a plurality of devices, or to a device made up of one device. Furthermore, it goes without saying that the present invention can also be applied to a case where the present invention is achieved by supplying a program to a system or device.

As explained above, according to this embodiment, (
1) Since extraction information regarding document elements within a document can be prepared and used in advance, there is no need to specify extraction information each time a document is registered or verified.

(2) Based on the extracted information, determine whether the specified document element has been updated (
This has the effect of making it possible to check whether the document element is valid or not. In the above embodiment, document data is the target data for determining whether or not the data content has been changed, but program data may also be the target data. That is, the present invention can also be applied to confirming the validity of a program source.

[0100]

[Effects of the Invention] As explained above, according to the present invention, by preparing extraction information regarding document elements within a document in advance, there is no need to specify extraction information every time a document is registered or verified. , and the validity of each document element can be confirmed.

[Brief explanation of the drawing]

FIG. 1 is a block configuration diagram of a device according to a first embodiment.

[Figure 2] “Document element” and “Document element name” in the example
FIG.

FIG. 3 is a flowchart for explaining document creation/registration processing in the first embodiment.

FIG. 4 is a diagram showing an example of document data in the first embodiment.

FIG. 5 is a diagram showing an example of extracted information data in the first embodiment.

FIG. 6 is a flowchart of a process of creating document data with a code for validation in the first embodiment.

FIG. 7 is a diagram for explaining an overview of a first extraction method of the first embodiment.

FIG. 8 is a diagram showing character strings extracted by the first extraction method of the first embodiment.

FIG. 9 is a diagram for explaining an overview of the second extraction method of the first embodiment.

FIG. 10 is a diagram showing character strings extracted by the second extraction method of the first embodiment.

FIG. 11 is a flowchart of a process of creating and storing a code for validation in the first embodiment.

FIG. 12 is a diagram illustrating an example of document data on which association processing has been performed in the first embodiment.

FIG. 13 is a diagram illustrating an example of coded document data for checking validity according to the first embodiment.

FIG. 14 is a flowchart of validity confirmation processing in the first embodiment.

FIG. 15 is a flowchart of validity code comparison processing in the first embodiment.

FIG. 16 is a block diagram of a device according to a second embodiment.

FIG. 17 is a flowchart of document creation/registration processing in the second embodiment.

FIG. 18 is a diagram showing an example of document data according to the second embodiment.

FIG. 19 is a diagram showing an example of extracted information data according to the second embodiment.

FIG. 20 is a flowchart of a process of creating document data with a code for verifying validity according to the second embodiment.

FIG. 21 is a flowchart of validity confirmation processing in the second embodiment.

FIG. 22 is a block configuration diagram of a device according to a third embodiment.

FIG. 23 is a flowchart of document creation/registration processing in the third embodiment.

FIG. 24 is a diagram illustrating an example of extracted information-attached document data according to the third embodiment.

FIG. 25 is a flowchart of a process of creating document data with a code for verifying validity according to the third embodiment.

FIG. 26 is a diagram illustrating an example of coded document data for verifying validity according to the third embodiment.

FIG. 27 is a flowchart of validity confirmation processing in the third embodiment.

[Explanation of symbols]

1 Console 2 CPU 3 Output device 10, 20, 30 memory 13 String extraction program 14 Extraction method determination program 15 String comparison program 18 Mapping program 19 String conversion program 21 Document data 22 Extracted information data

Claims (2)

[Claims] Claim 1: A document processing device that handles document data composed of a plurality of document elements, comprising: a setting means for setting extraction conditions for the contents of each document element; extracting means for extracting the content of the first document element based on the content set by the setting means when there is a second document element in the first document element; a password setting means for setting a password for the password; a code generating means for generating a corresponding code based on the character string extracted by the extracting means and the password set by the password setting means; 1. A document processing apparatus, comprising: storage means for storing the code in association with the first document element. [Claim 2] A document processing method for handling document data composed of a plurality of document elements, which includes a setting step of setting extraction conditions for the contents of each document element, and a setting step of setting extraction conditions for the content of the document element. an extraction step of extracting the content of the first document element based on the content set by the setting means when there is a second document element in the first document element; a password setting step of setting a password for the password; a code generation step of generating a corresponding code based on the character string extracted in the extraction step and the password set in the password setting step; a storing step of storing the code in association with the first document element.