JP2958141B2 - Document processing apparatus and method - Google Patents

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.

[0002]

2. Description of the Related Art Conventionally, when a document file created or created on a computer is to be collaborated by a plurality of users, the file is shared among the plurality of users by an operating system. However, other users were prohibited from accessing the file.

[0003] For example, the UNIX operating system (developed and licensed by AT & T, USA).
In the following, the permission for writing, referencing (reading), and execution for each file can be given to the owner, group, and other users of the file.

In such a system, a certain file is shared within the group (not only reading but also writing is possible), and a user outside the group is allowed to change the file. If you do not want to share the document only within the group, you can specify that the file is allowed to be written to the group and the file is not allowed to be written to users outside the group. it can.

[0005] Further, in a single set of documents, there is a range of responsibilities, and in order to prevent writing to each other, each file is divided into separate files for each part in charge (for each management target). , Had managed.

[0006]

However, according to the above-mentioned conventional technology, each of the responsible areas in one document has
Without allowing others to write, this document could not be combined into a single file. In addition, the applicant of the present application, in the Japanese Patent Application No. 3-32897 filed earlier, can confirm that the contents are legitimate (not changed by others) instead of preventing the contents from being changed, A method is proposed in which this confirmation can be performed for each document area, and such a plurality of document areas are collectively collected into one file.

However, in this method, a nesting (nesting) structure is permitted for each document area, and no consideration is given to a case where a certain document area includes another document area inside. Therefore, consider a system that allows the existence of another document in one document element. In this case, if the validity of other document elements included in the noted document element is checked collectively, the validity of each document element constituting the noted document element will be confirmed. Is expected. However, this inevitably complicates the work.

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and not only can simply verify whether or not illegal rewriting has occurred in stored document data, but also can store partial data constituting the document data. In each case, if there is a nested second partial data in the partial data (first partial data), it is assumed that the nested second partial data is included according to the set management level. Another object of the present invention is to provide a document processing apparatus and method capable of confirming the validity of the first partial data while switching between the first and second cases.

[0009]

In order to solve this problem, a document processing apparatus according to the present invention has the following arrangement. In other words, the storage device includes storage means for storing the document data in a predetermined document data storage means and reading means for reading the document data from the document data storage means, and a plurality of partial data separated by delimiters has a nested structure. A document processing apparatus for processing a document to be obtained, comprising: a management target partial data designating unit for designating one partial data to be registered as a management target in the document data; and setting management information for the designated partial data; A management information setting registration unit for registering the document data in association with the document data; and the storage unit stores, in the document data to be stored in the document data storage unit, the partial data designated by the management target partial data designation unit as a first data. First password input means for inputting a password to the first partial data as partial data; When the nested second partial data exists in the data, the second partial data is not at the same management level as the first partial data according to the management information registered by the management information setting / registering means. The second
Is extracted as data corresponding to the first partial data, and when it is determined that the data is at the same management level, the first partial data including the second partial data is extracted as the first partial data. First extracting means for extracting as data corresponding to data, a combination of data corresponding to the first partial data extracted by the first extracting means and a password input by the first password inputting means A first code generating means for generating code data according to a predetermined conversion algorithm, and embedding the code data generated for the first partial data in a delimiter for separating the first partial data. An embedding unit; and a storage unit for storing the document data in which the code data is embedded in the document data storage unit, wherein the reading unit stores the document data. Read document data designating means for designating document data to be read from the storage means, and validity confirmation partial data for designating partial data to be validated in the document data designated by the read document data designating means Specifying means, second partial password input means for setting the specified partial data as first partial data, and inputting a password corresponding to the first partial data, and nesting expression for the first partial data of interest. When there is the second partial data, if the second partial data is not at the same management level as the first partial data according to the management information registered by the management information setting / registering means, Data other than the second partial data is extracted as data corresponding to the first partial data, and if it is determined that the data is at the same management level, the second partial data is included. Second extracting means for extracting the first partial data as data corresponding to the first partial data, data corresponding to the first partial data extracted by the second extracting means, and the second password Second code generation means for generating code data in accordance with a predetermined conversion algorithm for a combination with the password input by the input means; code data generated by the second code generation means; Comparing means for comparing code data embedded in a delimiter symbol corresponding to the partial data designated by the partial data designating means; and said second extracting means based on a comparison result of the comparing means with respect to the partial data. Output means for outputting information as to whether or not the partial data extracted in step (1) has been changed.

The document processing method of the present invention includes the following steps. That is, in a document processing apparatus that processes a document in which a plurality of partial data delimited by a delimiter can have a nested structure, a storage step of storing document data in a predetermined document data storage unit in the document processing apparatus; A document processing method comprising: a reading step of reading document data from the document data storage means; a management target partial data specifying step of specifying one piece of partial data to be registered as a management target in the document data; A management information setting registration step of setting management information for the partial data and registering the management information in association with the document data; and the storing step includes specifying the management target partial data in the document data to be stored in the document data storage means. The first partial data is a partial data designated in the process, and a password is input to the first partial data. A password input step, and when the nested second partial data exists in the first partial data of interest, the second partial data is stored in accordance with the management information registered in the management information setting registration step. If it is not at the same management level as the first partial data, data other than the second partial data is extracted as data corresponding to the first partial data, and if it is determined that it is at the same management level, A first extraction step of extracting first partial data including the second partial data as data corresponding to the first partial data; and a first extraction step of extracting the first partial data extracted in the first extraction step. A first code generation step of generating code data in accordance with a predetermined conversion algorithm for a combination of corresponding data and a password input in the first password input step; An embedding step of embedding the generated code data in a delimiter separating the partial data; and a storing step of storing document data in which the code data is embedded in the document data storage means. A read document data designating step for designating document data to be read from the data storage means, and a validity confirmation part for designating partial data to be validated in the document data designated in the read document data designation step A data designating step, a second password inputting step of using the designated partial data as first partial data and inputting a password corresponding to the first partial data, and nesting the first partial data of interest. When the second partial data of the formula exists, the second partial data is stored in accordance with the management information registered in the management information setting registration step. Is not at the same management level as the first partial data, data other than the second partial data is extracted as data corresponding to the first partial data, and it is determined that the data is at the same management level. A second extracting step of extracting first partial data including the second partial data as data corresponding to the first partial data; and a first extracting step of extracting the first partial data in the second extracting step. A second code generation step of generating code data according to a predetermined conversion algorithm for a combination of the data corresponding to the data and the password input in the second password input step; A comparator for comparing the generated code data with the code data embedded in the delimiter corresponding to the partial data specified in the validity confirmation partial data specifying step. If, and an output step of changing the partial data extracted by said second extraction means outputs the information about whether or not made based on the comparison result for the partial data of said comparing step.

[0011]

In the configuration or process of the present invention, management information is set for designated partial data in document data, and registered in association with the document data. Then, in the case of saving, a password corresponding to the designated partial data in the document data to be stored in the document data storage means is input. Then, when the nested second partial data exists in the focused first partial data, the second partial data is set to the same management level as the first partial data according to the registered management information. If not, the second
Is extracted as data corresponding to the first partial data, and when it is determined that the data is at the same management level, the first partial data including the second partial data is extracted as the first partial data. Is extracted as data corresponding to. Then, code data is generated for a combination of the extracted partial data and the password input by the first password input unit according to a predetermined conversion algorithm. Then, the generated code data is embedded in the delimiter for separating the extracted first partial data, and the document data in which the code data is embedded is stored in the document data storage unit. On the other hand, in the case of reading, the document data constituting the document data to be read and the partial data whose validity is to be confirmed are specified. Then, a password for the specified partial data is input. And
Encoded data corresponding to the partial data of interest is generated in the same manner as when saving. Then, the generated code data is compared with the code data embedded in the delimiter of the partial data of interest in the document data to be read, and the partial data extracted based on the comparison result is compared. Outputs information on whether changes have been made.

[0012]

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

In the following description, a document element being "valid" means that the content of the document element has not changed from the time when the document element was registered. That is, once changed, if it is restored, the document element is regarded as valid.

When the first document element includes (nests) the second document element, the second document element is viewed from the first document element as a “child document element”. Is referred to as a “parent document element” when viewed from the second document. [Explanation of Apparatus Configuration] FIG. 1 is a diagram showing a configuration of a document processing system in the present embodiment.

In FIG. 1, reference numeral 1 denotes an input device for a user (a document creator or a document confirmer) of the present system to input a document or a command to the present system, for example, a keyboard.
Of course, in order to be able to input (read) a document created outside, the input device 1 includes, for example, a floppy disk in addition to a keyboard.

Reference numeral 2 denotes a CPU for performing the processing of this embodiment based on a command input from the input device 1;
An output device for printing out or displaying the processing result of U2 or a message from the present system, for example, a printer or a CRT.

Reference numeral 10 denotes a first storage device for storing a processing program according to the present embodiment, 20 denotes a second storage device for storing document data handled in the present embodiment, 30
Is a third storage device for temporarily storing data required for the processing of this embodiment.

The various components described above are connected to the bus 4. Although the first, second, and third storage devices do not have to be separated, a program that can be executed by the CPU 2 is loaded in the first storage device 10.
Generally, it is a RAM composed of a chip or a ROM in which a program is written in advance.
Further, since the second storage device stores document data and the like, it is desirable to retain the data even after the power is turned off. Therefore, a hard disk, a floppy disk, or the like is desired.

The first storage device 10 has the following programs. 102 is the document data 2
A character string extraction program for extracting part or all of the contents of a document element based on document element identification information such as a document element name from 01, and 103 converts a given character string into another character string ( A character string conversion program 104 for converting the character string into a document element and a validity confirmation code 305 obtained at the time of creation obtained by the character string conversion program 103 based on the document element name and the like. 105 is a document data 2
02, a code extraction program for validity check to extract the reference code 311 for the document element based on the document element name or the like from 02, and a character string comparison program 106 for determining whether two character strings are the same. It is.

In the second storage device 20, reference numeral 201 denotes document data composed of a plurality of document elements created by the document creators, and reference numeral 202 denotes a validity confirmation code in which a validity confirmation code is registered by the association program 104. The attached document data 203 is management data.

In the third storage device 30, the following areas are secured. Reference numeral 321 denotes a document element name storing information to indicate a target document element at the time of document creation (hereinafter, referred to as creation document element name), and 302 is extracted from the document data 201 by the creation string extraction program 102. An area for storing a character string to be encrypted (hereinafter referred to as a creation target character string), and an area 303 for storing a password input by the document creator from the input device 1 (hereinafter referred to as a creation password). ) And 304 are areas for storing the encrypted data created from the creation target character string 302 and the creation password 303 (hereinafter referred to as creation-time encrypted data). 305 is an area for storing a creation validity confirmation code created from the creation time encrypted data 304 by the character string conversion program 103, 326.
Is an area for storing a document element name for indicating a target document element at the time of document confirmation (hereinafter, referred to as a document element name at the time of confirmation), and 307 is a character string extraction program 102 from the signed document data 202 for validity confirmation. An area for storing the extracted character string (hereinafter referred to as a confirmation target character string),
An area 308 stores a password input by the document checker from the input device 1 (hereinafter, referred to as a password for checking). Reference numeral 309 denotes an area for storing the encrypted data created from the confirmation target character string 307 and the confirmation password 308 (hereinafter, referred to as confirmation encrypted data), and 31.
0 is an area for storing a code created from the encrypted data 309 at the time of confirmation by the character string conversion program 103 (hereinafter referred to as a code for validity confirmation at the time of confirmation), and 311 is valid by the code extraction program 105 for validity confirmation. This is an area (hereinafter, referred to as a comparison code) for storing a comparison code for confirming the validity extracted from the document data 202 with the character confirmation code. 312 is a character string comparison program 10
Area for storing the judgment result of No. 6 (hereinafter referred to as judgment result)
It is.

Next, a description will be given of the processing flow of this embodiment in the above configuration.

The processing is roughly divided into two. This is a process for creating a document and a process for checking validity. [Explanation of Document Creation Process] First, a process of registering a document created by a plurality of persons will be described with reference to the flowchart of FIG.

First, a document creator creates a document from the input device 1 by activating an existing editor (document editing program (not shown)) and stores it as document data 201.

FIG. 3 shows an example of the document data. As shown, the document data can be clearly separated for each document element by a specific document delimiter. here,
The document element with the document element name “a” is a start symbol “<a>”
And ends with a corresponding end symbol “</a>”. In other words, the character string surrounded by these two symbols is the content of the document element "a" (in the case of the figure, the character string "Aieo ..."). Therefore, the start and end symbols have special meanings,
Use of these in a document (document element) for purposes other than delimiting the document element is prohibited (substituted with some other symbol). The correspondence between the start symbol and the end symbol is the same as the correspondence between the parentheses in the mathematical formula, and the start symbol is always paired with one end symbol.

Each document element can include 0 or more nested other document elements.

In the case shown, the document element "a" includes the document elements "b" and "e". As described above, the document elements “b” and “e” are “child document elements” with respect to the document element “a”, and the document element “a” is conversely the document elements “b” and “e”. "" Is the parent document element.

After the document is created, the document creator assigns a code to the document element in the document data 201 to manage the document element. As a code to manage,
Here, the author name of the document element is temporarily set.

This need not be attached to every document element. Unsigned document elements will be subject to the same controls as their parent document elements (here the same author). As shown in FIG. 6, a file is prepared in which the correspondence between document elements and authors is assigned in a table format as shown in FIG. This is the management data 20
3.

In FIG. 6, the author of the document element “a” is “suzu
ki ", which indicates that the document element" b "is" sato ", and has no information about the document element" c "or the document element f which is not described here. Will be.

Since this file (management data 203) is associated with the document data 201 (because there is a possibility that a plurality of document data exist, not limited to the document data 201), the file has the same name as the document data 201 and has a unique name. Extension is added. For example, as a name of a file (management data 203) corresponding to a document element and a code for document data “file”, “file.
dat "etc. However, this file may be any file as long as the relationship between the document element and the code (author name in the embodiment) for managing the document element can be understood. No, preparation is complete, step S in FIG.
In 21, the storage locations (for example, file names) of the document data 201, the signed document data 202 for validity confirmation, and the management data 203 are input, and a document processing target is determined. In the next step S23, which document element is to be registered is designated by the input device 1, and this is designated as the creation-time document element name 32.
1 is stored. The document element specified here must be given a management code.

Next, in step S24, by activating the character string extraction program 102, a character string is read out from the corresponding document element, and the character string 302 is created at the time of creation.
To be stored. In step S25, the document creator inputs the password for the document element of interest to the input device 1
Enter more. The input password is stored in the creation password 303. Then, in step S26, the creation target character string 3 extracted in step S24
An encrypted code is generated from the character string in 02 and the password stored in the creation password 303 in step S25, and stored in the creation validity confirmation code 305 (details will be described later).

Finally, in step S27, by activating the associating program 104, an associating process is performed between the corresponding document element and the obtained validity confirmation code, and the document creating process is completed.

Here, the processing of step S24, that is, the processing of the character string extraction program 102 will be described.

This program has a document element name 32 at the time of creation.
The contents of the document element specified by 1 (excluding the start and end symbols of the specified document element) are extracted, but if there is another nested document element in it, the following processing is performed. Perform

First, when a management code is assigned to a nested document element (which can be determined by referring to the management data 203), the document element (nested document element = child document) It does not extract the contents of element). However, the start and end symbols of the document element are extracted. If a management code is not assigned to the nested document element, not only the start and end symbols but also the contents of the document element are extracted.

For example, when the document data shown in FIG. 3 and the management data shown in FIG. 6 are created, when the character string extraction program is executed for the document element "a", the character string shown in FIG. Is extracted.

When the same processing is performed for the document element "b", the character string shown in FIG. 4B is extracted.

The processing flow of the character string extraction program will be described below with reference to the flowchart of FIG.

First, in step S51, the pointer jumps immediately after the start symbol of the document element specified by the document element name 321 at the time of creation. Then, the next step S
In step 52, when the next document delimiter is detected by sequentially advancing the pointer, the character string up to that point is extracted. Then, in the next step S53, it is determined whether or not the previously detected document delimiter is the end symbol of the target document element (parent document element). The determination criterion can be determined based on whether or not the focused document element name exists in the delimiter and whether it is an end symbol. The judgment here is "YE
In the case of "S", all the character strings to be extracted have been extracted, so this processing ends. In the case of "NO" (that is, the detected document delimiter is the delimiter of the "child document element"). If so, the process proceeds to step S54.

Here, (step S54), it is determined whether or not a management code is attached to the document element corresponding to the detected document delimiter. When the document element name of this document element is registered in the management data 203, it is considered that a management code is attached. In the case of the end symbol, it is assumed that the management code is not attached. If not, the subsequent character strings including the delimiter are also character strings to be extracted, and the process returns to step S52. (After that, the process proceeds to the hierarchy below the nest one after another until the start symbol of the document element registered in the management data or the end symbol of the designated document element is found.)

When it is determined that the management code is attached, if the document element is described structurally correctly, the detected delimiter is not the end symbol but the start symbol of the child document element. You can think there is.

Moreover, since the "child document element" is provided with a management code, the character string immediately before the corresponding end symbol is a character string not to be extracted. Therefore, the pointer is advanced to the end symbol, and the process of extracting the character string therefrom is continued.

At this time, if the start symbol or the end symbol includes anything other than the document element name (for example,
At the time of validity confirmation to be described later, a validity confirmation code is inserted in the end symbol), and this is ignored (not extracted).

By the above processing, the target character string 3 at the time of creation
02, a character string is extracted and stored.

Next, the code generation processing in step S26 in FIG. 2 will be described with reference to the flowchart in FIG.

First, in step S61, the target character string 302 at the time of creation and the two character strings in the password 303 at the time of creation are concatenated and stored in the encrypted data 304 at the time of creation.
Here, the creation target character string 302 and the creation password 303 are assumed to be character strings, but may be simple byte strings.

Next, in step S62, by activating the character string conversion program 103, the character string in the encrypted data at the time of creation 304 is converted into another character string, which is converted into a validity confirmation code 305 at the time of creation. Store. Of course, when the encrypted data at the time of creation 304 is a simple byte string, it goes without saying that this program (reference numeral 103) is a byte string conversion program.

The character string conversion program 103 can be realized by, for example, an algorithm similar to the password encryption in UNIX. In other words, a certain character string is converted into another character by a method that cannot be virtually inverted. However, a document delimiter must not be generated in the converted character string.

Next, step S27 in FIG. 2, that is, the operation of the association program 104 will be described.

Here, the validity confirmation code 305 at the time of creation is used.
Is inserted into the end symbol of the target document element with a space character. Since the validity of the target document element is confirmed by the validity confirmation code, the purpose of inserting a blank character here is to clearly separate the document element name from the validity confirmation code. Things.

The document data into which the validity confirmation code is inserted is the document data 202 with the validity confirmation code.
become.

FIG. 5 shows the signed document data 2 for validity confirmation.
02 is shown. The character string "????" in the end symbol of the document element (here, a, b, d, e) for which the management code is designated is the validity check code. A validity confirmation code is inserted in the end symbol of each document element, and it can be seen that the document element name is separated from the document element name by one blank character.

The processing of this processing (association program 104) will be described with reference to the flowchart of FIG.

First, in step S71, 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 S72, a validity confirmation code 305 is inserted together with a blank character immediately after the document element name in the end symbol.

As described above, the processing in step S27 in FIG. 2 can be achieved. [Explanation of Validity Confirmation Process] Next, the flow of the validity confirmation process will be described with reference to the flowchart of FIG.

First, in step S80, the respective storage locations of the signed document data 202 for validity confirmation and the management data 203 are input, and the processing target is determined. Subsequently, in step S81, the document confirmer inputs a document element name to be confirmed from the input device 1. The input document element name is stored in the confirmation document element name 326.

In the next step S72, the character extraction program 10 is extracted from the signed document data 202 for validity confirmation.
2, the corresponding character string is extracted and stored in the confirmation target character string 307. This processing is basically the same as the processing at the time of document creation, that is, the same as that of FIG. However,
The processing target is the document element stored in the document element name 326 at the time of confirmation, and the storage destination of the extracted character string is the character string 307 at the time of confirmation.

Next, in step S83, the document confirmer inputs the confirmation password 308 from the input device 1.

In step S84, a confirmation validity confirmation code 310 is created from the confirmation target character string 307 extracted in step S72 and the confirmation password 308 input in step S83. This encryption is the same processing as the processing in step S26 in FIG. In other words, the creation target character string 302 in the description of FIG.
07, creation password 303, confirmation password 30
8. The same description can be made in exactly the same way, except that the encrypted data at creation 304 is replaced with the encrypted data at confirmation 309 and the creation validity confirmation code 305 is replaced with the validation validity confirmation code 310.

In step S85, the end symbol of the document element indicated by the document element number 306 at the time of confirmation input in step S71 is detected from the document data 202 with the code for validity confirmation, and the document element name in the end symbol is detected. The character string that does not include a blank character immediately after is extracted as a comparison code 311 (this character string is a validity check code inserted in the processing of FIG. 9 and is separated from the document element name in the end symbol by a blank character. Has been).

In step S86, the validity confirmation code 310 for confirmation created in step S84 and step S8
The comparison code 311 extracted in step 5 is compared. If they match, the validity is stored in step S87, for example, a character string "yes" is stored in the determination result 312. If they do not match, it is determined in step S88 that they are not valid, for example, a character string "no" is stored.

With the above, the description of the processing flow of the first embodiment has been completed. [Description of Another Embodiment] The second embodiment will be described below. In the second embodiment, the management code is described not in a separate file but in a document delimiter.

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

The processing flow of the second embodiment will be described below.

As in the first embodiment, this process is also divided into a process for creating a document and a process for checking validity.

First, the flow of the document creation processing will be described.

First, the document creator inputs a character string from the input device 1 and uses the existing editor or the like to input the document data 2.
At this time, the management code is also described in the document delimiter (start symbol).

FIG. 13 shows an example of the document data 211 in the second embodiment. Document data can be clearly separated for each document element by a specific symbol.

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 0 or more other document elements. Can be included.

When the management code is described in the delimiter, for example, "author
= Suzuki ”is inserted after the document element name with a space character between them.

As in the first embodiment, the author name of the document element is used as the management code. This indicates that the document element is suzuki. Also, as in the first embodiment, for all document elements,
There is no need to describe the management code. In other words, those with no description receive the same management as the parent document element (assuming the same author).

This will be described with reference to FIG. Step S10
In step 1, the storage locations (for example, file names) of the document data 211 and the document data 212 with validity confirmation code are input, and the processing target is determined. Processing is step S1
In step 02, the document creator inputs the document element name at the time of creation from the input device 1.

Next, in step S103, the character string of the corresponding document element is extracted by activating the character string extraction program 112, and stored in the creation target character string 302. In step S104, the creator of the document
Then, a password corresponding to the corresponding document element is input (the input password is stored in the creation password 303).

In step S105, step S103
Then, an encrypted code is created from the character string extracted in step (stored in the target character string 302 at the time of creation) and the password input in step S104 (stored in the password 303 at the time of creation). It is stored in the validity confirmation code 305 at the time of creation. This process is exactly the same as the process of step S26 in FIG. 2 in the first embodiment.

Finally, in step S106, the corresponding document element and the encryption code
05 is performed, and the document creation processing ends.

Here, step S103 in FIG.
The processing of the character string extraction program 112 is almost the same as that of the character string extraction program 102 in the first embodiment, and the contents of the processing are the same as those in FIG.

However, in the first embodiment, the correspondence between the document element and the management code is a separate file.
In the second embodiment, it is directly described as a delimiter in the document data. Therefore, to determine whether or not the management code is attached, the character string “author
Check if there is == ”.

In this case, if a character string other than the document element name is included in the delimiter (start symbol and end symbol) of the child document element, this character string is ignored. That is,
When extracting character strings, "author = su" in each start symbol
Do not extract character strings such as "zuki". (Do not also extract blank characters that deviate document element names and their management information.)

The document data shown in FIG. 13 shows the document data obtained by combining the document data shown in FIG. 3 and the management data shown in FIG. 6, and, like the first embodiment, the document element “a” FIG. 4A shows a character string obtained when the character string is extracted for the same as in the first embodiment. Also,
A character string obtained when the same processing is performed on the document element “b” is as shown in FIG. 4B.

Next, the validity confirmation processing, which is the second processing in the second embodiment, will be described with reference to FIG.

First, in step S120, the storage location of the signed document data 212 for validity confirmation is input, and the processing target is determined. Subsequently, in step S121, the document confirmer inputs the document element name of the document element to be confirmed from the input device 1 (the entered document element name is stored in the confirmation document element name 326). Next, step S1
In step 22, the character string extraction program 112 is started to extract a character string from the corresponding document element in the validity-confirmed signed document data 212, and extract it as a confirmation target character string 307.

In step S123, the document confirmer inputs the password for the corresponding document element from the input device 1 (the entered password is the password 30 for confirmation).
8). Next, in step S124, the character string extracted in step S122 (the confirmation target character string 3
07) and the password entered in step S123 (stored in the confirmation password 308) to generate a confirmation validity confirmation code 310. In this process, the same process as in step S84 in FIG. 10 in the first embodiment may be executed.

When the confirmation validity confirmation code 310 is generated, the process proceeds to step S125, in which the corresponding document element in the validity confirmation signed document data 212 (stored in the confirmation document element name 326). Then, the end symbol of the document element having the specified document element name) is detected, and the comparison code 311 is extracted from the end symbol.

Finally, in step S126, step S
The comparison code 310 generated in step 124 and step S1
25 and is compared with the validity check code 311 extracted. As a result, if they match, it is determined in step S127 that the file is valid (for example, the character string “yes”).
12 and if they do not match, step S128
Then, the fact that the message is not valid (for example, the character string “no”) is stored in the determination result 312. This is the end of the confirmation processing.

In this embodiment, the validity check code is inserted into the end symbol, but it is of course possible to insert it into the start symbol. Also, an example has been described in which only the document element name, the management code, and the validity confirmation code exist in the document delimiter, but information such as attributes may be present in the document delimiter.

In this case, the document element name and the validity confirmation code must be clearly distinguishable from other information.
For example, to determine the position in the end symbol,
As in the present embodiment, it is conceivable that the name of the attribute is specified as <a owner=me date=1990.9.11 passwd=?????>.
When specifying the position, a dummy validity confirmation code may be inserted at a predetermined position when document data is first created, and may be replaced with a correct validity confirmation code in the association process. As described above, according to the first and second embodiments, one piece of document data is divided into one or more document elements by a document delimiter, and the number of layers of further document elements inside the document element. I. It is possible to manage the validity of each document element of a certain group for document elements of any nest hierarchy. ii. The task for i. Is simplified because all document elements do not have to have a management code. iii. Document elements for which management is not specified can receive the same management as the parent document element.

The above effect is obtained.

Even when it is determined that the child document element is not under the control of the parent document element, even the delimiter of the child document element is to be encrypted. It is possible to confirm the validity of the document element, including the position of the document element in what position. In other words, in this case, even if the contents of the child document element are freely rewritten, the outer (parent) document element is regarded as "valid", and the child document element is deleted or the position is changed. If there is a document element name or attribute, and if the document element name or attribute is changed, it is not "valid".

In the above embodiment, the data for which the data content is to be changed is document data.
The program data may be targeted. That is, the present invention can also be applied to confirm the validity of a program source.

[0092]

As described above, according to the present invention,
When reading out the document data, it can be verified for each of a plurality of partial data constituting the document data whether the document data once stored in the document data storage means has been illegally rewritten. You can know. Moreover, when another partial data (second partial data) is nested in the partial data (first partial data),
If the first and second partial data have the same management level based on the registered management information, the validity of the first partial data including the second partial data can be determined. At the management level, the second partial data can know the validity of the first partial data while allowing at least a third party to make corrections. As a result, it becomes possible to perform an appropriate action according to each of the stored partial data constituting the document, and further, according to the nesting.

[Brief description of the drawings]

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

FIG. 2 is a flowchart illustrating a document creation processing procedure according to the first embodiment.

FIG. 3 is a diagram illustrating an example of document data according to the first embodiment.

FIG. 4 is a diagram for explaining a character string extraction process in the first embodiment.

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

FIG. 6 is a diagram showing contents of management data in the embodiment.

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

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

FIG. 9 is a flowchart illustrating details of a process in step S27 of FIG. 2;

FIG. 10 is a flowchart illustrating a document confirmation processing procedure according to the first embodiment.

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

FIG. 12 is a flowchart illustrating a document creation processing procedure according to the second embodiment.

FIG. 13 is a diagram illustrating an example of document data according to the second embodiment.

FIG. 14 is a flowchart illustrating a document confirmation processing procedure according to the second embodiment.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Input device 2 CPU 3 Output device 10, 20, 30 Storage device 102 Character string extraction program 103 Character string conversion program 104 Correspondence program 105 Code extraction program for validity confirmation 106 Character string comparison program 201 Document data 202 Validity confirmation Signed document data 203 Management data

Continuation of the front page (72) Inventor Masaaki Nagashima 3-30-2 Shimomaruko, Ota-ku, Tokyo Canon Inc. (72) Inventor Tadashi 3-30-2, Shimomaruko 3-chome, Ota-ku, Tokyo Inside Canon Inc. (56) References JP-A-3-278161 (JP, A) JP-A-3-8076 (JP, A) JP-A-2-297284 (JP, A) JP-A-2-28869 (JP, A) JP-A-2-14355 (JP, A) JP-A-1-243172 (JP, A) JP-A-1-161937 (JP, A) JP-A-1-101042 (JP, A) JP-A-63-269251 (JP JP, A) JP-A-60-118954 (JP, A) JP-A-60-26387 (JP, A) Information Processing Society of Japan, Proceedings of the 42nd (late 1991) National Convention (3) ( (March 12-14, 1991), p. 308 to 309 (58) Fields investigated (Int. Cl. ⁶ , DB name) G06F 17/21 G06F 17/22 G06F 17/24 G06F 9/06 G09C 1/00-5/00 JICST file (JOIS)

Claims (8)

(57) [Claims] A storage means for storing document data in a predetermined document data storage means; and a reading means for reading the document data from the document data storage means, wherein a plurality of partial data delimited by a delimiter are nested. A document processing apparatus for processing a document that may have a structure, comprising: a management target partial data designating unit that designates one partial data to be registered as a management target in the document data; and management information for the designated partial data. Management information setting registration means for setting and registering the document data in association with the document data; andthe storage means, in the document data to be stored in the document data storage means,
A first password input unit for inputting a password for the first partial data with the partial data designated by the management target partial data designating unit as a first partial data; When the nested second partial data exists in the data, the second partial data is not at the same management level as the first partial data according to the management information registered by the management information setting / registering means. In
Data other than the second partial data is extracted as data corresponding to the first partial data, and if it is determined that the data is at the same management level, the first partial data including the second partial data is extracted from the second partial data. First extracting means for extracting data corresponding to the first partial data, data corresponding to the first partial data extracted by the first extracting means, and a password input by the first password inputting means A first code generating means for generating code data in accordance with a predetermined conversion algorithm for the combination of the first and second partial data; and a code generated for the first partial data in a delimiter separating the first partial data. An embedding unit for embedding data; and a storage unit for storing document data in which code data is embedded in the document data storage unit. Read document data designating means for designating document data to be read from the document data storage means, and validity confirmation for designating partial data to be validated in the document data designated by the read document data designating means Partial data designating means; second partial password inputting means for setting the designated partial data as first partial data and inputting a password corresponding to the first partial data; When the nested second partial data is present, if the second partial data is not at the same management level as the first partial data according to the management information registered by the management information setting registration means, ,
Data other than the second partial data is extracted as data corresponding to the first partial data, and if it is determined that the data is at the same management level, the first partial data including the second partial data is extracted from the second partial data. Second extracting means for extracting data corresponding to the first partial data, data corresponding to the first partial data extracted by the second extracting means, and a password input by the second password inputting means A second code generation means for generating code data according to a predetermined conversion algorithm for the combination of: and code data generated by the second code generation means;
Comparing means for comparing code data embedded in a delimiter symbol corresponding to the partial data designated by the validity confirmation partial data designating means; and A document output device that outputs information as to whether or not the partial data extracted by the second extraction unit has been changed. 2. The document processing apparatus according to claim 1, wherein the password input by the first and second password input means is information unique to a user. 3. The management information setting / registering means sets, for each partial data, user information for managing or creating each partial data, and stores the first partial data of interest and the first partial data in If the user information of the nested second partial data matches, the first and second
The extracting means extracts the data including the second partial data as the data of the first partial data, and extracts the data not including the second partial data as the first partial data if they do not match. The document processing apparatus according to claim 1, wherein 4. When there is no user information for the nested second partial data, the second partial data has the same management level as the first partial data, and the second partial data and the second 4. The method according to claim 3, wherein when different user information is set for the first partial data, the first partial data and the second partial data are processed as not having the same management level. Document processing device as described. 5. A document processing apparatus for processing a document in which a plurality of partial data delimited by a delimiter can have a nested structure, stores the document data in a predetermined document data storage means in the document processing apparatus. A document processing method comprising: a storage step; and a reading step of reading document data from the document data storage means, wherein a management target partial data specifying step of specifying one piece of partial data to be registered as a management target in the document data; A management information setting registration step of setting management information for the designated partial data and registering the information in association with the document data; andthe storing step includes:
A first password inputting step in which the partial data specified in the management target partial data specifying step is set as first partial data, and a password is input to the first partial data; When the nested second partial data exists in the data, the second partial data is not at the same management level as the first partial data according to the management information registered in the management information setting registration step. In
Data other than the second partial data is extracted as data corresponding to the first partial data, and if it is determined that the data is at the same management level, the first partial data including the second partial data is extracted from the second partial data. A first extraction step of extracting data corresponding to the first partial data; data corresponding to the first partial data extracted in the first extraction step; and a password input in the first password input step A first code generation step of generating code data in accordance with a predetermined conversion algorithm for the combination of the first and second partial data; an embedding step of embedding the generated code data in a delimiter separating the first partial data; Storing the document data in which the embedded document data is stored in the document data storage unit. The reading step includes reading the document data from the document data storage unit. A read document data designating step for designating document data to be specified; a validity confirmation partial data designating step for designating partial data to be validated in the document data designated in the read document data designating step; A second password input step of inputting a password corresponding to the first partial data using the obtained partial data as a first partial data, and a nested second part in the first partial data of interest. When the data exists, according to the management information registered in the management information setting registration step, if the second partial data is not at the same management level as the first partial data,
Data other than the second partial data is extracted as data corresponding to the first partial data, and if it is determined that the data is at the same management level, the first partial data including the second partial data is extracted from the second partial data. A second extraction step of extracting data corresponding to the first partial data, data corresponding to the first partial data extracted in the second extraction step, and a password input in the second password input step A second code generation step of generating code data according to a predetermined conversion algorithm for the combination of the above, and code data generated by the second code generation step;
A comparing step of comparing code data embedded in a delimiter symbol corresponding to the partial data specified in the validity confirmation partial data specifying step; and An output step of outputting information as to whether or not the partial data extracted by the second extracting means has been changed. 6. The document processing method according to claim 5, wherein the password input in the first and second password input steps is information unique to a user. 7. The management information setting / registering step sets, for each partial data, user information for managing or creating each of the partial data, and assigns the first partial data of interest and the first partial data to each other. If the user information of the nested second partial data matches, the first and second
Extracting the data including the second partial data as the data of the first partial data, and extracting the data not including the second partial data as the first partial data if they do not match. 6. The document processing method according to claim 5, wherein: 8. When there is no user information for the nested second partial data, the second partial data has the same management level as the first partial data, and the second partial data and the second partial data have the same management level. 8. The method according to claim 7, wherein when user information different from the first partial data is set, the first partial data and the second partial data are processed as not having the same management level. Document processing method described.