JP2005316699A - Content disclosure system, content disclosure method and content disclosure program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a content disclosure system or the like capable of realizing drastic man-hour reduction, increasing accuracy of information retrieval and increasing a scale of a retrieval range by supporting ontology construction by use of history information of daily work of a user to a content. <P>SOLUTION: This content disclosure system has content use history 01070 storing a history of operation of a plurality of users 01210, etc. on a network including a plurality of ontologies 01080, etc. including information defined by a set of items related to each other. A plurality of content clients 01010, etc. and a plurality of ontology manager computers 01130, etc. calculate similarity between documents from an item of a document produced, classified and retrieved by the users 01210, etc., or an ontology item, and a similar item including the ontology item to store it into a content use history storage 01070, and perform production, classification and retrieval of a new document on the basis of the similarity. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention improves the accuracy of information retrieval by constructing and associating single or multiple ontologies on a single computer or in multiple computer environments connected by a wired or wireless network. The present invention relates to a technique for expanding the search range. The present invention also relates to a technique for reducing man-hours for constructing ontology and associating a plurality of ontology.

  In a content management system such as an information disclosure server, mail server, document management, etc. using the Internet or an intranet, if the amount of content such as documents and data files as information sources becomes enormous, information required by users The effort to obtain it also increases. On the other hand, in order to obtain necessary information with little effort, the computer understands the technical terms in advance for each field of information that the user wants to use, and the relationships between terms such as higher-level concepts, lower-level concepts, aliases, and synonyms. A dictionary database is created as possible, and this dictionary database is used for information retrieval, extraction, and classification. Such a dictionary database and concept are generally called “ontologies”.

  However, the work of constructing the ontology as described above has been conventionally performed manually by experts in the field, and there is a problem that the number of work steps increases according to the number of words. Specifically, as a general dictionary construction method, manual processing is performed on a term set obtained by processing (morpheme analysis processing) that automatically takes a document in a specialized field and inputs it into a term. Unnecessary term removal and classification work was done.

  As a technique for supporting such ontology construction, for example, Patent Document 1 describes a method of using search history information of a user and setting a search term as a registration candidate in order to construct a single dictionary database (ontology). Has been.

  On the other hand, when various ontologies are constructed in various fields as well as the conventional ontology construction, these ontology groups are semantically combined to generate a new semantic network. Needs such as search that have been used are also born, and as a similar idea, technology development called “Semantic Web” is currently underway in the Internet field.

  As a technique for handling a plurality of ontologies, for example, Patent Document 2 discloses a method for providing a GUI (Graphical User Interface) for coupling two ontology nodes, and Patent Document 3 describes a plurality of ontology nodes. A method for realizing retrieval from a plurality of information servers by storing conversion rules between them is described. In the field of business support systems, the same concept is realized by an Enterprise Application Integration (EAI) system for data linkage between two databases, and GUIs and schemas such as connecting the schemas of each database with lines. This is realized by describing the conversion process between them.

Patent Document 4 describes a method for generating ontology correspondence information by calculating the similarity between a slot (node) of a certain ontology and another slot.
Japanese Patent Application No. 2003-025359 Japanese Patent Laid-Open No. 2001-14166 JP 2003-345821 A JP 2003-450502 A

  The task of constructing an ontology has been conventionally performed manually by experts in the field, and there is a problem that the number of work steps increases according to the number of words. In addition, in order to link a plurality of ontology, it is necessary to manually associate the ontology with each other, and there is a problem that the number of work man-hours increases according to the number of words, for example.

The present invention facilitates the construction of an ontology by profiling a user's document usage history in a system including at least a plurality of ontologies including information defined by a set of items having a relationship with each other on a network, for example. I decided to make it. Further, for example, in such a system, each computer harmonizes (integrates) ontology by calculating the similarity between documents from items of documents used by users or ontology items and similar items including ontology items. We decided to plan.

  Conventionally, a large number of man-hours have been required manually for constructing and associating a plurality of ontology. However, by implementing the present invention, a great reduction in man-hours can be realized. In addition, by supporting the construction using the history information of the user's daily work on the content, it is possible to realize a significant reduction in man-hours and to improve the accuracy of information search and to expand the size of the search range. There is. In addition, for example, by calculating the similarity between documents from document items or ontology items and similar items including ontology items, the relationship between each ontology can be easily confirmed, and correspondence between multiple ontologies There is an advantage that can be easily realized.

  In carrying out the present invention, one or a plurality of content management servers for managing documents, data files, etc. are arranged in a distributed environment on a network such as the Internet or an intranet, and a plurality of users manage contents. The form that can use the server is the best. Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

  FIG. 1 is an example of a content publishing system according to an embodiment of the present invention, and shows an arrangement of software, a data storage medium, and users on a computer network. Users 01210, 01220, 01225, and 01230 (hereinafter referred to as “user 01210...” As appropriate) are users who use this system, and are content clients 01010, 01020, 01025, and 01030 (hereinafter referred to as “content client 01010...” As appropriate). Is used. Administrators 01240, 01250, 01260 (hereinafter referred to as “administrator 01240...” As appropriate) are administrators who manage the system, and ontology management clients 01130, 01140, and 01150 (hereinafter referred to as “ontology management client 01130... As appropriate”), respectively. Is used. Content databases 01170, 01180, and 01190 (hereinafter referred to as “content database 01170...” As appropriate) are databases for storing content handled by the system. The content usage history 01070 is a database for storing a history input by the user 01210... Operating the content clients 01010. The standard format 01075 is a database that stores the format definition of a document used by the user 01210... To create a new document in the content client 01010. Ontologies 01080, 01090, and 01100 (hereinafter referred to as “ontology 01080...” As appropriate) are databases for storing a classification system for classifying content. Content servers 01040, 01050, and 0060 (hereinafter referred to as “content server 01024...” As appropriate) have management functions such as addition, deletion, and change to content, storage and reading functions for content usage history 01070, and reading functions for ontology 01080. This is a server provided to the clients 01010. The ontology management server 01110 is a server that provides the ontology management clients 01130... With a read function for the content usage history 01070 and a storage and read function for the ontology 01080. Here, ontology 01080 is a dictionary in which the computer can understand in advance the technical terms for each field of information that the user 01210... Wants to use and the relationship between terms such as higher concepts, lower concepts, aliases, and synonyms. Database and concept.

  There may be one or more content clients 01010, content servers 01040, content database 01170, ontology 01080, and ontology management client 01130. Further, the functions of the apparatus may be arbitrarily installed in various apparatuses or may be distributed and installed. The content clients 01010... Can be connected to one or more content servers 01040. The content server 01040 ... stores, manages, and displays electronic documents such as document files, electronically exchanged documents such as electronic bulletin boards and emails, and other documents having electronic forms, or a combination thereof. can do.

  In the case where the content client 01010... Stores the document created by the user 01210... Only in the client machine of the user 01210.

  FIG. 2 is an example of an item group in ontology 01080... In FIG. Ontology 01080... Is defined by a set of items 07060 to 07120 that are related to each other. The ontology item ID 07010 is an ID for uniquely identifying the items 07060 to 07120. Ontology item name 07020 is the name of item 0760-07120. The ontology item type 07030 is a name for identifying what kind of object the items 07060 to 07120 represent. For example, since the items 07060, 07070, 07080, 07090, and 07100 represent development processes in software development, the ontology item type 07030 is “process”. Since items 07110 and 07120 represent objects that exist as objects, ontology item type 07030 is “object”. In addition to “process” and “object”, the name of ontology item type 07030 can be defined and stored. The relationship ontology item ID 07040 is an ontology item ID 07010 of another item related to a certain item. The relationship 07050 is a name indicating the relationship between the item and the item indicated by the ontology item ID 07010. For example, since the item 07070 “design” and the item 07100 “test” are elements constituting the item 07060 “development procedure”, the relationship is “aggregation”. Further, since the item 07080 “basic design” and the item 07090 “detailed design” embody the item 07070 “design”, the relationship 07050 is “inclusion”. In addition to “aggregation” and “inclusion”, the name of the relation 07050 can be defined and stored.

  The ontology item type 07030 and the relationship 07050 may be IDs that uniquely identify the ontology item type 07030 and the relationship 07050, respectively.

  FIG. 3 is an example of the document classification / creation history in the content usage history 01070 of FIG. The document classification / creation history is stored when a document created in advance by the user 01210... Is classified on the content client 01010. Also stored when a user 01210... Creates a new document using the content client 01010. The document ID 02010 is an ID that uniquely identifies a document that has been classified or created. The document name 02020 is the title of the document. The creator 02030 is the name of the user 01210 that created the document. The creation date 02040 is the date and time when the document was created. The update date 02050 is the date and time when the document was last updated. Document content 02060 is the text of the document. The creator 02030 may be an ID that uniquely identifies the users 01210.

  FIG. 4 is an example of a document creation history in the content usage history 01070 of FIG. The document creation history is stored when the user 01210... Creates a new document using the content client 01010. The document ID 03010 is an ID for uniquely identifying a document, and the items 03050 and 03060 are uniquely identified. The same ID as the document ID 03010 in the document classification / creation history represents the same document. The document creation history represents an example of design document creation history in a software development project. The project name 03020 is the name of the project to which the design document belongs. The technology used 30030 is the name of the technology used in the software that is the design object of the design document. The development method 03040 is the name of the software development method that is the design target of the design document. The project name 03020, the used technology 03030, and the development method 03040 may be IDs that uniquely specify the project name, the used technology, and the development method, respectively. FIG. 4 shows an example in which items related to software development are stored. In the document creation history, items corresponding to the contents of the content handled by the content server 01040.

  FIG. 5 is an example of a document search history in the content usage history 01070 of FIG. The document search history is stored when a user 01210... Or administrator 01240... Of the system performs a search operation on the document group, words included in the document group, and ontology items 07060 to 07120 stored in the system. The search ID 04010 is an ID that uniquely identifies the search operation. The searcher 04020 is the name of the user 01210 that performed the search operation or the administrator 01240. The search date 04030 is the date and time when the search operation was performed. Search key 04040 is a key input in the search operation. The search key 04040 may be one of the document IDs 02010 as D-13-4952 in the search 04050. Moreover, one or more words may be sufficient like searches 04060, 04070, and 04080. Also, one of ontology IDs 07010 may be used as in searches 04090 and 04100. Here, the word may be a compound word formed by combining a plurality of words as well as a word which is a minimum unit of words, or a clause combining words, particles, conjunctions, and the like.

  FIG. 6 is an example of the document classification history in the content usage history 01070 of FIG. The document classification history is stored when a user 01210 of the system classifies a document according to ontology 01080. Here, the classification is to define a degree of relationship with a document for one or more items of ontology 01080. The document ID 05010 is an ID that uniquely identifies a document. When the document ID 05010 is the same as the document ID 022010 in the document classification / creation history, it indicates that the document is the same. The classifier 05020 is the name of the user 01210 that performed the classification. The classification date 05030 is the date and time when the classification is executed. The ontology item ID 05040 is an ID of an item of ontology 01080... In which the degree of relationship with the document is defined in the classification. The ontology item ID 05040 is the same as the ontology item ID 07010 in FIG. 2 in the ontology item group (the contents of any one item in the items 07060 to 07120 in FIG. 2 and the contents of any one item in the items 05060 and 05070 in FIG. 6). Represents the same ontology item. The distance 05050 is a numerical value representing the degree of relationship in classification. The smaller the value of the distance 05050, the higher the degree of relationship.

  FIG. 7 shows an example of the format definition of the document stored in the standard format 01075. The standard ID 06010 is an ID for uniquely identifying the format definition. The fixed name 06020 is a name of the format definition. An item name 06030 is a definition of an item input by the user 01210... When creating a new document. The item name 06030 includes an item ID, an item name, and an item type. For example, in the format definition 06060, the item IDs are “Project”, “Tech”, “Method”, and “Module”, and the item names corresponding to each item are “project name”, “used technology”, “development technique”, respectively. And “module ID”, and the types corresponding to each item are “character type”, “character string type”, “character string type”, and “alphanumeric type”, respectively. A text 06040 is a document file format definition used when a new document is created. For example, in the format definition 06060, the value input by the user 01210... Is embedded in the item “Project” in the item name 06030 in the “<Project />” portion of the body. Similarly, the values input by the user 01210... For the items “Tech”, “Method”, and “Module” are respectively “<Tech />”, “<Method />”, and “<Module />”. Embed in the part. In this way, a document file having a body that has been embedded is generated. FIG. 7 shows an example in which items related to software development are stored. In the format definition, items corresponding to the contents of content handled by the content server 01040.

  FIG. 8 is an example of the similarity in the content usage history 01070 in FIG. The similarity is calculated when the similarity between each document, each word, each user 01210..., And each ontology item is calculated by the system, or when the similarity is changed by the user 01210. Stored. The item ID 07510 is an ID of a document and ontology item. The similar item 07520 is a document, word, user 01210..., And ontology item similar to the item ID 07510, and can store an ID or a character string. The similarity degree 07530 is a similarity degree between the document or ontology item represented by the item ID 07510 and the document, word, user 01210..., Or ontology item represented by the similar item 07520.

  FIG. 9 shows an example of screen transition of the content clients 01010... In FIG. First, the user authentication screen 08010 is displayed, and the user 01210... Inputs authentication information such as a user ID and a password. Alternatively, if the content client 01010... Is installed on the client machine of the user 01210... Or the content client 01010. Authentication information may be entered in If it is recognized by the authentication information that there is an authority to use this system, the screen shifts to the client initial screen 08020. Thereafter, when an operation is performed on the document, the content usage history 01070 stores that the user 01210 corresponding to the user information input on the user authentication screen 08010 has performed the operation. In the client initial screen 08020, the screen is switched to a document classification screen 08030, a document search screen 08040, and a document creation screen 08050 by a screen switching operation. Further, the use authority of the users 01210... May be determined according to the user information input on the user authentication screen 08010, and the screen may not be changed to a screen without the use authority.

  FIG. 10 shows an example of screen transition of ontology management clients 01130... In FIG. First, the user authentication screen 08110 is displayed, and the administrator 01240... Inputs authentication information such as a user ID and a password. Alternatively, if the ontology management client 01130 is installed in the client machine of the administrator 01240, or if the ontology management client 01130 can acquire information that uniquely determines the usage manager 01240, the user authentication screen 08110 is not displayed. Thus, the authentication information may be automatically recognized. If it is recognized by the authentication information that there is an authority to use this system, the screen shifts to the client initial screen 08120. Thereafter, when an operation is performed on the ontology 01080..., The ontology 01080... Is stored as an operation performed by the user 01210 corresponding to the user information input on the user authentication screen 08110. Further, when an operation is performed on the document, the content usage history 01070 stores that the administrator 01240 corresponding to the user information input on the user authentication screen 08110 has performed the operation. In addition, in the client initial screen 08120, the screen is changed to a document search screen 08130 and an ontology item addition screen 08140 by a screen switching operation.

  FIG. 11 is a flowchart showing an example of a display algorithm of documents, words, users 01210..., And ontology items in the content clients 01010... And the ontology management client 01130. In the algorithm example, the similarity between each of the document, word, user, and ontology item is obtained, and according to the similarity, those with high similarity are in the vicinity and those with low similarity are on the screen in the distance. To place. Hereinafter, the contents of each item of the flowchart will be described.

  In S09010, the document name 02020, the creator 02030, the word group stored in the document content 02060 in the document classification / creation history (see FIG. 3), the project name 03020, the technology 03030 in the document creation history (see FIG. 4), In order to confirm whether or not there is a newly generated word among the word groups stored in the development method 03040, the system searches the document group. If there is a new word in the document group, the appearance frequency v1 of the word w1 in each document d is obtained in S09020. It is assumed that the higher the appearance frequency v1, the higher the similarity between the word w1 and the document d. In S09030, for each creation user u1 of each document d, the appearance frequency v1 as a result of S09020 is added to obtain v2. It is assumed that the larger the added value v2, the higher the similarity between the user u1 and the word w1.

  In S09040, the present system is used to confirm whether or not there are newly generated words and ontology items among the word groups and ontology item groups stored in the search key 04040 in the search history (see FIG. 5). Searches for documents. When there are new search words and ontology items in the search history, in S09050, the difference s1 between the times when each search word and ontology item w2 and each search word and ontology item w are stored is obtained. It is assumed that the similarity between the word and the ontology items w and w2 is higher as the time difference s1 is smaller. In S09060, the number of appearances of the word and ontology item w2 is added for each user and administrator u2, and the difference in time is s2. It is assumed that the greater the added value s2, the higher the degree of similarity between the user and the administrator u2 and the word or ontology item w2.

  In S09070, it is confirmed whether there is a new search document in the search history and a new classification document in the classification history. If there is a new search document in the search history and a new search document in the classification history, in S09080, the user or the administrator searches for or classifies the document on the screen of the content client 01010... Or ontology management client 01130. Then, the distance c1 between the arrangement position of the document d3 and the display position of each word and ontology item w is obtained. It is assumed that the similarity between the document d3 and the word or the ontology item w is higher as the distance c1 is smaller.

  In S09090, the distance c1 of the document d3 arranged by each user u3 is added to each word and ontology item w to be c2. It is assumed that the greater the added value c2, the higher the similarity between the user or administrator u3 and the word or ontology item w.

  In S09100, based on the results of S09020, S09030, S09050, S09060, S09080, and S09090 that have been obtained from the start of the system operation to the present, each document, each word, each user, and each ontology item are determined according to the degree of similarity. Arrange and display. That is, the similarity between each document, each word, each ontology item, and each user is obtained from v1, v2, s1, s2, c1, and c2, and those having similarities are close to each other and those having low similarity are similar to each other. Is placed on the screen at a distance. The similarity is stored as the similarity in the content usage history 01070. When calculating the similarity in S09020, S09030, S09050, S09060, S09080, and S09090, using the profile information of each user and each administrator, each ontology 01080 of each user or each administrator, and each word The degree of specialization may be obtained, and the degree of similarity may be multiplied by a weight. Here, the profile information is information such as the job type, department, project involved, and business theme of each user or each administrator. By using the profile information, it is considered whether the operation performed by the user 01210... Or the administrator 01240. The similarity can be obtained, and the reliability of the similarity is improved. In addition, when each document, each word, each user, and each ontology item is displayed on the content client 01010... And ontology management client 01130..., The user 01210. In this case, the values of the similarity may be increased for those that have become close to each other due to the arrangement change, and the value of the similarity may be decreased for those that have become distant due to the arrangement change. By using the arrangement change information, it is possible to obtain a degree of similarity more in line with the judgments of the users 01210... And the managers 01240. Further, when there is a risk of infringing on the privacy of each user and each administrator by providing the similarity to the users 01210... Or the manager 01240..., The similarity is not used when determining the arrangement. Also good. For example, since the search history of each user and each administrator includes private information such as keywords used by each user and each administrator for search, the similarity calculated using the search history is the ontology. Used by the management clients 01130... But not used by the content clients 01010.

  The calculation execution of S09020, S09030, S09050, S09060, S09080, and S09090 is performed at an appropriate timing so that the display process S09100 can be quickly performed in response to the operation of the user 01210. For example, it may be repeated at predetermined time intervals, while the load on the server machine on which the content server 01040... And ontology management server 01110 operates is low, or may be performed at a fixed time at night.

  By this algorithm, the user 01210... And the administrator 01240... Automatically operate each content client 01010... And ontology management client 01130... Automatically between each document, each word, each user, and each ontology item. Similarity can be derived, and man-hours for organizing documents are greatly reduced.

  A user authentication screen 10110 of FIG. 12 is an example of the user authentication screens 08010 and 08110 of FIG. 9 or FIG. 10, respectively. The user 01210 or the administrator 01240 inputs the user ID 10120 and the password 10130 and clicks the login button 10140. Alternatively, alternative means such as pressing the return key instead of clicking the login button 10140 may be used. If the authentication is successful after executing the user authentication process, the screen transitions to the client initial screen 08020 or 08120. If authentication fails, an error message is displayed. By clicking the clear button 10150, the character strings entered in the user ID 10120 and the password 10140 can be emptied. By authentication, it is possible to confirm whether the user 01210... Or the administrator 01240... Has the authority to use each function, and provide a function according to the authority. Further, by identifying the users 01210... Or managers 01240..., Information on the users 01210.

  13 is an example of initial screens 08020 and 08120 (see FIGS. 9 and 10) of the content clients 01010... And ontology management client 01130. In the window title 10010, a character string representing the content of the content targeted by the present system is displayed. The screen is composed of a left part and a right part. In the left part, a user 01210... Or a manager 01240... Inputs or selects a character string or displays document information. In the right part, each document, each word, each user 01210..., And each ontology item 07060-07110 are displayed. There are tabs in the left part and the right part, and the display target can be changed. In the initial screen example, the tab “search” 10015 is selected in the left part, and the tab “map” 10017 is selected in the right part (here, the tab “tree” 10018 displayed in a tree format, table The table format “10019” displayed in the format is not selected). In the right part, ontology item 10040 is displayed. Each ontology item is displayed by connecting related ontology items with a line 10050 in accordance with the related ontology item ID 07040 in the ontology 01080. Further, the similarity between each ontology item and each document, word, user 01210... Is obtained by the algorithm shown in FIG. 11, and if there are many items (document, word, user) having a high similarity, the ontology item is displayed in a large size. As a result, it is possible to give an overview of what items in the ontology 01080... In the left part, the tab “Search” 10015 is in a selected state, and a character string to be searched for is input to the search key input field 10020 and the search button 10030 is clicked to transit to the document search screen 08040 or 08130. be able to. In addition, for example, by dragging and dropping a document file to the right part, it is possible to transition to the document classification screen 08030. In addition, by clicking a tab “document creation” 10016, a transition to a document creation screen 08050 can be made. In addition, when the client is the ontology management client 01130..., The tab “property” 10013 can be clicked to transit to the ontology item addition screen 08140.

  Hereinafter, the layout of the window title, the left part of the screen, the right part of the screen, and the tabs are the same in the document classification screen 08030, the document search screens 80040, 08130, the document creation screen 08050, and the ontology item addition screen 08140 (FIG. 9, FIG. 9). 10).

  FIG. 14 is an example of the document classification screen 08030 (see FIG. 9) (here, the window title 11010 is selected by the tab “property” 11015 on the left side and the tab “map” 11017 on the right side as in FIG. Have been). For example, the document can be arranged on the screen by dragging the document “XX system basic design document” 11070 on the client machine to the right part of the screen. The similarity between the document and each document, each word, each user 01210..., And each ontology item is calculated, and the document, word, user 01210..., And ontology item having a high similarity are arranged in the vicinity of the document. The higher the value, the larger the display. The document “XX system agent design document” 11050 is an example of a document having a high similarity with the document 11070 dragged by the user 01210. The word “agent” 11100 is an example of a word having a high similarity to the document 11070 dragged by the user 01210. The user “* da * ro” 11090 is an example of the user 01210... Having a high similarity with the document 11070 dragged by the user 01210. The ontology item “prototyping” 11080 is an example of an ontology item having a high similarity with the document 11070 dragged by the user 01210. Every time the user 11010... Drags the document 11070 that is dragged and changes the arrangement, the similarity between the document 11070 and each document, each word, each user 01210..., And each ontology item changes according to the arrangement situation. However, the arrangement and size of the display change. When the user 11010... Drags the document 11070 being dragged, the position of the document 11070 in the right part of the screen is determined. The document information is stored in the document registration / creation history in the content usage history 01070. The position information is stored in the document classification history in the content usage history 01070. Even after the drop, the position can be changed by dragging the document 11070 again. Further, the position can be changed by dragging each document, each word, each user 01210..., And each ontology item. Each time the position change operation is performed, the similarity between the document 11070 and each document, each word, each user 01210..., And each ontology item changes, and the display arrangement and size change. The result of the change in similarity is stored in the similarity in the content usage history 01070. The display change makes it easy for the users 01210... To determine the layout position of the document, and information related to the document can be acquired.

  In the left part of the screen, information related to the contents of the document 11070 is displayed in the document information input area 11020. The information can be changed and reflected in the document 11070 by clicking the update button 11030. The reflection result is stored in the document registration / creation history in the content usage history 01070.

  According to the classification, not only the automatic calculation of the similarity in the example of the algorithm of FIG. 11 but also the similarity can be calculated reflecting the intention of the user 01210..., And the accuracy of the similarity is improved.

  FIG. 15 is an example in which the display format of the right portion of the screen in FIG. 14 is a tree format (here, the tab “property” 12015 is selected in the left portion of the window title 12010 as in FIG. 14). In each of the screens 08020, 08030, 08040, 08050, 08120, 08130, and 08140 excluding the login screen in the content client 01010... And the ontology management client 01130. Can be displayed in a format. Each ontology item 12040 is displayed in a hierarchical structure. The system agent design document 12050 is arranged and displayed at the position of similar ontology items. Agent 12060 is lined up with it. Further, when similar to a plurality of ontology items, they are arranged and displayed at a plurality of locations as 12070. Agent 12080 is lined up with it. The display in the tree format is effective when searching for information by tracing the hierarchy of ontology 01080. The document information input area 12020 and the update button 12030 are the same as those in FIG.

  FIG. 16 is an example in which the right portion of the screen in FIG. 14 is in a tabular format (here, the tab “property” 13015 is selected in the left portion of the window title 13010 as in FIGS. 14 and 15). By clicking the tab “table format” 13017 on the right part of the screen in each of the screens 08020, 08030, 08040, 08050, 08120, 08130 and 08140 excluding the login screen in the content client 01010... And the ontology management client 01130. You can transition to the format screen. A list of documents 13050 is displayed in ascending order or descending order of document names, ascending order of update date and time, or descending order. Also, by clicking on “document name” 13080, the document 13050 can be rearranged by switching between ascending / descending order by document name. In addition, by clicking “update date” 13090, the document 13050 can be rearranged by switching the ascending order / descending order by the update date 13070. The classification name 13060 displays an ontology item having a high degree of similarity with the document 13050. Display in tabular form is effective when it is desired to refer to documents sorted in a list. The document information input area 13020 and the update button 13030 are the same as those shown in FIGS.

  FIG. 17 is an example of the document search screens 08040 and 08130 in FIGS. 9 and 10. When a search condition is input or selected in the search character string input / selection field 14020 on the left part of the window title 14010 and a search button 14030 is clicked, the search is executed, and a document, a word, a user 01210. And the ontology item is enlarged and displayed (here, the tab “Search” 14015 is selected). Further, by clicking the document, word, user 01210..., And ontology item in the right part of the screen, the document, word, user 01210..., And ontology item similar to the clicked item are enlarged and displayed. Also, by dragging and dropping a document file on the client machine to the right part of the screen, documents, words, users 01210..., And ontology items similar to the document can be searched and enlarged and displayed. The display specification of the screen when the file is dragged and dropped is the same as that of the document classification screen 08030. The search history is stored in the document search history in the content usage history 01070 (see FIG. 1). By searching, not only can you get a list of documents that match your search criteria, you can also get related words, users 01210 ..., and ontology items, and know how they are related to each other Is very convenient. Also, documents, words, users 01210..., And ontology 01080... Can be dragged to move. In this case, the display specifications of the screen are the same as those of the document classification screen 08030.

  FIG. 18 is an example of the document creation screen 08050 of FIG. In accordance with the format definition stored in the fixed format 01075, a document format is selected in the left portion of the window title 15010 (here, the tab “Create text” 15015 is selected), and an input field 15020 for an item in the selected document format. Is displayed. When the user 01210... Selects a document format, inputs it into an item and clicks the “Create” button, a new document is created and placed in the right part of the screen (here, the tab “Map” 15017 is selected). To display. A document 15050 in the content usage history 01070 (see FIG. 1) is an example of a newly created document. The arrangement and display specifications of each document, each word, each user 01210..., And each ontology item (system engineering knowledge system 15040, etc.) similar to the newly created document are the same as in the document classification screen 08030. By creating a document on the document creation screen, a standard document can be easily created, which is very convenient. In addition, since the word acquisition and search of each item of the standard document can be used for the search, the search accuracy is improved.

  FIG. 19 is an example of the ontology item addition screen 08140 of FIG. When information on an ontology item is entered in the ontology item information input field 16020 in the left part of the window title 16010 (here, the tab “property” 16015 is selected) and the “update” button 16030 is clicked, the right part (here, Add an ontology item to the tab “Map” 16017) and place and display it. When the displayed word is clicked, the word name is automatically input to the category name in the ontology item information input field 16020. When information other than the category name is input and the “update” button 16030 is clicked, a word is added as an ontology item (system engineering system 16040 or the like), and is arranged and displayed. By adding the ontology, words and the like generated by daily document operations of the users 01210... Can be reflected in the ontology 01080. Also, documents, words, users 01210..., And ontology 01080... Can be dragged to move. In this case, the display specifications of the screen are the same as those of the document classification screen 08030.

  When the administrator 01240 currently using the ontology management client 01130... And another administrator 01240... Associate the same ontology item with different ontology items, the relationship line is a normal relationship line. Different line types are displayed. 16090 and 16100 are examples of different line types. As a result, a plurality of managers 01240 can easily add and modify ontology items, and can find out inconsistencies among managers 01240, which is very convenient.

  By implementing the present invention, it is possible to easily connect the nodes of a plurality of ontology 01080.

  As a result, in the implementation within one company, when sharing information in the company with a document management system as a core, a plurality of ontology 01080... A business support system that outputs search results can be realized.

  As a specific example, in document management in a software development company, when a new document is classified for a plurality of ontologies 01080... Such as a development classification system for each customer, a system development knowledge system, etc., or an existing document is searched. It can be used for user support. Further, in the case of a document in a plant engineering company, it can be used for user support when classifying a new document or searching for an existing document for a plurality of ontology 01080... Such as a plant system, a system system, and an equipment system.

  On the other hand, in an implementation related to a plurality of companies and stakeholders, not only a single ontology but also a plurality of ontologies 01080 are used when an end user uses any search service for one or a plurality of Internet information disclosure servers. It becomes possible to realize a service that outputs a wide range of search results by semantically combining. For example, it is possible to realize a service that provides a GUI that links a plurality of ontology 01080... And a content search service on the Internet such as Google (R) using the service.

1 is a block diagram of a content publishing system according to an embodiment of the present invention. It is a figure which shows the example of the item group in the ontology which concerns on one Embodiment of this invention. It is a figure which shows the example of the document classification | category / creation log | history of a content utilization log | history which concerns on one Embodiment of this invention. It is a figure which shows the example of the document creation log | history of the content utilization log | history which concerns on one Embodiment of this invention. It is a figure which shows the example of the document search history of the content utilization history which concerns on one Embodiment of this invention. It is a figure which shows the example of the document classification | category log | history of the content utilization log | history which concerns on one Embodiment of this invention. It is a figure which shows the example of the format definition of the document stored in the fixed format which concerns on one Embodiment of this invention. It is a figure which shows the example of the similarity in the content utilization log | history which concerns on one Embodiment of this invention. It is a figure which shows the example of the screen transition of the content client which concerns on one Embodiment of this invention. It is a figure which shows the example of the screen transition of the ontology management client which concerns on one Embodiment of this invention. 6 is a flowchart illustrating an example of a display algorithm of a document, a word, a user, and an ontology item in a content client and an ontology management client according to an embodiment of the present invention. It is a figure which shows the example of the user authentication screen which concerns on one Embodiment of this invention. It is an example of the initial screen of the content client which concerns on one Embodiment of this invention, and an ontology management client. It is a figure which shows the example of the document classification screen of the content client which concerns on one Embodiment of this invention. It is a figure which shows the example which represented the document classification screen of the content client which concerns on one Embodiment of this invention in the tree format. It is a figure which shows the example which represented the document classification screen of the content client which concerns on one Embodiment of this invention with a table format. It is a figure which shows the example of the document search screen of the content client which concerns on one Embodiment of this invention. It is a figure which shows the example of the document creation screen of the ontology management client which concerns on one Embodiment of this invention. It is a figure which shows the example of the ontology item addition screen of the ontology management client which concerns on one Embodiment of this invention.

Explanation of symbols

01010, 01020, 01025, 01030 Content client 01070 Content usage history 01080, 01090, 01100 Ontology 01130, 01140, 01150 Ontology management client 01210, 01220, 01225, 01230 User 01240, 01250, 01260 Administrator

Claims (21)

In a content publishing system comprising at least a user computer, a plurality of ontologies including information defined by a set of items related to each other, and an ontology manager computer,
A content usage history storage means for storing a history operated by the user is provided,
The user computer and the ontology manager computer calculate the similarity between documents from the items of the document created, classified, or searched by the user, or ontology items and similar items including the ontology items, and use of the content A content publishing system characterized in that it is stored in history storage means and performs at least one of creation, classification, and search of a new document based on the similarity. The content usage history storage means includes:
The content publishing system according to claim 1, wherein a history of creation, classification, and search performed by a user is stored. The content disclosure system according to claim 1, wherein the ontology is linked based on the similarity. The content publication system according to claim 3, wherein the document item and the ontology item are arranged on the screens of the user computer and the ontology manager computer based on the similarity. The content publishing system according to claim 4, wherein the item of the document having a high similarity and the ontology item are arranged close to each other, and the item of the document having a low similarity and the ontology item are arranged far away. The content disclosure system according to claim 4, wherein the related ontology items are connected by a line. The content disclosure system according to claim 6, wherein when different ontology manager computers connect the same ontology items with a line, the ontology items are connected with a line different from the line. The content publication system according to any one of claims 4 to 7, wherein the size of the item of the document and the ontology item changes based on the similarity. 9. The content publishing system according to claim 8, wherein items of the document with a high similarity are displayed in a large size and items of the document with a low similarity are displayed in a small size. The content publishing system according to claim 4, wherein the similarity is changed by changing a position on the screen of the item of the document. In a content publishing method using at least a user computer, a plurality of ontologies including information defined by a set of items having relations with each other, a content usage history storage means for storing a document, and an ontology manager computer,
The history operated by the user is stored in the content usage history storage means, and the user computer and the ontology manager computer include document items created by the user, classified, or searched, or ontology items and ontology items. Content publishing characterized in that similarity between documents is calculated from similar items, stored in the content use storage means, and at least one of creation, classification and search of a new document based on the similarity Method. The content usage history storage means includes:
The content publishing method according to claim 11, wherein a history of creation, classification, and search performed by a user is stored. The content disclosure method according to claim 11, wherein the ontology is linked based on the similarity. The content publication method according to claim 13, wherein the document item and the ontology item are arranged on the screens of the user computer and the ontology manager computer based on the similarity. The content publishing method according to claim 14, wherein the document item having a high similarity and the ontology item are arranged close to each other, and the document item having a low similarity and the ontology item are arranged far away. The content disclosure method according to claim 14, wherein the related ontology items are connected by a line. The content disclosure method according to claim 16, wherein when different ontology manager computers connect the same ontology items with a line, the ontology items are connected with a line different from the line. The content publication method according to any one of claims 14 to 17, wherein the size of the item of the document and the ontology item changes based on the similarity. 19. The content publishing method according to claim 18, wherein the document item with a high similarity is displayed in a large size and the item of the document with a low similarity is displayed in a small size. The content publishing method according to claim 14, wherein the similarity is changed by changing a position on the screen of the item of the document. A content publishing program that causes a computer to execute the content publishing method according to any one of claims 11 to 20.

Images