JPH04271464A - System for deciding document - Google Patents

Abstract

PURPOSE:To decide the justice of a document element by storing a code generated from the document element adding punctuation information and from a password. CONSTITUTION:The document preparer prepares the document through the use of a console 1 and stored it in document data 21 of a memory 20 as a file. Furthermore, the document preparer inputs a document element name 32 and the password 31 and keeps them in the memory 30 together with the tag and contents 33 of the document element. A ciphered character string 32 is generated from tag and contents 33 and the password 31 and is ciphered so as to generate a code 35 for confirming justice. The generated code is registered at the designated position of document data 21, is permitted to be document data 22 with the code for confirming justice and is kept in the memory 20 as the file. When the document is confirmed, the code for confirming justice 35 is newly generated concerning document data 22, is compared with the code taken out of document data 22 and is judged to be justice at the time of coincidence. Thus, it is confirmed whether the document is rewritten or not after it is prepared.

Description

[Detailed description of the invention]

0001

[Industrial Application Field] The present invention is a document processing system that creates, registers, and manages documents, and is capable of determining whether the contents of a stored document are valid as they were created. This relates to a document determination method.

0002

2. Description of the Related Art Conventionally, documents have been created on a computer and stored as files.

[0003] When this document file is the subject of collaborative work by multiple users, the operating system uses a method of sharing the file among the multiple users and prohibiting other users from accessing the file. was.

[0004] For example, in the UNIX operating system, writing, referencing (reading)
, execution permissions can be granted to file owners, collaboration groups, and other users.

[0005] In such a system, a certain file is shared within a group, and
If you want to set the file so that users outside the group are not allowed to change it, use a method that allows the group to write the file and disallows users outside the group to write the file. This allows the document to be shared only within the group.

[0006] In addition, in a single document, each person has a scope of responsibility, and if writing is not allowed for each other, each person is responsible for each part (for each management target).
However, they were divided and managed as separate files.

[0007]

[Problem to be Solved by the Invention] However, in the above conventional example, for one file, the file owner,
Permissions for writing or reading can only be granted to groups and other users.

[0008] Furthermore, by prohibiting unauthorized users from writing and reading, the validity of the document is guaranteed. This type of management could only be performed on a file-by-file basis, which caused the following problems.

1: When document files created by multiple people are part of a set of documents created jointly, the files cannot be combined into one, and the documents cannot be combined at once. I can't handle it.

2: It may be rewritten by another person, but if the data has been rewritten, the request to confirm the fact cannot be met.

3: If a file is rewritten by a super user (a user who has all rights to any file) or by a person who has permission to rewrite, the change will not be known.

[0012] In addition, in order to solve this problem, for example, the content of the document element at the time of creation and the password input by the user are encoded and stored according to a predetermined procedure, and this code and the current password are encoded and stored. It is conceivable to determine whether rewriting has occurred by comparing the contents of the document element with a code generated by a similar procedure.

However, in this method, since the code is generated from the content of the document element and the password input by the user, only the validity of the content of the document element can be determined. Therefore, even though the content of the document elements is the same, for example, when the name of the document element is changed or the attributes of each document element are changed, it is not possible to judge the validity of the document element including those changes. There is a problem.

[0014]

[Means for Solving the Problems] In order to solve the above problems, the present invention provides a document processing system that creates, edits, and stores document data consisting of a plurality of document elements separated by delimiter information. A first storage means for storing document data, an input means for inputting a password, a designation means for designating a desired document element, a document element designated by the designation means, and a separation between the document elements. code generating means for generating a code by converting the delimiter information for the document and the password input by the input means; a second storage means for storing the code in correspondence with the document element; an instruction means for instructing that a determination as to whether or not there is a content change in the document data stored in the storage means 1 is made for the document element specified by the specification means; control means for controlling the code generation means to generate a code from the password input by the input means, the document element specified by the specification means and delimiter information for delimiting the document element; Comparing means is provided for comparing the generated code and the code stored in the second storage means.

According to the present invention, a code generated and stored from a document element including delimiter information and a password is compared with a code generated from a current document element including a delimiter code and the password. This makes it possible to determine whether a document element has been changed, including delimiter information.

[0016]

[Embodiment] An embodiment of the present invention will be described with reference to the drawings. In this embodiment, when document data stored in one file is composed of a plurality of document elements, the validity of each document element is determined.

In this embodiment, "the document is valid" means that when the document is referenced, the contents of the document have not changed from when the document was registered. That is, even if a document is changed once, if it is changed back to its original state, the document is considered to be valid. The same applies to document elements.

FIG. 1 is a diagram showing the system configuration of this embodiment.

Reference numeral 1 denotes a console, which is equipped with a device (for example, a keyboard) for inputting information to the computer, and a device (for example, a CRT) that can display responses from the computer.

2 is a CPU that controls each device using the bus 4 and executes various processes according to a processing program stored in the program memory 10; 3 is a CPU that prints out or displays on a screen, etc. It is an output device.

10 is an RO that stores various processing procedures including processing procedures corresponding to the flowcharts of FIGS. 2 and 5 to 8.
A program memory consisting of M, etc., 20 is document data 2
This is a data memory such as an FD or an HD that stores documents such as 1, document data 22 with a code for verifying validity, which will be described later, in a file format. 30 is a main memory composed of RAM, etc., in which the input password 31 and document element name 32 are stored.
, tag/content 33 of a document element which is a document element including a tag as delimiter information, an encrypted character string 34 to be encrypted in code generation, an encrypted validity confirmation code 35, and a comparison code 36, judgment results 37, etc. are stored, and also has various work areas such as document editing. These memories 10, 20, and 30 do not have to be separate.

[0022] In the above and the following, unless there is a particular problem, the content of data and the area in memory for storing that data will not be distinguished by name or reference number. Next, the flow of processing in this embodiment will be explained. The processing is broadly divided into two parts: a part for creating and registering documents, and a part for confirming the validity of the contents.

Next, regarding the structure of the document data 21, FIG.
Explain using. Document data is divided into several document elements using specific delimiters. In this example, in the diagram, '<
', '>', and the string surrounded by these are delimiters.

[0024] However, '<' or ' is included in the content of the document element.
When inserting >', for example, write it as '|<' or '|>', and follow the rules such as not using strings enclosed in '|<' and '|>' as delimiters. Set it up.

Here, '<A a>' is a document delimiter symbol indicating the start of a document element, and is hereinafter referred to as a start tag. 'A' is a character string representing the name of the document element;
' is a character string representing an attribute attached to the document element whose document element name is A (hereinafter referred to as document element A). Strings 'A' and 'a' are separated by a space character ''. There may be no character string 'a', or there may be more than one character string. In that case, it shall be separated by a space character ''. On the other hand, '</A>', i.e. '</'
The document delimiter starting with is a document delimiter that indicates the end of a document element (in this case, the end of document element A), and is hereinafter referred to as an end tag. Also, the start tag and end tag will be collectively referred to as a tag. In this example,
As shown in FIG. 3, tags divide a document into multiple document elements.

FIG. 4 shows the structure of the coded document data 22 for verification in this embodiment. In this embodiment, a document element name and a validation code are inserted into the end tag. Both strings are separated by a space character ''. (Therefore, there must be no blank characters '' in the character string of the validation code. Therefore, when creating the encrypted character string 35 that is the validation code, the blank characters '' must not be included. The processing procedure of this embodiment will be described below.

[0027] This process is a process in which the document creator creates the signed document data 22 for checking validity (hereinafter referred to as creation/
This process is divided into two parts: a process in which the document referencer determines whether the document data 22 with a code for validity confirmation is valid (hereinafter referred to as a determination process).

FIG. 2 is a flowchart showing the flow of document creation/registration processing.

In the figure, S201 to S207 represent each step.

First, a document creator uses the console 1 to create document data 21 and stores it in the memory 20 as a file (S201). This is generally done by a document creation/editing device called an editor.

Next, the document creator inputs the document element name 32 of the target document element from the console 1, and stores it in the memory 3.
0 (S202). Furthermore, the document creator also enters password 31 from console 1, and
Save in the tag/content 33 of the document element in 0 (S203
). Then, the tag and contents of the document element having the input document element name 32 are extracted from the document data 21 and stored in the memory 30 (S204).

[0032] Then, an encrypted character string 34 is created from the tag/content 33 of the document element obtained in step S204 and the password 31 obtained in step S203, and is stored in the memory 30.
(S205). Then, the encrypted character string 34
is encrypted to create an authentication code 35, and the memory 3
0 (S206).

[0033] This encryption process can be realized using an algorithm similar to that used for password encryption in UNIX, for example. This converts one string into another string in a way that is practically irreversible. However, if a blank character '' appears during encryption, replace it with another code to ensure that there is no blank character '' in the generated string.

[0034] If this process only accepts character strings of a fixed length (for example, 8 bytes), and the content/tag + password of the document element exceeds this length, then the following You can create a fixed-length encrypted character string by doing something like this. First, cut the document element + password into 8-byte pieces. Next, take the exclusive OR (EX-OR) of these sequentially (take the EX-OR of the first 8 bytes and the next 8 bytes, and the result and
Ex-OR the next 8 bytes. Continue in the same manner below. ). Furthermore, if the remaining portion after the last segmentation is less than 8 bytes, it is sufficient to take measures such as inserting blanks until 8 bytes are left. In this way, a code of 8 bytes is finally obtained. Convert this to a printable character code. At this time, inappropriate codes (line feed codes, etc.) shall be converted as appropriate.

By encrypting this character code, a coded character string unique to the document element is obtained. Note that this encryption method does not limit input and output to character strings, and may be one that can handle just a byte string.

The code generated here is called a validity check code, and is stored in the main memory 30 as a validity check code 35. At this time, this validation code may be displayed on the console 1 or the like.

[0037] This completes the encryption process.

Then, the validity check code 35 created in step S206 is registered in a predetermined position of the document data 21, and the document data 22 with the validity check code is created and stored in the memory 20 as a file. (S20
7).

The process of step S205 in FIG. 2 will be explained with reference to the flowchart in FIG.

First, the start tag and the content of the document element are extracted from the tag/content 33 of the document element (S501). Then, the above two character strings and the character string of the password 31 are connected to form one character string (S502). The character string created in step S502 is stored in the third memory as the encrypted character string 34 (S503), and as shown in FIG.
The process of step S205 ends.

Further, the process of step S207 in FIG. 2 will be explained with reference to the flowchart in FIG.

First, from the document data 21, document element name 3
The end tag of document element No. 2 is detected (S601). Then, insert a blank character '' after the character string of the document element name in the end tag, followed by the validation code 35.
is inserted (S602).

The coded document data 22 for verification of validity created in step S602 is stored as a file in the second memory 20 (S603), and the process of step S207 is ended.

This concludes the explanation of the creation processing procedure in this embodiment.

Next, regarding the determination processing procedure of this embodiment,
This will be explained using the flowchart in FIG.

[0046] Before this process, the signed document data 22 for verifying validity has already been created. First, the document referencer inputs the file name of the signed document data 22 for validity confirmation from the console 1, and selects the target file. (S701).

[0047] Then, steps S202 to 2 in FIG.
06, a validity check code is obtained and stored in the validity check code 35 (S202-206).

[0048] Subsequently, the validity check code is extracted from the selected document data 22 with a validity check code and stored in the comparison code 36 (S707).

[0049] Then, the encrypted character string 35 obtained in step S706 and the comparison code 36 obtained in step S707 are compared, and if they match, 'valid' is determined.
, if there is a mismatch, 'invalid' is determined as result 3
7 and displayed on the console 1 etc. to notify the user (S708-711). This completes the determination process.

[0050] Here, the process of extracting the code for validity confirmation in step S702 described above will be described in detail using the flowchart of FIG.

First, from the document data, the document element name 32
The end tag of the document element having the document element name shown in is detected (S801).

[0052] Then, in the end tag, a blank character ''
Extract the second string separated by (S802)
. This is stored in the memory 30 as the comparison code 36 (S803). This completes the process of step S702.

This concludes the explanation of the determination processing procedure.

[0054] In this embodiment, in a system that handles document data divided into document elements by tags, an authentication code is created from the start tag and the content of the document element, so the name and attributes of the document element are included in the start tag. etc., the validity of the document element can be determined by including the name, attributes, etc. in addition to the contents of the document element. (Second Embodiment) In the above embodiment, an example has been described in which an authentication code created from a start tag, the content of a document element, and a password is inserted into an end tag. Here, an example will be described in which a validation code created from the contents of a document element, an end tag, and a password is inserted into a start tag.

The system configuration of this embodiment is similar to that of the first embodiment shown in FIG.

FIG. 9 shows the structure of the coded document data for verifying validity. That is, the attributes of the document element are written in the end tag, and the validation code is inserted in the start tag, separated by the document element name and a blank character ''.

The creation processing procedure in this embodiment follows the flowchart of FIG. 2 in the first embodiment. however,
Since the processes in steps S205 and S207 are different from those in the first embodiment, these two processes will be explained here.

First, the process of creating an encrypted character string in step S205 will be explained using the flowchart shown in FIG.

First, the end tag and the content of the document element are extracted from the tag/content 33 of the document element (S1001).
. Then, connect the above two character strings and the character string of password 31 to make one character string (S1002)
.

The character string created in step S1002 is stored in the memory 30 as the encrypted character string 34 (
S1003), the process of step S205 in FIG. 2 ends.

Next, the registration process of the validity confirmation code in step S207 will be explained using the flowchart of FIG.

First, from the document data 21, document element name 3
Detect the start tag of document element 2 (S1101)
. Then, a blank character '' is inserted after the character string of the document element name in the start tag, followed by the validity confirmation code 35 (S1102).

The coded document data 22 for verification of validity created in step S1102 is stored as a file in the memory 20 (S1103), and the document data 22 with a code for verifying validity created in step S1102 is stored as a file in the memory 20 (S1103).
The process of 07 ends.

This concludes the explanation of the creation processing procedure of this embodiment.

Next, the determination processing in this embodiment will be explained.

The processing procedure follows the flowchart of FIG. 7 in the first embodiment. However, the process of creating the encrypted character string in step S205 follows FIG. Step S7
The processing for extracting the comparison code of 02 will be explained using FIG.

First, the start tag of the document element having the document element name shown in the document element name 32 is detected (S120
1).

[0068] Then, the blank character '' in the start tag
Extract the second character string separated by (S120
2). This is stored in the third memory as the comparison code 36 (S1203), and the process of step S702 in FIG. 7 is ended.

[0069] In this embodiment, in a system that handles document data divided into document elements by tags, an authentication code is created from the contents of the end tag and the document element, so the name, attributes, etc. of the document element are included in the end tag. When inserted, the validity of the document element can be determined by including the name, attributes, etc. in addition to the contents of the document element. (Third Embodiment) In this embodiment, processing is performed to determine the validity of document elements including start tags and end tags.

The system configuration diagram of this embodiment is shown in FIG. 1 of the first embodiment.

The structure of the document data 21 at this time is shown in FIG. That is, in this embodiment, the attributes of a document element are described in the second and subsequent blank characters in the start tag and the third and subsequent blank characters in the end tag. A dummy character string that will later become a validation code is written in the second end tag. The dummy character string must be a character string that can be clearly distinguished from the validation code. For example, use a character string that starts with a character that cannot be generated when encrypted.

FIG. 14 shows the structure of the coded document data 22 for verification.

[0073] Instead of the dummy characters, a validation code is written in the end tag. The creation processing procedure in this embodiment follows the flowchart of FIG. 2 in the first embodiment. However, steps S205 and S207
Since the processing is different from the first embodiment, the two processing will be explained here.

First, step S205 in this embodiment
The process of creating an encrypted character string will be explained using the flowchart of FIG. 15.

First, the content of the document element and the part excluding the second character string (dummy character string) of the start tag and end tag are extracted from the tag/content 33 of the document element (S1
501). Then, the above two strings and password 3
1 strings to make one string (S
1502).

An encrypted character string is created from the character string obtained in step S1502, and the created character string is stored in the memory 30 as the encrypted character string 34 (S1503).
, the process of step S205 in FIG. 2 ends.

Next, step S207 in this embodiment
The registration process of the validity check code will be explained using the flowchart of FIG. 16.

First, from the document data 21, document element name 3
Detect the end tag of document element 2 (S1601)
.

Then, the second character string (dummy character string) in the end tag is deleted (S1602). As described above, the dummy character string can be clearly distinguished as a dummy character string or an authentication code by making it a character string that starts with a character that cannot be generated when encrypted.

[0080] Then, a blank character '' is inserted after the character string of the document element name in the end tag, followed by the validity confirmation code 35 (S1603).

[0081] The coded document data 22 for verification of validity created in step S1603 is stored as a file in the memory 20 (S1604), and the document data 22 with the code for validity confirmation created in step S1603 is stored as a file in the memory 20 (S1604).
The process of 07 ends.

This concludes the explanation of the creation processing procedure of this embodiment.

Next, the determination processing in this embodiment will be explained.

The procedure of this process follows the flowchart of FIG. 7 in the first embodiment. However, step S205
The process of creating the encrypted character string follows the process shown in FIG. 10 in the second embodiment. Further, the comparison code extraction process in step S702 follows FIG. 12 in the second embodiment.

This concludes the explanation of the determination processing procedure in this embodiment.

[0086] In this embodiment, in a system that handles document data divided into document elements by tags, an authentication code is created from the contents of the start tag, end tag, and document element. When the name, attributes, etc. of a document element are inserted, the validity of the document element can be determined by including the name, attributes, etc. in addition to the content of the document element.

[0087] At this time, if the encrypted character string is created including the validity check code included in the start tag or end tag, the comparison results will always be inconsistent, making it impossible to make a determination at the time of reference. In this embodiment, the above problem is solved by creating an encrypted character string excluding the authenticity confirmation code part.

[0088] Furthermore, in the above three embodiments, '<'
The character string surrounded by '>' and '>' is used as the document delimiter, but the delimiter is not limited to these. For example, as shown in FIG. 17, the delimiter may be a character string from the character string '****' or '********' to a carriage return or a new line. In FIG. 17, the start tag is a line in which the character string '***' is followed by the document element name, followed by the attribute. The end tag begins with the character string '＊＊＊＊＊', followed by the document element name, followed by a validation code. In short, it is sufficient that the content of the document element and the delimiter part are described so as to be clearly distinguishable.

Furthermore, in the three embodiments described above, document elements are identified using the document element name, but it is also possible to specify, for example, the number of the document element. At this time, there is no character string for the document element name in the tag.

In addition, in the third embodiment, an example was described in which both the start tag and the end tag clearly exist, but in a system that does not allow nesting of document elements, either tag may be omitted. This embodiment can be applied even when For example, as shown in Figure 18, if the end tag is omitted, the end tag is the start tag or EOF (End of
This is considered to be a null string (a virtual string consisting of 0 characters) in front of File). In other words, the content of a document element is a character string surrounded by the start tag of the document element and the next start tag or EOF.
The end tag is a null string,
The third embodiment may be applied.

[0091] In the above embodiment, the target data for determining whether or not the data content has been changed is document data.
The target may be program data.

Furthermore, the present invention may be realized by a device made up of a single device, or by a system made up of a plurality of devices. Furthermore, it goes without saying that the present invention is also applicable to cases where functions are achieved by supplying programs to devices or systems.

[0093]

[Effects of the Invention] As explained above, according to the present invention,
This has the effect that it is possible to check whether the contents of a document file have been rewritten.

As explained above, according to the present invention, for document data that is divided into several document elements using delimiter information, it is determined for each document element whether or not the document element has been changed. It is possible to check the document element including its delimiter information, so if the delimiter information describes the name or attributes of a document element, you can check not only the contents of the document element but also the validity of the document element including its name, attributes, etc. gender can be determined.

[Brief explanation of the drawing]

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

FIG. 2 is a flowchart of document creation/registration processing in the first embodiment.

FIG. 3 is a diagram showing an example of document data.

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

FIG. 5 is a flowchart of encrypted character string creation processing in the first embodiment.

FIG. 6 is a flowchart of validation code registration processing in the first embodiment.

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

FIG. 8 is a flowchart of comparison code extraction processing in the first embodiment.

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

FIG. 10 is a flowchart of encrypted character string creation processing according to the second embodiment.

FIG. 11 is a flowchart of validation code registration processing in the second embodiment.

FIG. 12 is a flowchart of comparison code extraction processing in the second embodiment.

FIG. 13 is a diagram showing an example of document data according to the third embodiment.

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

FIG. 15 is a flowchart of encrypted character string creation processing according to the third embodiment.

FIG. 16 is a flowchart of validation code registration processing according to the third embodiment.

FIG. 17 is a diagram showing still another example of coded document data for checking validity.

FIG. 18 is a diagram showing still another example of coded document data for checking validity.

[Explanation of symbols]

1 Console 2 CPU 3 Output device 4 Computer bus 10 Main memory 20 Data memory 21 Document data 22 Coded document data for checking validity 30 Program memory 31 Password 32 Document element name 33 Document element tag/content 34 Encrypted characters Column 35 Validity confirmation code 36 Comparison code 37 Judgment result

Claims (6)

[Claims] Claim 1: A document processing system for creating, editing, and storing document data consisting of a plurality of document elements separated by delimiter information, comprising: a first storage means for storing document data; an input means for inputting a code, a designation means for designating a desired document element, a document element designated by the designation means, delimiter information for delimiting the document element, and a password input by the input means; code generation means for converting the code to generate a code; second storage means for storing the code in correspondence with the document element; an instruction means for instructing that the presence/absence determination be made for the document element specified by the specifying means; a password input by the input means in response to an instruction from the instruction means; and a password specified by the specifying means. control means for controlling the code generation means to generate a code from the generated document elements and delimiter information for delimiting the document elements; 1. A document determination method characterized by comprising a comparison means for comparing a document with a code. 2. The document determination method according to claim 1, wherein the codes are stored in the second storage means in a distinguishable manner as part of delimiter information for delimiting corresponding document elements. 3. The delimiter information includes document element start information and document element end information, and the code generation means uses the document element start information as delimiter information for code generation. The document determination method described in 1. 4. The delimiter information includes document element start information and document element end information, and the code generation means uses the document element end information as delimiter information for code generation. The document determination method described in 1. 5. The delimiter information includes document element start information and document element end information, and the code generation means uses the document element start information and document element end information as delimiter information for code generation. The document determination method according to claim 1, characterized in that: 6. The document determination method according to claim 2, wherein the code generation means excludes a code included in the delimiter information as delimiter information for code generation.