WO2000072190A1

WO2000072190A1 - Method for supporting development of internet contents, recorded medium on which program for implementing the same is recorded, and system for implementing the same

Info

Publication number: WO2000072190A1
Application number: PCT/JP1999/002611
Authority: WO
Inventors: Shuichi Matsuda; Takashi Kawashima; Minoru Masuda; Akiko Mogi
Original assignee: Fujitsu Limited
Priority date: 1999-05-19
Filing date: 1999-05-19
Publication date: 2000-11-30

Abstract

A method for supporting development of Internet contents characterized by comprising preparing a link definition file containing link definition information corresponding to HTML files constituting Internet contents, extracting link definition information described in reference tags in the HTML files made, and recognizing the coincidence relation between the extracted link definition information and the link definition information contained in the link definition file. As a result, the error/correctness of the link relation between HTML files made is easily judged, and the reliability of link relation is improved.

Description

Description: Internet content development support method, recording medium storing program for executing the method, and system for executing the same

[Technical field]

The present invention relates to an Internet content development support method for supporting development work such as creation and update management of Internet content home pages.

[Background technology]

Conventionally, when developing in-net content (homepage), the components of each screen (image sound, HTML file, CGI program, etc.) are visually checked. In addition, when confirming the link definition between homepages, the user can view the homepage screen of the link destination, such as clicking with a mouse, on the personal computer screen and visually check it.

On the other hand, the scale of content development reaches hundreds of homepages in large scale. In this way, with the spread of the Internet, the scale of content is expanding, and the hierarchy is becoming deeper and more complex.

Under such circumstances, for the purpose of confirming the definition of the link between the home pages at the time of development, such as creation and update of the home page, as described above, the home page is displayed on the screen and relied on human visual inspection. Therefore, there is a high probability of omission of confirmation or confirmation mistake, and enormous time is spent on the confirmation work. Also, when updating (including deleting) link definitions at the time of updating, they are conventionally performed manually one by one, so there is a high possibility of omissions or incorrect corrections, and enormous time is required for the correction work. It was necessary.

Therefore, an object of the present invention is to provide a method for supporting the development of an in-net content that automatically checks the validity of the link definition between homepages and automatically corrects the link definition between homepages. An object of the present invention is to provide a recording medium storing a program for executing the program and a system for executing the program. [Disclosure of the Invention]

In order to achieve the above object, a first Internet content development support method of the present invention comprises a link definition having link definition information corresponding to each html file in a plurality of html files constituting Internet content. Steps to create a file,

Extracting link definition information described in reference tags of the created html files,

A step of determining a coincidence between the extracted link definition information and the link definition information included in the link definition file.

According to the present invention, the correctness of the link relation between a plurality of created html files can be easily determined, and the reliability of the link relation can be improved.

Further, the second method for supporting Internet content development according to the present invention includes: a step of extracting link definition information described in reference tags of a plurality of created html files;

Generating a component definition file having link definition information corresponding to each html file based on the extracted link definition information;

Determining a match between the link definition information described in the reference page of the html file updated after the creation and the link definition information of the component definition file.

According to the present invention, it is possible to easily determine whether the link relation between a plurality of updated html files is correct or not, and to improve the reliability of the link relation.

In addition, the third method for supporting the development of Internet content according to the present invention includes a command having command information for correcting and / or deleting the reference tag corresponding to the link destination file name described in the reference tag of each html file. Creating a file,

Extracting a reference page having a link destination file name corresponding to the command file;

Modifying and / or deleting the extracted reference tags in accordance with the command information. According to the present invention, the modification / deletion of reference tags in an html file can be performed collectively without omission.

Further, a fourth method for supporting Internet content development according to the present invention comprises the steps of: creating a link definition file having link definition information corresponding to each html file;

Generating an html file in which reference tags based on link definition information are described for each html file.

According to the present invention, a plurality of html files having a correct link relationship can be generated.

The present invention also provides a recording medium storing a program for executing the above method, and an Internet content development support system for executing the above method.

[Brief description of drawings]

FIG. 1 is a diagram for explaining an internet content development support process according to the embodiment of the present invention.

Fig. 2 is a schematic block diagram of the Internet content development support system.

Figure 3 is a diagram for explaining the link relationship on the homepage.

FIG. 4 is a diagram showing an example of the link definition file 103.

FIG. 5 is a diagram showing an example of the check result output data 105.

FIG. 6 is a diagram showing an example of the component cross reference table 106.

FIG. 7 is a diagram showing an example of the deletion / modification definition file 107.

FIG. 8 shows a flowchart of an automatic check process for checking the link relationship of the source file 102 based on the link definition file 103.

FIG. 9 is a diagram for explaining a case where an error message is output.

FIG. 10 shows a flowchart of the process of creating the component definition file 104. FIG. 11 shows a flowchart of the output process of the component cross reference table 106.

FIG. 12 shows a flowchart of the link definition deletion / modification process. FIG. 13 is a diagram showing a flowchart of a process of creating an html file based on the link definition file 104.

[Best Mode for Carrying Out the Invention]

Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the technical scope of the present invention is not limited by such an embodiment.

FIG. 1 is a diagram for explaining an internet content development support process according to an embodiment of the present invention. In FIG. 1, an Internet content development support system 101 is, for example, a computer system including a personal computer.

FIG. 2 is a schematic block diagram of a convenience viewing system that is the Internet content development support system 101. As shown in FIG. As shown in the figure, the computer system is composed of a CPU 201, a keyboard 202, a mouse 203, a printer 204, a LAN line 205, a storage device such as a CD-ROM device and a hard disk. 6, memory 206, display 208, etc. The storage device 206 stores a program for executing a development support process according to an embodiment of the present invention described later, and the CPU 201 executes the program.

Returning to FIG. 1, the source file 102 is a group of html files of a plurality of homepages that are in-net contents described in the HTML language, and is created by manual input by a human. Further, the link definition file 103 is a file having a link relationship between the in-net content (homepage) in the source file 102 and is created by manual data input. .

Figure 3 is a diagram for explaining the link relationship on the homepage. In FIG. 3, the title of the homepage 611 is “comprehensive index”, and the file name of the html file 601 is “index.html”.

Here, in the html file 601, the title tag is

T TITLE> Thailand

And the reference tag is

A HREF = "Link destination file name"> Link destination name / A> The link definition information has a link destination file name that is the file name of the link destination html file, and a link destination name that is a screen display character corresponding to the link destination html file.

Therefore, the html file 6001 contains the file name of the linked homepage “a.html”, “b.html”, “c.html” and the title of the linked homepage as the corresponding screen display character. "Xx information", "yy guide", "topics" are described. The home page 611 displays the titles of the linked home pages “xx information”, “y guide”, and “topics”. Then, when the user clicks the displayed title with the mouse, the linked home page is displayed. More specifically, clicking on “xx information” on the home page 6 11 displays the home page 6 1 2 (title “xx information”). In the html file 602 (file name “a.html”) of this home page 612, the file name “index.html” of the linked home page and the screen display character “return” are described. Therefore, the home page 6 1 1 is displayed by clicking “Back” displayed on the home page 6 1 2. Clicking on “y y guide” on the home page 6 11 will display the home page 6 13 (title “y guide”). The html file 603 (file name “b.html”) of the homepage 613 describes the file name “index.html” of the linked homepage and the screen display character “return”. Therefore, by clicking "Back" displayed on the home page 6 13, the home page 6 11 is displayed. Furthermore, when you click “Topics” on the home page 6 11, the home page 6 14 (title “Topics”) is displayed. The html file 604 (file name “c.html”) of this home page 614 describes the file name “index.html” of the linked home page and the screen display character “return”. Therefore, the home page 611 is displayed by clicking "Back" displayed on the home page 614.

FIG. 4 is a diagram showing an example of the link definition file 103. FIG. 4 shows a link definition file 103 corresponding to the link relationship shown in FIG. 3 as an example. In other words, the link definition file 103 contains a link destination name and Link destination file name and link destination title data.

This link definition file 103 is created before the actual creation of the homepage (creating the source file 102) as a summary of the link relationship between the homepages to be created in advance. Then, after the source file 102 is created, the in-net content development support system 101 compares the link relationship of the source file 102 with the data of the link definition file 103. As a result, a check operation for checking whether or not there is an input error in the created source file 102 is automatically performed. Therefore, it is possible to reduce the checking work, to prevent a checking mistake and omission of checking, and to create a highly reliable source file 102.

Returning to FIG. 1, the component definition file 104 has the same data as the link definition file 103 of FIG. 3, that is, a file having the link-related data of the source file 102. Unlike definition file 1 ◦ 3, it is automatically created based on the component definition file creation processing described later by the file development support system 101. That is, the component definition file 104 has a role as a master file from which the link relation of the completed source file 102 is extracted. For example, if the source file 102 is updated after the completion of the source file 102, the correctness of the link relationship of the source file 102 is confirmed again using the component definition file 104 after the update. be able to. More specifically, it is possible to find an error in the link relation when the description of the reference tag is changed by mistake when inputting update data manually at the time of updating.

The check result output data 105 is an output data of a comparison result between the link relation in the source file 102 and the link relation in the link definition file 103. Is output. This makes it possible to easily confirm whether or not the link relation in the source file 102 is correctly defined, that is, whether or not it matches the link relation in the link definition file 103.

FIG. 5 is a diagram showing an example of the check result output data 105. As shown in Fig. 5, an error message is displayed for the target html file whose link relationship does not match. A message is output.

The component cross-reference file 106 is a list of file names of linked files of each html file, and is output by the component cross-reference output process described later.

FIG. 6 is a diagram showing an example of the component cross-reference data 106. In FIG. 6, each target html file in the link definition file 103 and the corresponding reference file which is the name of all linked files are output as list data. This makes it easy to check which html file is linked to which html file.

As described in the link definition deletion / modification processing described later, the deletion / modification definition file 107 uses the component definition file 104 to generate the link definition described in the source file 102. Command files used for batch deletion / batch correction, created by manual input.

FIG. 7 is a diagram showing an example of the deletion / modification definition file 107. In FIG. 7, the command “c” is a correction command for changing the link destination file name and the link destination name of the corresponding reference tag, and the command “d” is a deletion command for deleting the reference tag. Command. For example, command example 1 shows the link destination file names of all the reference tags in which "k.html" is described as the link destination file name among all the reference tags in the html file of the source file 102. Is changed to “index.html” and the link destination name is changed to “Back to Contents”. In command example 2, among all the reference tags in the html file of the source file 102, the link destination name of all the reference tags in which "htmlj" is described as the link destination file name is changed to "TOPICS". This is the command to perform. In addition, Command Example 3 is used to delete all the reference tags in which “q.html” is described as the link destination file name among all the reference tags in the html file of the source file 102. Command.

FIG. 8 shows a flowchart of an automatic check process for checking the link relationship of the source file 102 based on the link definition file 103. This processing corresponds to the processing flow of arrow A in FIG. In step S801, first, phosphorus The network definition file 103 is read. In step S802, when the header is initially set in the leading component definition information sequence of the read link definition file 103, in step S803, the pointer is set in the component definition information sequence in which the pointer is initialized. The target html file name is initialized. For example, in the link definition file 103 in Fig. 4, the file name "index.html" is initialized.

In step S804, a screen prompting the input of the initially set target html file name is displayed on the display 208, and the user inputs it using the keyboard 202. In step S805, the target html file name initially set in the link definition file 103 is set as the target html file, and the initial setting is completed.

In step S806, the html file set in the target html file is read from the source file 102. In step S807, the description of the read html file is analyzed to determine whether there is a reference tag. If there is a reference evening, the process proceeds to step S808. In step S808, the link destination name and the link destination file name are extracted from the reference evening. In steps S809 and S810, the extracted link destination name and link destination file name are linked with the link destination name and link destination file name defined corresponding to the target html file in the link definition file 103. They are matched to determine if they match.

If they do not match, a link destination name mismatch error message and a link destination file name mismatch error message are output in steps S820 and S821, respectively, and the process returns to step S807. The error message is output as check result output data in Fig. 5.

FIG. 9 is a diagram for explaining a case where an error message is output. For example, in step S806, the html file 701 of the target html file “b.html” is read from the source file 102. The html file 70 1 describes a title TITLE> yy guide </ TITLE> and a reference <HREF = "home.html"> home / A>. Therefore, the title “yy guide” and the link destination name “home” are displayed on the homepage screen 711 corresponding to this html file. However, the link of this html file 7 0 1 The name (“home”) and the link destination file name (“home.html”) are the link destination name (“home.html”) of the component definition information column corresponding to the target html file “b.html” in the link definition file 103. It does not match with "Back") and linked file name ("index.html"). Therefore, in step S809 described above, it is determined that the link destination names do not match, so the process proceeds to step S S820, and an error message indicating that the link destination names do not match is output in the check result output data (see FIG. 5). ).

If they match in steps S809 and S810, in step S811, the html file corresponding to the link destination file name is read from the file 102, and the title is extracted. Then, in step S812, the extracted title is compared with the link destination title of the target html file against the link destination title defined corresponding to the target html file in the link definition file 103. To determine if they match.

If they do not match, in step S822, a link destination title mismatch error message is output, and the process returns to step S807. If they match, the link relationship of the reference tag detected in step S807 matches the component definition information string to which the pointer is set in the link definition file 103 and it is defined correctly. It is confirmed.

Then, in step S813, the point setting in the link definition file 103 is updated to the next component element definition information sequence, and the process returns to step S807. In step S807, the description of the html file of the set target html file is analyzed again, and the next reference tag is searched. If there is a reference tag, the processing from step S808 described above is performed. If there is no reference evening, the process proceeds to step S830, and the next target html file is set. For the next target file, in the link definition file 103, the target html file of the component definition column to which the pointer is set is set. In step S831, it is checked whether the next target file exists. If so, the next target html file that has been set is read from the source file 102 in step S806. If not, the process ends.

In this way, all the html files in the source file 102 are linked. By comparing the link relationship with the link definition file 103, the correctness can be automatically checked.

In step S811, S812, and S822, the match determination based on the link definition information (link destination file name and link destination name) is performed without performing the match determination of the title. Is achieved, but in order to further enhance the checking function, it is preferable to further determine whether the title matches. In addition, when the title match determination is not performed, the link definition file 103 does not need to have the information of the link destination title.

FIG. 10 shows a flowchart of the process of creating the component definition file 104. This processing corresponds to the processing flow of arrow B in FIG. In step S1001, a character string is initially set in the first element definition column area in the element definition file 104. In step S1002, the html file having the file name “index on tml” is set as the target html file to be initialized in the component definition file 10. In step S1003, a screen for prompting the user to input the target html file name initially set in the display 208 is displayed, and the user inputs it using the keyboard 202. In step S1004, the target html file name initially set in the component definition file 104 is set as the target html file, and the initial setting is completed.

In step S1005, the html file set in the target html file is read from the source file 102. In step S1006, the description of the read html file is analyzed to determine whether there is a reference tag. If there is a reference tag, the process proceeds to step S1007. In step S1007, a link destination name and a link destination file name are extracted from the reference tag.

Further, in step S1008, the html file corresponding to the link destination file name is read from the source file 102, and the title is extracted. Then, in step S1009, the extracted link destination name, link destination file name, and link destination title are written in the component definition column in which the pointer of the component definition file 104 is set. Note that the component definition file 104 does not need to have the information of the link destination title similarly to the link definition file 103. Then, in step S1010, the setting of the position in the component definition file 104 is updated to the next component definition information string area, and the process returns to step S1006. In step S1006, the description of the html file of the set target html file is analyzed again, and the next reference tag is searched. If there is a reference tag, the processing from step S1007 described above is performed. If there is no reference tag, the process proceeds to step S1011, and the next target html file is set. As the next target file, the html file corresponding to the link destination file name in the component definition column written before updating the pointer in step S1010 is set. In step S1012, it is checked whether or not the next target html file exists. If so, in step S1013, the next target html file is set as the target html file of the already written component element definition information sequence. The existence is checked. If not, the processing from step S1005 is repeated. If the pointer exists, the process returns to step S1011, and an html file corresponding to the link destination file name of another component element definition column written before updating the pointer is set. If the next target html file does not exist in step S1012, the process ends.

FIG. 11 shows a flowchart of an output process of the component cross-reference data 106. This processing corresponds to the processing flow of arrow C in FIG. First, in step S1101, the component definition file 104 is read. In step S1102, one target html file is extracted in order from the leading component definition information sequence in the read component definition file 104. When the target html file is extracted in step S1103, the extracted html file name is set as the target html file of the component cross-reference data in step S1104. Then, in step S1105, the link destination file names of the set target html files are extracted one by one. If the extraction of the link destination file name does not end in step S1106 (the link destination file name has been extracted), it is determined in step S1107 whether or not it has already been added as a reference file corresponding to the target html file. . If not added, refer to the target html file of the component cross-reference data. The extracted link destination file name is added as the reference file, the process returns to step S1105, and the link destination file is extracted again. In step S1106, if there is a link destination file name that has not been extracted yet, steps S1107 and S1108 described above are repeated. When the extraction of all the link destination file names corresponding to the target html file is completed, the target html file is extracted. Is output as the component cross-reference data corresponding to.

When the process returns to step S1102, a target html file that has not been extracted from the component definition file 104 is extracted, and the processes from step S1103 onward are repeated. Then, in step S1103, when the extraction of all target html files in the component definition file 104 ends, the process ends. FIG. 12 shows a flowchart of the link definition deletion / modification process. This processing corresponds to the processing flow of arrow D in FIG. First, in step S1201, the deletion / modification definition file 107 is read, and in step S1202, the component definition file 104 is read. In step S1203, command files are extracted one by one from the first command line in the read deletion / modification definition file. In step S1204, when the command file is extracted, in step S1205, if the extracted command file is a change command, the process proceeds to step S1210, and in step S1206, the extracted command file is deleted. If it is a (delete) command, the process proceeds to step S1220.

First, if the command file is a change (change) command, in step S1210, a target html file having a link target file name to be corrected is searched from the link destination file names of the component definition file 104. If there is a target html file in step S1211, it is read from the source file 102 in step S1212, and in step S1213, the presence or absence of a reference tag is determined. If there is a reference tag, in step S1214, it is confirmed that the link destination file name in the reference tag is the link destination file name to be corrected, and in step S1215, the correction command includes the new link destination file name in the correction command. If it is confirmed that the name has been set, go to step S1216. Then, the link destination file name in the reference tag is changed to the new link destination file name. If it is confirmed in step S1217 that the new link destination name is set in the correction command, the link destination name in the reference tag is changed to the new link destination name in step S1218.

Then, with one correction command, all the html files having the old link destination file name to be corrected and all the reference tags are automatically searched, so that the link destination to be corrected without any omission is corrected. All file names and link destination names can be modified. Therefore, the work efficiency is greatly improved as compared with the conventional manual correction work.

If the command file is a delete command, in step S1220, a target html file having the old link destination file name to be deleted is searched from the link destination file names of the component definition file 104. If there is a target html file in step S1221, it is read from the source file 102 in step S1222, and it is determined in step S1223 whether there is a reference tag. If there is a reference tag, in step S1224, when it is confirmed that the link destination file name in the reference evening is the link destination file name to be deleted, the reference tag is deleted in step S1225. Then, for one deletion command, all html files having the link destination file name to be deleted and all the reference tags are automatically searched, so that all the reference tags to be deleted can be deleted without omission. Can be deleted. Therefore, the work efficiency is greatly improved as compared with the conventional manual deletion work.

In this process, a link definition file 102 may be used instead of the component definition file 104.

FIG. 13 is a diagram showing a flowchart of a process of creating an html file based on the link definition file 103. If the link definition file 103 is created before creating the source file 102, the reference tags are automatically described when creating the html file based on the link relationship in the link definition file 103. It is possible to do. This processing corresponds to the processing flow indicated by arrow E in FIG. In step S1301, the link definition file 104 is read, and in step S1302, the target html files of the link definition file 103 are sequentially extracted one by one. If one target html file is extracted in step S1303, a description area corresponding to the target html file is generated in step S1304. Then, in step S1305, the link destination file names of the target html file are extracted one by one from the link definition file 103. When one link destination file name is extracted in step S1306, the corresponding link destination name is extracted in step S1307. Then, in step S1308, the extracted link destination file name and the reference tag having the link destination name are written in the description area of the target html file.

In this way, the description area of all target html files in the link definition file 103 is created, and all reference tags in each target html file are written. This eliminates the need to manually describe the reference tag, thereby reducing the input work. Also, since there is no mistake in inputting the reference tag, there is no need to check the link relation between the html files.

[Possibility of industrial use]

As described above, according to the present invention, it is possible to automatically check the link relation of contents in the creation and update of Internet contents. Therefore, it is not necessary to check the link relationship between the source files of the contents by the conventional visual inspection, so that the number of man-hours is greatly reduced, and the reliability of the link relationship of the content is also greatly improved.

Claims

The scope of the claims

1. In an Internet content development support method that supports the development of multiple html files that compose Internet content,

Creating a link definition file having link definition information corresponding to each html file;

A step of determining a correspondence between the extracted link definition information and the link definition information included in the link definition file.

2. In Claim 1,

A method for supporting Internet content development, wherein the link definition information is a link destination file name and a link destination name described in a reference tag of an html file.

3. In Claim 2,

The link definition file further includes title information of an html file corresponding to the link definition information,

A step of determining a coincidence between the title of the html file of the link destination file name extracted in the extraction step and the title information of the link definition file. Development support method.

4. In any of claims 1 to 3,

A cross-reference data development method, comprising outputting cross-reference data having information on a link destination file name corresponding to each html file based on the link definition file.

5. In the Internet content development support method for supporting the development of a plurality of html files constituting Internet content,

A link definition information described in a reference page of an html file updated after the creation, and a step of determining a matching relationship between the link definition information of the component definition file and the link definition information. Net content development support method.

6. In Claim 5,

The method for supporting the development of Internet content on the Internet, wherein the link definition information is a link destination file name and a link destination name described in a reference tag of an html file.

7. In Claim 6,

The component definition file has title information of an html file corresponding to the extracted link definition information,

An Internet content development support method comprising: determining a correspondence between a title of an html file having a link destination file name extracted in the extraction step and title information of the component definition file. .

8. In any of claims 5 to 7,

A method for supporting Internet content development, comprising outputting cross-reference data having information on a link destination file name corresponding to each html file based on the component definition file.

9. In the Internet content development support method that supports the development of multiple html files that compose Internet content, Creating a command file having command information for correcting and / or deleting the above-mentioned reference tags corresponding to the link destination file name described in the reference tag of each html file;

Correcting and / or deleting the extracted reference tag in accordance with the command information.

10. In claim 9,

The method according to claim 1, wherein the command information includes a command for correcting a link destination file name and / or a link destination name described in a reference page.

1 1. In Claim 9,

The method for supporting Internet content development, wherein the command information includes a command for deleting a reference tag.

1 2. In the Internet content development support method that supports the development of multiple html files that compose Internet content,

Generating an html file in which reference tags based on the link definition information are described for each html file.

1 3. On a recording medium that stores a program for supporting the development of multiple html files that make up Internet content,

Read a link definition file that has link definition information corresponding to each html file. With the step

A storage medium storing a program, comprising: a step of determining a match between the extracted link definition information and link definition information included in the link definition file.

14 4. In a storage medium storing a program for supporting the development of a plurality of html files constituting the Internet content,

A step of generating a component definition file having link definition information corresponding to each html file based on the extracted link definition information;

Stores a program characterized by comprising link definition information described in a reference page of an html file updated after creation and a step of determining a match between the link definition information of the component definition file. Recording medium.

15 5. In a recording medium that stores a program for supporting the development of multiple html files that compose Internet content,

A step of reading a command file having command information for correcting and / or deleting the above-mentioned reference tag corresponding to the link destination file name described in the reference tag of each html file,

A step of correcting and / or deleting the extracted reference message in accordance with the command information.

16 6. In a storage medium storing a program for supporting the development of a plurality of html files constituting the Internet content, Reading a link definition file having link definition information corresponding to each html file;

Generating a html file in which a reference tag based on the link definition information is described for each html file.

17 7. In an Internet content development support system that supports the development of multiple html files that make up Internet content,

A reading unit that reads a link definition file having link definition information corresponding to each html file;

An extraction unit for extracting link definition information described in reference tags of the plurality of created html files,

An internet content development support system, comprising: a determination unit that determines a correspondence between the extracted link definition information and link definition information included in the link definition file.

1 8. Internet content development support system that supports the development of multiple html files that make up Internet content

A generating unit that generates a component definition file having link definition information corresponding to each html file based on the extracted link definition information;

An internet connection network comprising: a link definition information described in a reference tag of an html file updated after creation; and a determination unit that determines a match between the link definition information included in the component definition file. Content development support system.

1 9. In an in-net content development support system that supports the development of multiple html files that make up in-net content,

According to the link destination file name described in the reference tag of each html file, A reading unit for reading a command file having command information for correcting and / or deleting a reference message;

An extraction unit for extracting a reference page having a link destination file name corresponding to the command file;

A processing unit for correcting and / or deleting the extracted reference tag in accordance with the command information;

20. In the Inuichi Net Content Development Support System, which supports the development of multiple html files that make up the Internet content,

A generation unit for generating, for each html file, an html file in which reference tags based on the link definition information are described, an Internet content development support system.