WO2000072190A1 - Procede pour prendre en charge la mise au point de contenus internet, support d'enregistrement contenant le programme applicatif du procede, et systeme d'application du procede - Google Patents

Procede pour prendre en charge la mise au point de contenus internet, support d'enregistrement contenant le programme applicatif du procede, et systeme d'application du procede Download PDF

Info

Publication number
WO2000072190A1
WO2000072190A1 PCT/JP1999/002611 JP9902611W WO0072190A1 WO 2000072190 A1 WO2000072190 A1 WO 2000072190A1 JP 9902611 W JP9902611 W JP 9902611W WO 0072190 A1 WO0072190 A1 WO 0072190A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
link
html
link definition
definition information
Prior art date
Application number
PCT/JP1999/002611
Other languages
English (en)
Japanese (ja)
Inventor
Shuichi Matsuda
Takashi Kawashima
Minoru Masuda
Akiko Mogi
Original Assignee
Fujitsu Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fujitsu Limited filed Critical Fujitsu Limited
Priority to PCT/JP1999/002611 priority Critical patent/WO2000072190A1/fr
Publication of WO2000072190A1 publication Critical patent/WO2000072190A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting

Definitions

  • 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.
  • 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.
  • 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.
  • 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,
  • 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.
  • the second method for supporting Internet content development includes: a step of extracting link definition information described in reference tags of a plurality of created html files;
  • 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.
  • the third method for supporting the development of Internet content 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.
  • 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.
  • a fourth method for supporting Internet content development comprises the steps of: creating a link definition file having link definition information corresponding to each html file;
  • 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.
  • 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.
  • FIG. 1 is a diagram for explaining an internet content development support process according to an embodiment of the present invention.
  • 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.
  • 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.
  • 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.
  • 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.
  • the title of the homepage 611 is “comprehensive index”
  • the file name of the html file 601 is “index.html”.
  • 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.
  • 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”).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the deletion / modification definition file 107 uses the component definition file 104 to generate the link definition described in the source file 102.
  • FIG. 7 is a diagram showing an example of the deletion / modification definition file 107.
  • the command “c” is a correction command for changing the link destination file name and the link destination name of the corresponding reference tag
  • the command “d” is a deletion command for deleting the reference tag.
  • 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”.
  • 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.
  • 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.
  • step S801 first, phosphorus The network definition file 103 is read.
  • 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.
  • 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.
  • 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.
  • step S806 the html file set in the target html file is read from the source file 102.
  • 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.
  • step S808 the link destination name and the link destination file name are extracted from the reference evening.
  • 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.
  • 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.
  • the html file 701 of the target html file “b.html” is read from the source file 102.
  • step S809 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). ).
  • 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.
  • step S822 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.
  • 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.
  • 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.
  • the target html file of the component definition column to which the pointer is set is set.
  • 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.
  • 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.
  • step S1001 a character string is initially set in the first element definition column area in the element definition file 104.
  • 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.
  • 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.
  • 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.
  • step S1005 the html file set in the target html file is read from the source file 102.
  • 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.
  • step S1007 a link destination name and a link destination file name are extracted from the reference tag.
  • 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.
  • step S1011 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.
  • step S1101 the component definition file 104 is read.
  • step S1102 one target html file is extracted in order from the leading component definition information sequence in the read component definition file 104.
  • step S1103 the extracted html file name is set as the target html file of the component cross-reference data in step S1104.
  • step S1105 the link destination file names of the set target html files are extracted one by one.
  • step S1107 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.
  • FIG. 12 shows a flowchart of the link definition deletion / modification process. This processing corresponds to the processing flow of arrow D in FIG.
  • step S1201 the deletion / modification definition file 107 is read, and in step S1202, the component definition file 104 is read.
  • step S1203 command files are extracted one by one from the first command line in the read deletion / modification definition file.
  • 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.
  • 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.
  • step S1217 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.
  • 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.
  • 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.
  • 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.
  • step S1305 the link destination file names of the target html file are extracted one by one from the link definition file 103.
  • step S1306 the link destination file name is extracted in step S1306.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Artificial Intelligence (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Computational Linguistics (AREA)
  • General Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un procédé de prise en charge de la mise au point de contenus Internet. Le procédé consiste à préparer un fichier de définition de liens qui contient des données de définition de liens correspondant à des fichiers HTML constituant les contenus Internet, à extraire d'étiquettes de référence lesdites données de définition de liens dans les fichiers HTML constitués. Le procédé consiste ensuite à reconnaître la relation coincidente entre les données de définition de liens extraites et les données de définition de liens contenues dans le fichier de définition de liens. On peut ainsi apprécier facilement l'inadéquation ou la pertinence de la relation entre les fichiers HTML constitués, ce qui améliore la fiabilité de cette relation.
PCT/JP1999/002611 1999-05-19 1999-05-19 Procede pour prendre en charge la mise au point de contenus internet, support d'enregistrement contenant le programme applicatif du procede, et systeme d'application du procede WO2000072190A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP1999/002611 WO2000072190A1 (fr) 1999-05-19 1999-05-19 Procede pour prendre en charge la mise au point de contenus internet, support d'enregistrement contenant le programme applicatif du procede, et systeme d'application du procede

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP1999/002611 WO2000072190A1 (fr) 1999-05-19 1999-05-19 Procede pour prendre en charge la mise au point de contenus internet, support d'enregistrement contenant le programme applicatif du procede, et systeme d'application du procede

Publications (1)

Publication Number Publication Date
WO2000072190A1 true WO2000072190A1 (fr) 2000-11-30

Family

ID=14235739

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP1999/002611 WO2000072190A1 (fr) 1999-05-19 1999-05-19 Procede pour prendre en charge la mise au point de contenus internet, support d'enregistrement contenant le programme applicatif du procede, et systeme d'application du procede

Country Status (1)

Country Link
WO (1) WO2000072190A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006190253A (ja) * 2004-12-30 2006-07-20 Microsoft Corp ウェブページのアスペクトを評価するための方法と装置
JP2006236084A (ja) * 2005-02-25 2006-09-07 Ricoh Co Ltd データベース装置
JP2007133763A (ja) * 2005-11-11 2007-05-31 Nippon Telegr & Teleph Corp <Ntt> 要素情報比較装置およびプログラム
JP2008097617A (ja) * 2007-10-26 2008-04-24 Nec Corp ハイパーテキスト検査装置および方法ならびにプログラム
JP2016212881A (ja) * 2015-05-08 2016-12-15 キヤノンマーケティングジャパン株式会社 情報処理装置とその処理方法及びプログラム

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Microsoft Frontpage98 for Windows Katsuyou Guide", 1 October 1997 (01.10.97) Microsoft Co., Ltd., pages 14-23, 96-119, 152-158. *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006190253A (ja) * 2004-12-30 2006-07-20 Microsoft Corp ウェブページのアスペクトを評価するための方法と装置
JP2006236084A (ja) * 2005-02-25 2006-09-07 Ricoh Co Ltd データベース装置
JP2007133763A (ja) * 2005-11-11 2007-05-31 Nippon Telegr & Teleph Corp <Ntt> 要素情報比較装置およびプログラム
JP2008097617A (ja) * 2007-10-26 2008-04-24 Nec Corp ハイパーテキスト検査装置および方法ならびにプログラム
JP2016212881A (ja) * 2015-05-08 2016-12-15 キヤノンマーケティングジャパン株式会社 情報処理装置とその処理方法及びプログラム

Similar Documents

Publication Publication Date Title
AU2005225130B2 (en) Management and use of data in a computer-generated document
CN100489849C (zh) 用于绑定数据的可编程性
US7734577B2 (en) Composite user interface and framework
US8359550B2 (en) Method for dynamically generating a “table of contents” view of the HTML-based information system
US8689137B2 (en) Command user interface for displaying selectable functionality controls in a database application
US7376895B2 (en) Data object oriented repository system
JP4396994B2 (ja) リソース・ファイルの翻訳検証方法、装置、およびプログラム
JP4924976B2 (ja) ソフトウェア開発支援システム
JP2008503830A (ja) ウェブブラウザ上で直接ウィジウィグ編集が可能な組立式ホームページと、個人ポータルサイトの作成と編集、取引方法及びそのプログラム記録媒体
US5982365A (en) System and methods for interactively generating and testing help systems
JPH10124380A (ja) 多層バックグラウンドを有する文書から単層文書を自動生成する方法及びそのための装置
US7191400B1 (en) Methods for generating and viewing hyperlinked pages
JP3023943B2 (ja) 文書検索装置
US20140032480A1 (en) Form template refactoring
JP3601675B2 (ja) 情報検索装置、情報検索方法、及び記録媒体
WO2000072190A1 (fr) Procede pour prendre en charge la mise au point de contenus internet, support d&#39;enregistrement contenant le programme applicatif du procede, et systeme d&#39;application du procede
JP2006127117A (ja) Ｗｅｂ閲覧操作の記録・再生方法及び装置及びプログラム及びプログラムを格納した記憶媒体
JP5016333B2 (ja) 文書作成支援装置及び文書作成支援プログラム
JPH0778139A (ja) コメント付与方法及び文書処理装置
Libes Writing CGI scripts in Tcl.
JP2020115246A (ja) 生成装置、ソフトウェアロボットシステム、生成方法及び生成プログラム
US7613709B2 (en) System and method for editing operations of a text object model
JP4724283B2 (ja) 文書管理装置、文書管理方法および記憶媒体
JP3672473B2 (ja) 個体名の抽出装置、抽出方法、並びに、記録媒体
JP2009151727A (ja) 文書処理システム

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): JP US

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
NENP Non-entry into the national phase

Ref country code: JP