JPH04286060A - Device and method for processing document - Google Patents

Abstract

PURPOSE:To recognize a target document element and the justness of the whole document element by generating a code corresponding to a notice document element based on a having set password and storing the generated code in accordance with the document element concerned. CONSTITUTION:When there is a second document element in the document element corresponding to the password which is set in a password setting means, an input device 1 designates whether a character string including the second document element is extracted or a character string excluding the second document element is extracted. The character string is extracted from the notice document element based on a designated content. Then, the code corresponding to the notice document element is generated based on the extracted character string and the password which is set in the password setting means. The generated code is stored in memories 10 and 20 in accordance with the document element concerned. Thus, the target document element and the justness of the whole document element can be recognized.

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 certain 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]Also, in a single unified document, each person has a scope of responsibility, and in order to prevent writing from each other, it is necessary to divide each 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, if a certain document area contains other document areas inside, the validity of this document area can be checked to include the inner area, or to check the validity of this document area to include the inner area, or to check the validity of this document area including the inner area. , it was not possible to target the name or attribute part instead of the content. Further, it is desirable that the above-mentioned form of confirmation be performed selectively.

[0008] Therefore, let us consider a system that allows the existence of other documents within one document element. in this case,
If the validity of other document elements included in the document element of interest is also checked all at once, it is expected that the validity will be checked for each of the document elements that make up the document element of interest. Ru. However, this inevitably makes the work complicated.

[0009] The present invention has been made in view of such prior art, and when there is another document element within one document element, it is possible to confirm the validity of the target document element and the entire document element. The present invention aims to provide a document processing device and a method thereof.

0010

[Means for Solving the Problems] A processing apparatus of the present invention for solving this problem includes the following. That is, the document processing apparatus handles document data composed of a plurality of document elements, and includes a password setting means for setting a password for the document element, and a second document in the document element corresponding to the set password. If there is an element, an extracted character string specifying means for specifying whether to extract a character string including the second document element or a character string excluding the second document element, and specifying the extracted character string. an extraction means for extracting a character string from a document element of interest based on content specified by the means;
code generating means for generating a code corresponding to the document element based on the character string extracted by the extracting means and the password set by the password setting means; and storage means for storing the document elements in association with each other.

Further, the document processing method of the present invention includes the following steps. That is, this is a document processing method that handles document data composed of a plurality of document elements, which includes a password setting step of setting a password for the document element, and a second document in the document element corresponding to the set password. If there is an element, an extraction character string specification step of specifying whether to extract a character string that also includes the second document element or a character string that excludes the second document element, and specifying the extraction character string. an extraction step of extracting a character string from the document element of interest based on the content specified in the step; and a corresponding step for the document element based on the character string extracted in the extraction step and the password set by the password setting means. and a storage step for storing the code generated in the code generation step in association with a corresponding document element.

0012

[Operation] In the document processing device and method of the present invention having such a configuration and steps, when a second document element exists in the document element of interest, does the content of that document element become the target for extraction? Specify whether or not. Then, a character string is extracted according to the specified content, a code is generated together with the set password, and the code is attached to the document element of interest and stored.

[0013]

Embodiments Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

[0014] 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.

[0015] When a document element contains (nests) another document element, the inner document element is a "child document element" when viewed from the outer document element, and conversely, the outer document element is considered a "child document element" when viewed from the outer document element. From the perspective of the document, it is called the "parent document element." [Description of Apparatus Configuration] FIG. 1 is a diagram showing the configuration of a document processing system in this embodiment.

In the figure, reference numeral 1 denotes an input device, such as a keyboard, through which a user (document creator or document checker) of the system inputs documents and commands into the system. Of course, since it is also possible to input (read) documents created externally, the input device 1 includes, for example, a floppy disk in addition to the keyboard.

2 is a CPU for carrying out the processing of this embodiment based on the commands input from the input device 1; 3 is a CPU;
An output device for printing out or displaying the processing results of U2 or messages from this system, such as a printer or CRT.

10 is a first storage device for storing the processing program in this embodiment, 20 is a second storage device for storing document data handled in this embodiment, and 30
is a third storage device for temporarily storing data required for the processing of this embodiment.

The various components mentioned above are connected to the bus 4. Furthermore, although the first, second, and third storage devices do not have to be separate, since the program that can be executed by the CPU 2 is expanded to the first storage device 10, the IC
Generally, it is a RAM consisting of a chip or a ROM in which a program is written in advance. Furthermore, since the second storage device stores document data and the like, it is desired that the data be retained even after the power is cut off, so a hard disk, a floppy disk, or the like is preferable.

Now, the following programs exist in the first storage device 10. 102 is document data 2
A character string extraction program (hereinafter referred to as creation character string extraction program) is used to extract part or all of the content of a document element using the order from 01 as a guide; 103 transforms a given character string and extracts it in another way; A character string conversion program 104 is a character string conversion program for converting a character string (validity confirmation code) into a valid character string (validity confirmation code), and a character string conversion program 104 corresponds to the document element and the creation validity confirmation code 305 obtained by the character string conversion program 103 in the order as a guide. A correspondence program 105 is used to perform the mapping, a code extraction program 106 is used to extract the comparison code 311 of the document element from the document data 202 with the code for validity check, using the order as a guide; String comparison program for determining whether two strings are the same, 1
Reference numeral 07 denotes a character string extraction program (hereinafter referred to as a verification character string extraction program) for extracting part or all of the contents of document elements based on the order of the signed document data 202 for verification.

In the second storage device 20, 201 is document data made up of a plurality of document elements created by document creators, and 202 is a validity confirmation code registered by the association program 104. This is attached document data.

In the third storage device 30, the following areas are secured. Reference numeral 301 indicates a document element number (hereinafter referred to as a document element number at the time of creation) that stores information to indicate the number of the document element to be targeted at the time of document creation, and 302 indicates the character string extraction program at the time of creation 102. 303 is an area for storing the character string to be encrypted extracted from the document data 201 (hereinafter referred to as the target character string at the time of creation), and an area 303 is for storing the password input by the document creator from the input device 1 ( 304 is an area for storing encrypted data created from the creation target character string 302 and the creation password 303 (hereinafter referred to as creation-time encrypted data). 30
5 is an area for storing a creation-time validation code created from the creation-encrypted data 304 by the character string conversion program 103, and 306 is an area for storing the document element number of the target document element at the time of document verification. an area for storing a document element number for indicating (hereinafter referred to as confirmation document element number), 3
07 is an area for storing character strings extracted from the signed document data 202 for validation by the verification character string extraction program 107 (hereinafter referred to as verification target character strings);
Reference numeral 08 denotes an area (hereinafter referred to as confirmation password) for storing a password input by the document confirmer using the input device 1. Further, 309 is an area for storing encrypted data created from the verification target character string 307 and the verification password 308 (hereinafter referred to as verification encrypted data); 310
is an area (hereinafter referred to as
311 is an area for storing a comparison code for confirming the validity extracted from the document data 202 with the validation code by the validation code extraction program 105. (hereinafter referred to as comparison code). Reference numeral 312 denotes an area (hereinafter referred to as determination result) for storing the determination result of the character string comparison program 106. Further, although the details will be described later, 313 is an extraction method at the time of creation, and 314 is an extraction method at the time of confirmation.

Next, the flow of processing in this embodiment with the above configuration will be explained.

[0024] The processing is broadly divided into two parts. These are the process of creating a document and the process of confirming its validity. [Description of Document Creation Process] First, the process of registering documents created by a plurality of people will be explained using the flowchart of FIG.

First, a document creator creates a document by activating an existing editor (document editing program, not shown) and stores it as document data 201. In step S201, the storage location (file name) of the input target document data 201 and the storage location of the output target document data with validity check code 202 are input to determine the processing target.

An example of document data is shown in FIG. As shown in the figure, document data can be clearly separated into document elements using a certain document delimiter. here,
A document element is a character string that starts with "<" and ends with the corresponding ">". Therefore, the characters (symbols) "<" and ">" have special meanings, so they cannot be used in documents (document elements).
It is prohibited to use them for any purpose other than delimiting document elements (they must be represented by some other symbol).

Note that "corresponding" here has the same meaning as the correspondence between parentheses in a mathematical formula. “<” acts as an opening parenthesis, “>” acts as a closing parenthesis, “<”
” is always paired with one “>”. If “<” appears again before the corresponding “>” appears, it marks the beginning of a nested “child document element”. It represents. Here, "<" is called the "start symbol" of a document element, and ">" is called the "end symbol".

In the document shown in FIG. 3A, <AIUEO. ．． ．． ．． ．． ．． One document element that starts with <Kakikukeko. ．． ．． ．． ．． ．． Document elements that start with and <naninuneno. ．． ．． ．． ．． ．． Contains document elements starting with <Kakikukeko. ．． ．． ．． ．． ．． Document elements that start with <Sasisuseseso. ．． ．． ．． ．． Indicates that it contains document elements starting with . In this way, a document element can contain zero or more nested document elements.

[0029] In the case shown in the figure, <AIUEO. ．． ．． ．． ．． ．． For document elements starting with
<Kakikukeko. ．． ．． ．． ．． ．． Document elements that start with and <naninuneno. ．． ．． ．． ．． ．． Document elements starting with are "child document elements."

Returning to FIG. 2, in the next step S22,
The document creator inputs the number n of the document element in the document data 201 from the input device 1, and
Furthermore, the user inputs the character data extraction method used to create the validity check code for the document element. Here, when we say "nth document element", we mean nth document element counting from the beginning of the document.
Refers to the character string from the first "<" (character representing the beginning of a document element) to the corresponding ">". The input document element is stored in the creation document element number 301,
The specified character data extraction method is creation extraction method 31
Store in 3. Although the details will be described later, the method mentioned here is for specifying the range of the character string to be referenced before creating the encryption of the document element. In this example, there are two methods. exist. Therefore, to specify the method here, it is sufficient to input a number such as 1 or 2.

Next, the process advances to step S23, and by activating the creation character string extraction program, character strings are read from the corresponding document element, and the creation target character string 302 is extracted (details will be described later).

Furthermore, in step S24, the document creator inputs his/her creation password from the input device 1, and stores it as the creation password 303. and,
In the next step S25, the character string 302 to be created
A validation code is generated based on the character string in and the password in the password at creation 303, and is stored as the validation code at creation 305 (details will be described later).
.

Finally, in step S26, the correspondence program 104 is activated to perform a process of associating the corresponding document element with the creation validity confirmation code 305,
Finish the document creation process.

The process of step S23, that is, the process of the creation character string extraction program 102 will now be described.

This program performs two types of operations depending on the extraction method.

According to the first method, when an attempt is made to encrypt the second document element in FIG. 3, a document element starting with <Kakikukeko..., only the range surrounded by the broken line in FIG. 4A is targeted. do. In other words, it is characterized in that the contents of child document elements are not targeted. Therefore, the extracted character string is as shown in FIG. 4B.

According to the second method, when attempting to encrypt the second document element in FIG. 3, only the range surrounded by the line in FIG. 5A is targeted. In other words, the feature is that the entire contents of child document elements, including delimiters, are targeted. Therefore, the extracted character string is shown in Figure 5B.
become that way.

The flow of this process will be explained below with reference to the flowchart shown in FIG.

First, in step S41, a start symbol "<" of a document element to be processed is detected. next,
In step S42, the extraction method is determined by referring to the contents of the creation extraction method 313.

If the first method is used, in step S43, immediately after the start symbol of the specified document element,
The character string up to just before the corresponding end symbol is ignored when creating the target character string 30, ignoring all the contents of child document elements.
2 and exit. At this time, the content of the child document element is ignored, but its start symbol and end symbol are not ignored. This allows modification of the content of child document elements, but
This takes into consideration the case where there is a change in the placement position in the parent document element.

[0041] Furthermore, if it is the second method, step S4
In step 4, all character strings from immediately after the start symbol of the specified document element to immediately before the corresponding end symbol are stored in the creation target character string 302, and the process ends.

This concludes the explanation of the process of step S23 in FIG. 2 (character string extraction program 102 at the time of creation).

Next, the code generation process in step S25 in FIG. 2 will be explained with reference to the flowchart in FIG.

First, in step S51, the two character strings in the creation target character string 302 and the creation password 303 are concatenated and stored in the creation encrypted data 304. Note that although it is assumed here that the creation target character string 302 and the creation password 303 are character strings, they may be simple byte strings.

Next, in step S52, the data to be encrypted at the time of creation 304 is converted into another character string using the character string conversion program 103, and this is converted into another character string using the code 30 for verifying the validity at the time of creation.
Save as 5. Of course, when the encrypted data 304 is just a byte string, it goes without saying that this program (reference numeral 103) becomes a byte string conversion program.

[0046] This character string conversion program 103 can be realized by, for example, an algorithm similar to password encryption in UNIX. In other words, it converts a character string into another character string using a method that practically cannot be reversed. However, you must ensure that blank characters, "<", and ">" are not generated in the converted string.

This concludes the explanation of the code generation process in step S25 in FIG. Next, the processing of the association program 104 in step S26 in FIG. 2 will be described.

[0048] Here, the code 305 for verifying validity at the time of creation
By inserting this along with a blank character immediately before the end symbol of the target document element, the two are associated. Here, the meaning of inserting a blank character is to clearly separate the content of the document element from the validation code.

The document data into which the validation code has been inserted in this way is the document data with validation code 202.
It is.

FIG. 6 shows the coded document data 2 for checking validity.
An example of 02 is shown. In this example, the target document element is the second one (starts with <Kakikukeko...)
. “???” immediately before the end symbol of the second document element.
? ? ” is the code for verifying validity.

[0051] In the example shown in Fig. 6, an authentication code (encryption code) is inserted just before the end symbol of the second document element, and it is separated from the content of the document element by one blank character. It is being The flow of this mapping process will be explained using the flowchart of FIG. 9.

First, in step S61, the document data 201
, the end symbol “>” of the document element indicated by the document element number 301 at the time of creation is detected.

Next, in step S62, the creation validation code 305 is placed immediately before the end symbol ">" (that is,
(immediately after the target document element content) along with a blank character.

This concludes the explanation of the association process in step S26 in FIG. [Description of the validity confirmation process] Next, the flow of the validity confirmation process will be explained according to the flowchart of FIG.

First, in step S70, the storage location of the document data with validation code 202 to be processed is input, and the document data to be processed is specified. Subsequently, in step S71, the document confirmer inputs the document element number 306 at the time of confirmation and the extraction method 314 at the time of confirmation from the input device 1.

In the next step S72, the corresponding character string 307 to be verified is extracted from the coded document data 202 for verification using the verification character extraction program 107.

Next, in step S73, the document verifier inputs the verification password 308 from the input device 1.

In step S74, a verification code 310 is created from the verification target character string 307 extracted in step S72 and the verification password 308 input in step S73. This code generation process is the same process as the process in step S25 in FIG. Therefore, FIG.
In the explanation of , when checking the target character string 302 at the time of creation, the target character string 307, when checking the password 303 at the time of creation, the password 308, when checking the encrypted data 304 at the time of creation, the encrypted data 309, and the code for verifying validity at the time of creation. The same explanation can be given by replacing 305 with comparison code 310.

[0059] In step S75, the end symbol of the document element indicated by the verification document element number 306 input in step S71 is detected from the coded document data 202 for verification, and the character string immediately before this end symbol is detected. It is taken out as a comparison code 311. (This is shown in Fig. 6, step S6
This is the creation validation code inserted in step 2, and is separated from the last character of the document element content by a blank character. ) In step S76, the verification code 310 created in step S74 is compared with the comparison code 311 extracted in step S75. If they match, step S77 indicates that the character string “y” is valid.
es" is stored in the determination result 312. If they do not match,
In step S78, it is determined that the character string " is not valid."
"no" is stored. This completes the confirmation process.

Here, details of the processing of the character string extraction program 107 at the time of confirmation in step S72 in FIG. 10 are shown in FIG.
1 will be used for explanation.

Note that the processing from step S81 to step S84 is the same as the processing from step S41 to step S44 in FIG.

[0062] However, the document data 201 is the document data with a code for verifying validity 202, the document element number at the time of creation 301 is the document element number at the time of confirmation 306, the extraction method at the time of creation 313 is the extraction method at the time of confirmation 314, and the target character string at the time of creation. 302 becomes the target character string 307 at the time of confirmation.

In the case of this process, in step S85, the blank character located at the end of the character string and the following validity check code are removed from the character string stored in the verification target character string 307 in the previous process. . in particular,
It is sufficient to remove the character string from the last blank to immediately before the end symbol from the character string 307 to be checked. This concludes the explanation of the process in step S72. In addition, after storing the character string in the target character string 307 at the time of confirmation,
Instead of deleting the blank character and the validity check code following it, the corresponding character string may be deleted when storing the character string in the verification target character string 307.

This completes the explanation of the processing flow of this embodiment. [Description of Other Embodiments] The second embodiment will be described below. The second embodiment is characterized in that each document element has a name by writing an ID (name) in the document delimiter.

FIG. 12 is a diagram showing the system configuration in the second embodiment. Although the configuration of the device is the same as in FIG. 1, the programs and data stored in the first, second, and third storage devices are different.

The flow of processing in this embodiment will be explained.

Similar to the first embodiment, this process is divided into two parts: document creation process and validity confirmation process.

First, the flow of document creation processing will be explained using FIG. 13.

A document creator inputs a character string from the input device 1 and creates document data 211 using an existing editor or the like. FIG. 17 shows an example of document data 211 in the second embodiment. Document data can be clearly separated into document elements using certain symbols.

[0070] Here, the start symbol of the document element whose document element name is "a" is "<a>", and the end symbol is "</
a>”. The character string surrounded by these two symbols is the content of the document element “a”. As in the first embodiment, each document element nests zero or more other document elements. In step S101, the storage location (file name, etc.) of the document data 211 to be inputted and the storage location of the document data with validity check code 212 to be outputted are input to determine the processing target.

Next, in step S102, the document creator inputs the document element name at the time of creation using the input device 1, and further specifies the extraction method at the time of creation. These pieces of information are stored in the creation document element name 321 and the creation extraction method 313. Next, in step S103, by starting the character string extraction program 112, a character string in the corresponding document element is extracted from the document data 211 and stored in the creation target character string 302.

Next, in step S104, the document creator:
A password 303 is input from the input device 1 and stored in the creation password 303. In step S105, the creation target character string 30 extracted in step S103
2 and the creation password 30 entered in step S104.
3, a code 305 for verifying validity at the time of creation is created. This process is performed in step S2 of FIG. 2 in the first embodiment.
This is exactly the same as the process in step 5.

Finally, in step S106, the correspondence program 114 is used to perform a process of associating the corresponding document element with the creation validity confirmation code 305, and the document creation process ends.

Here, step S103 in FIG.
The processing of the character string extraction program 112 will be described.

As in the first embodiment, here too two operations are performed depending on the extraction method.

According to the first method, when attempting to encrypt document element "b" in FIG. 17, only the range surrounded by the broken line in FIG. 18A is targeted. That is, the delimiter symbols (start symbols and end symbols) of child document elements are subjected to code generation processing, but the content of the child document elements is not. Therefore, the extracted character string is as shown in FIG. 18B.

According to the second method, when document element "b" in FIG. 17 is to be encrypted, the range surrounded by the broken line in FIG. 19A is targeted. In other words, it is characterized in that the entire contents of child document elements, including delimiters, are targeted. Therefore, the extracted character string is shown in Figure 19.
It will look like B.

The character string extraction program 112 processing in step S103 will be explained according to the flowchart of FIG.

First, in step S111, the start symbol of the document element specified by the document element name 321 at the time of creation is detected from the document data 211.

Next, in step S112, the content of the creation extraction method 313 is referred to to determine the character string extraction method.

If it is determined that the first method is used, the process proceeds to step S113, and the character string from immediately after the start symbol of the target document element to immediately before the corresponding end symbol is converted into the content of the child document element. (However, the start symbol and end symbol of child document elements are not ignored) and is stored in the target character string 302 at the time of creation. At this time, if a character string other than the document element name appears in the delimiter (start symbol and end symbol) of the child document element, it may be possible to ignore this character string. If a validation code is already included in the end symbol, it is ignored.

[0082] If it is determined that the second method is used, the process advances to step S114, and all character strings from immediately after the start symbol of the target document element to immediately before the corresponding end symbol are (Contents of child document elements,
(including the delimiter) is stored in the target character string 302 at the time of creation. In this case as well, if a character string other than the document element name appears in the delimiter (start symbol and end symbol) of a child document element, it may be possible to ignore this character string. If a validation code is already included in the end symbol, it is ignored.

This concludes the explanation of the process of step S103 in FIG.

Next, the processing of the association program in step S106 in FIG. 13 will be described.

[0085] Here, the code 305 for verifying validity at the time of creation
By inserting this into the end symbol of the target document element, the two are associated. The flow of processing will be explained according to FIG. 15.

First, in step S121, the end symbol of the document element specified by the document element name 321 at the time of creation is detected from the document data 211.

Next, in step S122, a code 305 for verifying validity at the time of creation is inserted after the document element name in the detected end symbol. At this time, in order to distinguish between the document element name and the validation code, they are separated by a single blank character.

The document data created in this process is document data with a code for verifying validity, that is, document data 212 with code for verifying validity.

FIG. 20 shows an example of the coded document data 212 for verification.

In the figure, "???" among the end symbols of document element "b" is a symbol for verifying validity.

This completes the explanation of the document creation process.

Next, regarding the flow of validity confirmation processing,
This will be explained using FIG. 16.

First, in step S130, the storage location of the document data with validity check code 212 to be processed is input, and the document data to be processed is determined. Subsequently, in step S131, the document checker specifies the name of the document element to be checked and the extraction method using the input device 1. The input document element name is stored in the document element name at the time of confirmation 326, and the extraction method is stored in the extraction method at the time of confirmation 314.

[0094] In step S132, by starting the character string extraction program 112, a character string based on the specified method is extracted from the corresponding document element of the document data 212, and it is stored in the character string 307 to be checked. . This process is the same as the process in step S103 in FIG. Therefore, in FIG. 14, document data 211 is coded document data for checking validity 212, document element name at the time of creation 321 is designated as document element name at time of verification 326, and target character string at the time of creation 3.
Target character string 307 when checking 02, extraction method 313 when creating
It can be explained in exactly the same way by replacing ``with the confirmation extraction method 314''.

Returning to FIG. 16, in step S133, the document verifier inputs a password from the input device 1 (the input password is stored in the confirmation password 308).

In the next step S134, step S1
A verification code 310 is created from the verification target character string 307 extracted in step S132 and the verification password 308 input in step S133. This process is similar to the process in step S74 in FIG. 10 in the first embodiment.

[0097] Then, in step S135, the end symbol of the document element specified by the verification document element name 326 is detected from the signed document data 212 for verification, and from among the end symbols, the end symbol for comparison is detected. Take out the code 311. Finally, in step S136, step S13
The verification code 310 created in step S135 is compared with the comparison code 311 extracted in step S135. If they match, in step S137, a message indicating that they are valid (for example, a character string "yes") is stored in the determination result 312. If they do not match, a message indicating that they are not valid (for example, a character string "no") is stored in the determination result 312 in step S138. This completes the confirmation process.

In the second embodiment, although the validation code is inserted into the end symbol in the above example, it is easily possible to insert it into the start symbol. Further, although the case has been described in which the document delimiter includes only the document element name and the validity confirmation code, information such as attributes may also be included in the document delimiter. At this time, it is necessary to clearly distinguish between document element names, validation codes, and other information. For example, the second position in an end symbol, “<a
owner=me data=1990.9.11 p
asswd=? ? ? ? ? You can consider specifying the name of the attribute, such as ``>''. If you want to specify the position, insert a dummy validation code at the specified position when first creating the document data. , just replace it with the correct validation code in the matching process.

[0099] In this embodiment, the name of the document element is also
You can specify the document element whose validity you want to check.

[0100] Furthermore, since the delimiters of child document elements are also subject to encryption, the validity of the document element can be verified, including where and with what name the document element is located in the target document element. can be confirmed.

[0101] 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. It goes without saying that the present invention can also be applied to cases where the present invention is achieved by supplying a program to a system or device.

As explained above, according to the first and second embodiments, document data is divided into one or more document elements by the document delimiter, and inside this document element, there are further multiple documents. In the case where elements can be nested in many layers, if you use the first string extraction method, when extracting the string contained in a certain document element, the content of the child document element will be extracted. (without removing the start symbol and end symbol of the child document element), and create a validation code for that document element from this character string. If a name or attribute is written in a delimiter, the validity can be confirmed by including the document element name or attribute information. In other words, in this method, the validation code is created without including the content of the child document element, so even if you freely rewrite the content of the child document element, the outer (parent) document element will be “ If you delete a child document element, change its position, or change the name or attribute of a document element (if any), it will not become "legal". .

[0103] Furthermore, if the second character string extraction means is used,
When extracting a string contained in a certain document element, extract all the contents of the child document element (including the child document element's start symbol, its contents, and end symbol), and extract the text of that document element from this string. By creating a validity check code, you can check the position and content of child document elements, including information on document element names and attributes if they are written in delimiters. It is possible to confirm the authenticity of the information, and also reduce the work required to confirm the authenticity. In other words, in this method, a validation code is created from all the contents of a document element, so if the contents of a child document element are rewritten, deleted, or relocated, or if there is a document element name or attribute, Changing the document element name or attributes does not make it "legal."

[0104] In the above embodiment, the data to be determined as to whether or not the data content has been changed is document data.
The target may be program data. That is, the present invention can also be applied to confirming the validity of a program source.

[0105]

[Effects of the Invention] As explained above, according to the present invention, 1
If one document element contains another document element, it becomes possible to confirm the validity of the target document element and the entire document element.

[Brief explanation of the drawing]

FIG. 1 is a system configuration diagram in a first embodiment.

FIG. 2 is a flowchart showing a document creation processing procedure in the first embodiment.

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

FIG. 4 is a diagram for explaining a first extraction method in the first embodiment.

FIG. 5 is a diagram for explaining a second extraction method in the first embodiment.

FIG. 6 is a diagram illustrating an example of document data with a validity check code according to the first embodiment.

FIG. 7 is a flowchart showing details of the process in step S23 of FIG. 2;

FIG. 8 is a flowchart showing details of the process of step S25 in FIG. 2;

FIG. 9 is a flowchart showing details of the process of step S26 in FIG. 2;

FIG. 10 is a flowchart showing a document confirmation processing procedure in the first embodiment.

11 is a flowchart showing details of the process of step S72 in FIG. 10. FIG.

FIG. 12 is a system configuration diagram in a second embodiment.

FIG. 13 is a flowchart showing a document creation processing procedure in the second embodiment.

14 is a flowchart showing details of the process in step S103 of FIG. 13. FIG.

15 is a flowchart showing details of the process in step S106 of FIG. 13. FIG.

FIG. 16 is a flowchart showing a document confirmation processing procedure in the second embodiment.

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

FIG. 18 is a diagram for explaining a first extraction method in the second embodiment.

FIG. 19 is a diagram for explaining a second extraction method in the second embodiment.

FIG. 20 is a diagram illustrating an example of document data with a validity check code according to the second embodiment.

[Explanation of symbols]

1 Input device 2 CPU 3 Output device 4 Buses 10, 20, 30 Storage device 102 Creation string extraction program 103 Character string conversion program 104 Correspondence program 105 Validity confirmation code extraction program 106
Character string comparison program 107 Character string extraction program for confirmation 201 Document data

Claims (2)

[Claims] Claim 1: A document processing device that handles document data composed of a plurality of document elements, the apparatus comprising: a password setting means for setting a password for the document element; and a password setting means for setting a password for the document element; Extracted character string specifying means for specifying whether to extract a character string that also includes the second document element or a character string that excludes the second document element when there is a second document element; an extraction means for extracting a character string from the document element of interest based on the content specified by the character string specification means; A document processing device comprising: code generating means for generating a code corresponding to an element; and storage means for storing the code generated by the code generating means in association with a corresponding document element. 2. A document processing method that handles document data composed of a plurality of document elements, comprising: a password setting step of setting a password for the document element; and a step of setting a password in the document element corresponding to the set password. If there is a second document element, an extraction character string specifying step of specifying whether to extract a character string that also includes the second document element or a character string that excludes the second document element; an extraction step of extracting a character string from the document element of interest based on the content specified in the character string specification step; and a step of extracting a character string from the document element of interest based on the content specified in the character string specification step; A document processing method comprising: a code generation step for generating a code corresponding to an element; and a storage step for storing the code generated in the code generation step in association with a corresponding document element.