JP3624649B2 - Structured information file inspection device and computer-readable recording medium - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to an apparatus for supporting creation of a structured document (hypertext) used in WWW (World Wide Web) or the like.
[0002]
[Prior art]
An HTML document (Hyper Text Markup Language), which is a structured document used on the WWW, stores not only individual information but also link information to other documents. If there is link information, a message to that effect is displayed, so that the operator can easily access related information by simply clicking on the displayed portion with a mouse or the like. In the case of a WWW HTML document, the link information includes an identifier of a processing apparatus (WWW server) in which a file of the corresponding other document is arranged, a file storage position, and a file name.
[0003]
Using the features of the structured document, each structured document is created and stored in the WWW server so that the operator (WWW browser) can obtain each person's desired information in easy-to-see units. .
Furthermore, desired information is displayed by answering a question so that each person's desired information can be easily acquired. However, it is not easy to create an HTML document that realizes this, and an invention that makes this easy has been filed as Japanese Patent Application No. 8-234160 “Intelligent Search Program Creation System”.
[0004]
[Problems to be solved by the invention]
However, even if a system for creating a structured document as described above is used, the work associated with other structured documents must be performed manually. The associating operation is to set link information to the corresponding document, but there is often a case where the corresponding document has not yet been created. In that case, for the time being, only the link information is set, and the corresponding document will be created later. There is a problem in that the creation of the entire structured document is delayed due to reasons such as storing the created document or using a different file name.
[0005]
An object of the present invention is to provide a document that assists in creating a structured document more efficiently.
[0006]
[Means for Solving the Problems]
FIG. 1 is a principle diagram of the present invention. 1A and 1B are WWW servers, and 2 is a WWW client. 6A and 6B are structured information files which are arranged on the WWW server and referred to by the WWW client via the Internet 7.
3 is a determination means for determining whether or not the corresponding information file exists based on the link information from the information file to the other information file, and 4 is the link information for which the corresponding information file does not exist and the relevant information file. It is an output means for outputting the identification information of the information file having a link in an identifiable form. Reference numeral 5 denotes a generation unit that generates a file having a corresponding file name at a corresponding location based on link information when there is no corresponding information file.
[0007]
DETAILED DESCRIPTION OF THE INVENTION
As described above, the present invention refers to link information from an individual file to another file such as an HTML document, and checks whether there is a corresponding file. In the following description, the structure described in Japanese Patent Application No. 8-234160 “Intelligent Search Program Creation System” is mainly described. An explanation will be given for the information file.
[0008]
In the “intelligent search program creation system”, the answers to the questions (Q1 to Q6) (entered with 0 or 1) and corresponding to them in the table format as shown in FIG. 4 (see the table of 11 to 13) By inputting the output (R1 to R6) or the additional questions (K2 to K3), a document referred to by a WWW browser (WWW client) and a related program are generated.
[0009]
FIG. 4 is a diagram showing related files in the intelligent search program creation system described above. In the intelligent search program creation system, the knowledge table shown in FIG. 4 is generated by inputting the relationship between the question, the answer, and the output (including additional questions) from the input screen similar to the knowledge table shown in FIG. Based on the generated knowledge table, a file (HTML document) that is actually referred to from the WWW browser is created.
[0010]
In the generated HTML document (referred to as a knowledge information file in the specification), the operator displays a question on the WWW browser, selects and inputs an answer to the question, and based on the result of the selection and input A program (script) for determining an HTML document to be received next (conclusion information files R1 to R6 or knowledge information files K2 to K3) is stored.
[0011]
The above input will be described using the knowledge table K3 (13) in FIG.
If the answer corresponding to the question sentence Q6 is 1 when the answer is YES and 0 when the answer is NO, in the example of this figure, when the answer of the question sentence Q6 is input from the browser of YES and WWW, R6 ( An HTML document (referred to as a knowledge information file) including a program (script) that causes the WWW browser to receive an HTML file called a conclusion information file and receive the conclusion information file R5 when NO is input. Generated based on the table.
[0012]
In the knowledge table K3, only the conclusion information file is received after the answer to the question is input by the WWW browser. However, as in the knowledge tables K1 (11) and K2 (12), the additional question file ( The reception of the knowledge information file) can also be specified.
In the knowledge table K1 (11), in addition to the three conclusion information files R1 to R3, K2 is designated as a file to be received. K2 corresponds to the knowledge table K2 (12) in the figure below. That is, when answering NO to question Q1, NO to question Q2, and YES to question 3, the additional question Q4 or Q5 specified in the knowledge table K2 is displayed on the WWW browser.
[0013]
If the question is in the knowledge table K2, Q4 is NO, and Q5 is YES, the HTML document corresponding to the knowledge table K3 is further received by the WWW browser, and the question (Q6) specified in the knowledge table K3 is received. ) Is displayed on the WWW browser.
In the following description, a mechanism for checking the relationship between the knowledge information files (K1 to K3) and the conclusion information file based on the link information and generating a necessary file (knowledge information file or conclusion information file) will be described.
[0014]
First, the operation of the present invention will be described with reference to FIG. FIG. 2 is a diagram showing a processing flow of the present invention.
First, the range of inspection of link information or the start point of inspection is obtained (step 100). By default, the inspection range is within the own computer, but if the operator designates, the inspection is performed within the range. For example, the operator designates only a specific folder in the own computer as a search range, or sets a resource or file that can be shared on the network other than the own computer as a search range.
[0015]
In addition, for the starting point of the inspection, the default is a knowledge table (or knowledge information file) with the specified name on the area specified by the intelligent search system, but if specified by the operator, it is specified. The following processing is performed using the selected file as the starting point of inspection.
It is determined whether or not it is in a mode for inspecting at startup (step 110). If the mode is to perform the inspection process, the link information is inspected sequentially from the start point. This detailed processing will be described with reference to the link structure processing flow of FIG.
[0016]
The link structure inspection process called in step 120 is the same as the same process started in step 300 of this flow. However, in step 300, a file may be automatically generated, but in step 120, a file is not automatically generated only by inspection.
Next, the entire link structure is displayed (step 130). At this time, the link structure is displayed as shown in FIG. 7 in accordance with the display work table of FIG. 6 generated in the previous step 120. The identification information is displayed for each information file in a line in the order stored in the display work table. At that time, indent processing is performed based on the numerical value in the “hierarchy level” column to display each information file. Do.
[0017]
In addition, each attribute can be identified based on the “Type” column indicating the type of information file, the “Existence” column indicating whether the file exists, or the “Generation” column indicating whether the file is automatically generated. In such a form, it is displayed as shown in FIG.
That is, regarding the type of information file, the intelligent information file is displayed as an octagon, and the conclusion information file is displayed as a rectangle. When the file is automatically generated, this display is performed with a double line. If the file does not exist, it is displayed with a dotted line.
[0018]
FIG. 8 shows a display example different from FIG. This display is displayed in association with the physical storage of each information file. In the first hierarchy, a component folder, a conclusion folder, and a knowledge folder are displayed. These three folders are physical storage units, and parts such as image data used in the conclusion information file are stored in the parts folder. A conclusion information file is stored in the conclusion folder. Similarly, a knowledge information file is stored in the knowledge folder.
[0019]
What corresponds to the hierarchical display in FIG. 7 is below each knowledge folder. Each knowledge folder is arranged based on link information between knowledge information files, and a knowledge information file (for example, k1.html) and a knowledge table (for example, k1.sheet) are stored in each knowledge folder. . The link information (each linked information file) of each information file is displayed with a dotted line. In this display, each information file is displayed in the “type” column indicating the type of the information file stored in the knowledge conclusion management table of FIG. Based on the “generation” column indicating whether or not it has been generated, display is performed in a form in which each attribute can be identified, as in FIG.
[0020]
If the inspection mode is not set in step 110, the entire link structure is displayed using the display work table generated in the previous check process. Further, when the check process has never been performed, the link structure is not displayed.
Next, when the editing process is designated (step 140), the editing process is called (step 200). As a method of starting editing processing of an existing information file, a mouse is compared with a method of starting editing processing and then specifying a file name to be edited, and displaying the entire link structure displayed in the previous step 130. There are two ways to start the editing process for the file clicked in step 1.
[0021]
In the above description, the link structure of the information file is displayed. However, there is a mode in which only uncreated or automatically generated information is displayed as a list.
For this display, a list of related files is displayed based on the “existence” column and the “generation” column of the knowledge conclusion management table of FIG. In other words, only the information files that are “None” in the “Existence” column are extracted and displayed in a list, or only the information files that are “Generated” in the “Generation” column are displayed. Extract and display a list.
[0022]
This display is particularly effective during the editing process, and the operator performs an editing process by selecting from this list.
If the link structure check process is designated (step 150), the link structure inspection process under the start point is called (step 300), as in step 120. In this case, the difference from the processing in step 120 is that an actual file is generated for the link information that does not yet exist.
[0023]
The link structure inspection process is also called after the editing process (step 200) is completed.
If the information file is automatically generated after the link structure inspection process is completed (step 160), the inspection process is started again (step 120).
Until the end is designated (step 170), the display of the link structure, the designation of the editing process, and the designation of the designation of the link structure process are performed.
[0024]
Next, the link structure check process will be described in detail with reference to the flowchart of FIG. 3 and the knowledge conclusion management table of FIG.
The knowledge conclusion management table 30 shown in FIG. 5 is generated when the knowledge tables K1 to K3 of FIG. 4 are created. Each record of the knowledge conclusion management table 30 corresponds to the conclusion (R1 to R6) and the knowledge (K1 to K3) of the knowledge tables K1 to K3 in FIG. This table includes identification information (ID), name, URL or FILE name of each information file, information file type indicating whether each information file is a knowledge information file or a conclusion information file, automatic A generation mode indicating whether to perform generation, “inside / outside” indicating whether each file exists on the local computer or an external computer, and whether the file exists. “Existence” indicating the check result and “Generation” indicating whether it is automatically generated or not.
[0025]
In step 310 of FIG. 3, it is checked whether or not the file specified at the start of the check process is within the inspection target range. For example, when only a specific folder is specified as the inspection range, it is determined whether or not the specified file is in the specific folder. If the specified file is not in the specific folder, This check process ends.
[0026]
Note that this determination (step 310) is not performed when this check processing is started without specifying a file.
Next, it is determined whether this process has been started by designating a file (step 320). If no file is specified, the default file name of this system is set as the specified file (step 321).
[0027]
Then, it is determined whether or not the designated file actually exists (step 330). If the designated file exists in a computer other than the own computer, it is determined that the file does not exist if the file cannot be obtained by requesting the HTTP protocol.
If the file does not exist and the inspection process is not specified (step 331), the file is generated (step 400). Automatic file generation will be described with reference to FIG.
[0028]
First, it is determined whether the file to be generated is in the local computer (step 410). If it is in the own computer, it is next determined whether the information file to be generated is a conclusion information file or a knowledge information file (step 420).
If the information file to be generated is a conclusion information file, the name of the conclusion information file (“name” field in FIG. 5) is extracted and incorporated in the generation pattern of the conclusion file (step 430). FIG. 10 shows a state in which a name is incorporated in the generation pattern. That is, a character string “about western food” is extracted from the “name” column of FIG. 5 and the character string is stored between “<TITLE>” and “</ TITLE>” of the generation pattern.
[0029]
When the generation target is the knowledge information file, the character string of the name is extracted in the same manner, and the character string is stored in the corresponding portion of the corresponding generation pattern (step 440).
If the generation target is not within the own computer, it is determined whether or not there is an authority to generate the file on the computer where the file should be (step 450). Automatic generation is not performed if there is no authority.
[0030]
If there is an authority to generate, the corresponding character string is stored in the corresponding generation pattern as described above (step 460).
Then, the generation pattern storing the character string is stored in the location designated by the designated file name (step 470).
The above describes an example in which a new HTML document is generated based on the knowledge conclusion management table. However, a new HTML document can be generated in the same manner from an HTML document including link information. Specifically, this will be described with reference to FIG. 11A shows an HTML document including link information, and FIG. 11B shows a newly generated HTML document. In the case of the HTML document in FIG. 11A, “<A HREF =” xxx. “html”><B> Details of facility </ B></A> ”corresponds to the link information, and on the WWW browser screen, only“ About the details of the facility ”is displayed. When the operator clicks the display location of “about facility details” with the mouse, “xxx.html” becomes the reception target file. A case where the file “xxx.html” is automatically generated will be described.
[0031]
The link information in the HTML document of FIG. 11A is “<A HREF =” xxx. html "><B> about facility </ B></A>", and the character string of the name to be extracted is "about facility". Then, the extracted character string “about facility” is stored between “<TITLE>” and “</ TITLE>” as a new HTML document, and is generated with a file name “xxx.html”.
[0032]
Next, information on the presence / absence of the corresponding file, information on whether or not the file has been automatically generated, file type, file name (or URL name), name, identification code (ID), and information on the current hierarchical level are shown in FIG. 6 (step 341). At this time, information on the presence / absence of the corresponding file and whether it was automatically generated is also stored in the knowledge conclusion management table of FIG.
[0033]
The information indicating whether or not it is automatically generated is “NULL” at the initial stage, and becomes “generated” when newly automatically generated. When the file is corrected by the editing process, it is returned to “NULL”.
The file type, file name (or URL name), name, and identification code (ID) are extracted from the knowledge conclusion management table of FIG. The hierarchy level indicates the depth of the hierarchy when the inspection target file has an inspection start point of 1.
[0034]
If the designated file actually exists in step 330, it is next determined whether there is link information from the file (step 340). In the “intelligent information retrieval program creation system” to which the present invention is applied, the knowledge information file (knowledge table) is transferred to a conclusion file or knowledge information file (knowledge table) that is a reception target by answering a question. For example, the knowledge table K2 (12) in FIG. 4 has R4 and R5 as conclusion information files, and K3 and K4 as knowledge information files (knowledge tables). Have.
[0035]
If the result of determination in step 340 is that there is no link information from the designated file, the processing of step 341 described above, ie, the existence / generation status of the file, file type, file name, and hierarchical level information Memorize.
If the result of determination in step 340 is that there is link information from the specified file, the file existence / generation status, file type, file name, and hierarchy level information are stored as described above (step 350). Then, the first file of the link information is taken out and used as a designated file for the next processing (step 360).
[0036]
Then, the current hierarchical level is incremented by 1, and the check process of this link structure is recursively called using the previously specified file as the inspection start point (step 370). Next, after the recursive call processing is completed, the current hierarchy level is reduced by 1 (step 371).
It is determined whether there is another file in the link information (step 373). If there is no other unprocessed file, this process is terminated. If there is another unprocessed file, the next file is designated as the designated file (step 373). And the process after step 370 is performed.
[0037]
【The invention's effect】
According to the present invention, since it is possible to easily know which information file needs to be created, creation of a structured information file is facilitated.
In addition, since the necessary information file is automatically generated based on the link information, it is possible to avoid storing documents created later in different locations or using different file names. Creating an information file is easy.
[Brief description of the drawings]
FIG. 1 is a principle diagram of the present invention.
FIG. 2 is a processing flow of the present invention.
FIG. 3 is a link structure processing flow.
FIG. 4 is a diagram illustrating a relationship between a knowledge table and a conclusion information file.
FIG. 5 is a diagram showing a configuration of a knowledge conclusion management table.
FIG. 6 is a diagram showing a configuration of a display work table.
FIG. 7 is a display example (No. 1) of the link relation of the structured information file.
FIG. 8 is a display example (No. 2) of the link relation of the structured information file.
FIG. 9 is an automatic generation process flow of an HTML document.
FIG. 10 is an example of an automatically generated conclusion information file.
FIG. 11 is an example of automatic generation from an HTML document.
[Explanation of symbols]
1A, 1B WWW server 2 WWW client 3 Determination means 4 Output means 5 Generation means 6A, 6B Structured information file storage section 7 Internet

Claims (4)

In a structured information file inspection device having link information from an information file to another information file,
Determination means for determining whether or not the corresponding information file exists based on link information from the information file to another information file;
Structuring characterized by comprising generation means for generating an information file with a corresponding file name embedded with a corresponding title in a corresponding location based on the link information when the corresponding information file does not exist Information file inspection device. A management table storing the link information;
2. The structured information file inspection device according to claim 1, wherein the generation unit generates an information file based on information on a title, a file name, and a location stored in the management table. Each information file contains link information to other information files,
2. The structured information file inspection apparatus according to claim 1, wherein the generation unit generates an information file based on information on a title, a file name, and a location indicated by the link information. Computer
Determination means for determining whether or not the corresponding information file exists based on link information from the information file to another information file;
When there is no corresponding information file, structured information is made to operate as a generation means for generating an information file with the corresponding title embedded with the corresponding title in the corresponding location based on the link information. A computer-readable recording medium on which a file inspection program is recorded.

Images