JP2005141691A - Schema extension system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To correctly extend a schema, based on a schema or metadata in existence. <P>SOLUTION: A control part 22 of a user device 2A computes the total number of pieces of returned metadata, if the total number is equal to or above a first threshold level (for instance, 3) stored previously in the part, transmits, to a schema management device 1, a property value 'Chinese noodle shop' and a property 'last order time', and makes a request (steps 39, 41) for provisionally register a property definition indicating that 'last order time' is applicable as the property of an instance of the conceptual class ' Chinese noodle shop'. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a schema extension system that extends a schema for managing metadata holding information.

  In the past, the concept common to multiple resources was defined for the purpose of defining metadata consisting of resource URIs (Uniform Resource Identifiers), resource attribute names (hereinafter referred to as properties), and property values (attribute values). A schema configured by accumulating RDF (Resource Description Framework) statements including a concept class to be shown and properties shared by the plurality of resources is used.

  The schema defines the vocabulary used in metadata. Specifically, what kind of concept class exists (definition of the concept class), what kind of properties, what kind of subject and Defines whether an object (property value) can be taken (property definition). In other words, candidate subjects and objects are represented by concept classes. In the RDF statement of metadata, an instance of the concept class is associated with a defined property.

  The metadata is used for various information provision and information retrieval in a computer system represented by the Internet.

  For example, the related art is disclosed in Patent Document 1 below. In this document, metadata is described as context data.

RDF is described in Non-Patent Documents 1 and 2.
JP 2002-251311 A "Resource Description Framework (RDF) Model and Syntax Specification", Ora Lassia, Ralph R. Swick, [online], Internet <URL: http://www.w3.org/TR/1999/REC-rdf-syntax- 19990222 /> "RDF Vocabulary Description Language 1.0: RDF Schema", Dan Brickley, RVGuha, [online], Internet <URL: http://www.w3.org/TR/rdf-schema/>

  By the way, when it becomes necessary to extend the schema for defining metadata as described above, an RDF statement including a new property is added to the schema.

  An RDF sentence is added by a schema administrator or the like operating a computer that stores the schema. Therefore, the schema may not be extended correctly due to an operation error. For example, an unnecessary RDF sentence may or may not be added.

  Further, a schema administrator or the like extends the schema by predicting metadata that will be required in the future regardless of the schema and metadata actually stored in the computer. For this reason, the expanded portion may actually be unnecessary for metadata management.

  Accordingly, the present invention has been made in view of the above-described conventional problems, and an object of the present invention is to provide a schema extension system that can correctly extend a schema based on an existing schema or metadata.

  In order to solve the above-described conventional problems, in the present invention, a schema extension system configured by a computer generates metadata including the same resource URI and the same property from the metadata accumulated in the storage unit of the computer. Search, calculate the total number of the searched metadata, and include the same concept class and the property when it is determined that the calculated total number is equal to or greater than a pre-stored threshold value Extend the schema by adding statements to the schema.

  Further, a schema extension system configured by a computer uses a resource other than a specific resource URI among resource URIs of a plurality of resources having a concept indicated by the same concept class from metadata accumulated in a storage unit of the computer. When the metadata including the URI and the same property is searched, the total number of the searched metadata is calculated, and when it is determined that the calculated total number is equal to or greater than a threshold value stored in advance, Extend the schema by adding a statement containing the same concept class and the property to the schema.

  Further, a schema extension system configured by a computer includes a meta data including any one of resource URIs of a plurality of resources having the concept indicated by the same concept class and the same property from the metadata accumulated in the storage unit of the computer. When the data is searched, the total number of the searched metadata is calculated, and it is determined that the calculated total number is equal to or greater than a threshold value stored in advance, the same concept class and the property The schema is extended by adding a statement containing

  In addition, a schema extension system configured by a computer searches a schema stored in a storage unit of the computer for a schema part including a plurality of concept classes under the same concept class, and is identical to the schema part. When it is determined that the property is included, the schema is extended by adding a statement including the same concept class and the same property to the schema.

  According to the present invention, since the schema is extended based on the existing schema and metadata, the schema can be correctly extended.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram showing the configuration of a computer system to which the present invention is applied.

  The schema management device 1 stores a schema configured by accumulating RDF statements including a concept class indicating a concept common to a plurality of resources and a property common to the plurality of resources, and stores the schema. A computer configured to be updated as appropriate. In the present embodiment, an existing ramen shop named “Menmendo”, other ramen shops, existing Chinese restaurants, restaurants, stores, and the like will be described as examples of resources.

  The user devices 2A, 2B, and 2C are computers used for the users A, B, and C, respectively, and are based on a resource URI that is a URI of one resource, a resource property (attribute name), and a property value (attribute value). And the metadata is appropriately displayed and updated.

  The schema management device 1 can communicate with the user devices 2A, 2B, and 2C via the Internet (not shown), and the user devices can communicate with each other in the same manner.

  FIG. 2 is a directed labeled graph showing a part of the schema managed by the schema management apparatus 1. In the diagram described in the present embodiment, the namespaces of rdf and rdfs correspond to vocabularies defined in RDF and RDF Schema shown in Non-Patent Documents 1 and 2, respectively.

  Now, the concept classes in the schema will be described with reference to FIG. For example, when the character string “ramen restaurant” is used for the concept class, the character string “ramen restaurant” is not only the concept class. This is because there are other computer systems as in the present embodiment, and the character string “ramen restaurant” can be used as a concept class there. Therefore, an address related to the company that employs the computer system of the present embodiment is given before the character string “Ramen shop” (for example, http://www.ntt.co.jp/schema#Ramen shop) It is a concept class. In the following description, for example, a concept class including the character string “ramen restaurant” is expressed as a concept class “ramen restaurant”, but the concept class may be unique so long as it does not overlap with other concept classes.

  As shown in FIG. 2, an arrow with a label rdfs: subClassOf extends from a concept class managed by the schema management apparatus 1 to a concept class higher than the concept class. For example, the concept class “Chinese restaurant” is a higher concept than the concept class “Ramen restaurant”.

  Further, the property at the base of the arrow of the label rdfs: domain and the concept class at the end of the arrow are managed in the same RDF statement. Specifically, for example, an RDF sentence including a concept class “ramen restaurant” and a property “noodle type” is stored. This RDF sentence indicates that the target for applying the property “noodle type” is the concept class “ramen restaurant”.

  The concept class at the end of the arrow of the label rdfs: range is managed in the same RDF statement as the property at the base of the arrow. Specifically, for example, an RDF sentence including a concept class “time” and a property “business start time” is stored. This RDF statement defines that an instance of the concept class “time” should be described in the metadata as a property value of the property “business start time”.

  Returning to FIG.

  The user devices 2A, 2B, and 2C each store a metadata management unit 21 that stores and manages metadata including a resource URI of a resource, a property of the resource, and a property value, and registration of new metadata and schema extension. Therefore, a control unit 22 that performs processing and a display unit 23 that displays schema and metadata are provided.

  The control unit 22 interprets the graphic data and displays the graphic data on the display unit 23. The main control unit generates graphic data for displaying an area for display contents and data input. And a GUI (Graphic User Interface) unit that returns data input to the main control unit, and the main control unit performs various controls based on the returned data.

  FIG. 3 is a directed graph with a label indicating metadata stored in the metadata management unit 21 of the user device 2A.

  In FIG. 3, what is represented by URI is indicated by an ellipse. That is, the resource URI in the metadata managed by the metadata management unit 21 of the user device 2A is represented by the URI for the same reason as the concept class described above. In the following description, for example, a resource URI including the store name “Menmendo” is represented as a resource URI “Menmendo”, but if the resource URI is unique and does not overlap with other resource URIs, Good.

  Further, in the metadata managed by the metadata management unit 21, a URI including a character string “ramen restaurant” is used as a property value. In the following description, a URI including this character string “ramen restaurant” is expressed as a property value “ramen restaurant”.

  On the other hand, property values composed only of character strings such as “Menmendo” and “Mitaka City in Tokyo” are also used. Such property values are indicated by rectangles in FIG. In the following description, such a property value is also expressed as a property value “Menmendo” or a property value “Mitaka-shi, Tokyo ...”.

  The property is composed of a URI including, for example, a character string (such as “store name”). The property may be a unique property that does not overlap with other properties. In the following description, the property is expressed as a property “store name”, for example.

  Note that such notation in the drawings and description also applies to the metadata of the user device 2B and the user device 2C.

  Now, as shown in FIG. 3, the labeled arrow of the property of the URI extends from the resource URI “Menendo” of the metadata stored in the metadata management unit 21 of the user apparatus 2A to the property value of the property. ing.

  That is, the metadata management unit 21 of the user apparatus 2A includes metadata including a resource URI “menmendo”, a property “rdf: type”, and a property value “ramen restaurant”, a resource URI “menmendo”, and a property. Metadata consisting of “store name” and property value “Menmendo”, metadata consisting of resource URI “Menmendo”, property “phone number” and property value “03-xxxx-xxxx”, resource URI “Men” Stores metadata including “Mendo”, a property “address”, and a property value “Mitaka City, Tokyo ...”.

  On the other hand, although not shown, the metadata management unit 21 of the user device 2B stores metadata including a resource URI “Menmendo”, a property “business start time”, and a property value “10:00”. .

  Although not shown, the metadata management unit 21 of the user apparatus 2C stores metadata including “menmendou”, a property “business end time”, and a property value “23:00”.

  The metadata management unit 21 and the control unit 22 function when a computer control element (so-called CPU) reads and writes data stored in a storage device (such as a hard disk device or a semiconductor memory).

  Next, the operation of the present embodiment will be described.

  FIG. 4 is a sequence diagram when newly registering metadata including the last order time of Menmendou.

  When the user A performs a predetermined operation on the user device 2A, the control unit 22 of the user device 2A acquires the schema from the schema management device 1, and for example, a plurality of concepts including the concept class “restaurant” illustrated in FIG. When the class is pulled down on the display unit 23 and the concept class “Restaurant” is selected, a plurality of subordinate concept classes are displayed in the same manner, and the concept class “Chinese restaurant” is displayed. When selected, a plurality of subordinate concept classes are displayed in the same manner.

  Then, when one of the displayed concept classes (for example, the concept class “ramen shop”) is selected, the control unit 22 is a concept class higher than the selected concept class from the schema management device 1. The properties (for example, the property “store name”, the property “phone number”, and the property “address”) of the concept class that does not depend on the type of business (for example, the concept class “store”) are acquired and selected as shown in FIG. The concept class and each acquired property are displayed on the display unit 23, and an area for inputting a property value corresponding to each displayed property as a keyword for metadata search is displayed.

  On the other hand, when the user A tries to register information from the telephone number of the store and performs a predetermined operation on the user apparatus 2A, the control unit 22 searches the display unit 23 for the metadata of the telephone number as shown in FIG. Displays an area for inputting as a keyword.

  When the user apparatus 2A enters the store, the control unit 22 displays the store name as a metadata search keyword in cooperation with GPS (Global Posisioning System) as shown in FIG. Also good.

  In the user apparatus 2A, the user A inputs a keyword in the area displayed as shown in FIG. 6 or FIG. 7, or instructs the keyword displayed as shown in FIG. 8 (step S1).

  Hereinafter, a keyword that is input or designated is simply referred to as a keyword. Further, an example will be described in which “Menmendo” input in the area corresponding to the property “Store Name” displayed as shown in FIG. 6 is a keyword.

  The control unit 22 of the user device 2A gives the keyword “Menendo” to its metadata management unit 21 and requests metadata related to the keyword. Further, the metadata management unit 21 of the user device 2A requests the metadata management unit 21 of the user devices 2B and 2C to similarly search for metadata (step S3).

  Each metadata management unit 21 searches the metadata managed by itself for metadata including the given keyword “menmendou” as a property value, and the resource URI “menmendo” in the retrieved metadata. "Is further searched from metadata managed by itself (step S5).

  The metadata management unit 21 of the user device 2A returns directly to the control unit 22 and the metadata management unit 21 of the user devices 2B and 2C returns the retrieved metadata to the control unit 22 via the metadata management unit 21 of the user device 2A. (Step S7).

  In this example, the metadata shown in FIG. 3 is returned from the metadata management unit 21 of the user device 2A.

  Next, the control unit 22 of the user apparatus 2A transmits the property value “ramen shop” of the metadata including the property “rdf: type” to the schema management apparatus 1 and requests a schema search (step S9).

  The schema management device 1 searches the schema stored by itself for a portion including the same concept class “ramen restaurant” as the transmitted property value “ramen restaurant” (step S11), and uses the retrieved schema as the user device 2A. To the controller 22 (step S13).

  In this example, the concept class “ramen restaurant”, the concept class “noodle type” that is a property of the instance of this concept class “ramen restaurant”, and the concept class “Chinese restaurant” that is a higher class of this concept class “ramen restaurant”. ”, Its higher concept class“ restaurant ”, the properties“ business start time ”and“ business end time ”of instances of this concept class“ restaurant ”, its higher concept class“ store ”, and this concept The part of the schema that includes the properties “Store Name”, “Address”, and “Telephone Number” of the instance of the class “Store” and the conceptual class “Time” in which the properties “Business Start Time” and “Business End Time” are the instance properties Search for and return.

  The control unit 22 of the user device 2A searches the returned schema for a property corresponding to one or more upper concepts for the concept class “ramen restaurant”. In this example, the properties “business start time” and “business end time” are searched.

  The control unit 22 of the user device 2A requests the metadata by giving the resource URI “Menmendo” and the properties “business start time” and “business end time” to its metadata management unit 21. The metadata management unit 21 of the user device 2A similarly requests metadata from the metadata management unit 21 of the user devices 2B and 2C (step S15).

  Each metadata management unit 21 searches for metadata including “menmendou” and each property from metadata managed by the metadata management unit 21 (step S17).

  The metadata management unit 21 of the user device 2A returns the metadata retrieved by itself to the control unit 22 via the metadata management unit 21 of the user device 2A and the user device 2B and 2C metadata management unit 21 directly. (Step S19).

  In this example, the metadata management unit 21 of the user device 2B returns metadata including the resource URI “Menmendo”, the property “business start time”, and the property value “10:00”, and the user device 2C. The metadata management unit 21 returns metadata including the resource URI “menmendou”, the property “business end time”, and the property value “23:00”.

  The control unit 22 of the user device 2A causes the display unit 23 to display the concept class included in the returned schema and the property value included in the returned metadata (step S21).

  FIG. 9 is a diagram showing the contents displayed on the display unit 23.

  As shown in FIG. 9, first, the concept class “ramen restaurant” is displayed.

  Below that, property values “Menmendo”, “03-xxxx-xxxx”, and “Mitaka City, Tokyo ...” for the resource URI “Menmendo”, which are instances of this concept class “Ramen shop”. Is displayed.

  Here, the reason why the areas for input described below are not displayed in association with the property values is that these property values are returned from the metadata management unit 21 of the user device 2A itself, and the user device 2A itself. This is because only the metadata including the property value recognized as correct by the user is stored in the metadata management unit 21.

  Under the property value “Menendo” etc., the property “business start time” included in the returned schema and the property value “10:00” which is an instance of this property, that is, the user device 2B The property values returned from the metadata management unit 21 are displayed in association with each other. The property value “10:00” is displayed in the property value input area and can be rewritten.

  Further, the property “business end time” included in the schema is associated with the property value “23:00” which is an instance of this property, that is, the property value returned from the metadata management unit 21 of the user device 2C. Display in the same way.

  Furthermore, a property “noodle type” included in the returned schema is displayed below, and an area for inputting a property value that is an instance of this property is displayed in association with this concept. In this case, since the metadata including the property value corresponding to the property “noodle type” has not been returned, the area is blank.

  Note that the property “noodle type” is displayed below the property “business start time”, etc., in the returned schema than the concept class “ramen shop” that has the property “noodle type”. This is because the concept class “restaurant” having “business start time” is higher.

  In the display in step S21, a set of an area for inputting a new property and an area for inputting a property value that is an instance of this property is displayed. Since a plurality of such sets are displayed, a plurality of new property / property value sets can be input.

  In step S21, a check box is displayed in association with the property included in the returned schema and the area for inputting a new property. The check box is checked by the user when the property value displayed or input corresponding to the check box is correct.

  As shown in FIG. 8, when the user apparatus 2A is brought into the store, “Menmendo” is displayed, and when the store name is designated, “Menmendo” is entered as a keyword in FIG. The processing is performed in the same manner as in the above case.

  Further, as shown in FIG. 7, when “03-xxxx-xxxx” is input in the area for inputting a keyword for metadata search, when “03-xxxx-xxxx” is input in FIG. The process is performed in the same manner as. The display results in these cases are the same as in this example.

  In the display as shown in FIG. 9, for example, a new property “last order time” is input in an area for inputting a new property, and a property value “22” is input in an area for inputting a property value that is an instance of this property. : 30 ”is input, and a check box corresponding to the properties“ business start time ”and“ business start time ”and a check box corresponding to the new property“ last order time ”are checked.

  The control unit 22 of the user device 2A gives the metadata including the checked property value to its own metadata management unit 21 (step S23), and the metadata management unit 21 newly adds the given metadata to itself. (Step S25). Therefore, only what is recognized as correct by the user A of the user device 2A is stored in the metadata management unit 21.

  FIG. 10 is a directed graph with labels showing the metadata stored in the user device 2A after step S23.

  In addition to the metadata shown in FIG. 3, the metadata management unit 21 of the user apparatus 2A includes metadata including a resource URI “menmendou”, a property “business start time”, and a property value “10:00”; Metadata consisting of the resource URI “menmendo”, the property “business end time” and the property value “23:00”, the resource URI “menmendo”, the property “last order time” and the property value “22:30” And new metadata is stored.

  If the display in step S21 is as shown in FIG. 11, the user A has the property “impression” and the property value “gyoza set was good”, the property “discount information” and the property value “http: //”. /Aaa.co.jp / ... "(http: //aaa.co.jp / ... is the URI of the homepage from which discount information can be obtained), property" business start time ", property" business end time ", property When the check boxes of “last order time”, property “impression”, and property “discount information” are checked, metadata as shown in FIG. 12 is stored in the metadata management unit 21 of the user apparatus 2A.

  Next, in the present embodiment, processing for extending the schema stored in the schema management apparatus 1 with conditions is performed. For convenience, the process in the case of extending the schema with the property “last order time” will be described, but the same process is performed for other properties.

  13 and 14 are sequence diagrams when the schema of the schema management apparatus 1 is extended by the user apparatus 2A.

  As illustrated in FIG. 13, the control unit 22 of the user device 2A requests metadata including the property “last order time” from its own metadata management unit 21 (step S31).

  The metadata management unit 21 of the user apparatus 2A includes, for example, a resource URI “Menendo”, a property “Last Order Time”, and a property value “22:30” as metadata including the property “Last Order Time”. The metadata is searched, the metadata including the resource URI “Menendo” and the property “rdf: type” of the metadata is searched and returned to the control unit 22 (step S33).

  The control unit 22 of the user device 2 </ b> A requests metadata including the resource URI “Menmendo” and the property “Last Order Time” from its own metadata management unit 21. Further, the metadata management unit 21 of the user device 2A similarly requests the metadata from the metadata management unit 21 of the user devices 2B and 2C (step S35).

  The metadata management unit 21 of the user device 2A searches for and returns the metadata directly, and the metadata management unit 21 of the user devices 2B and 2C retrieves the metadata via the metadata management unit 21 of the user device 2A (step S37). ).

  If the control unit 22 of the user device 2A calculates the total number of returned metadata and determines that the total number is equal to or greater than a first threshold value (for example, “3”) stored in itself, the schema The property value “ramen restaurant” and the property “last order time” are transmitted to the management apparatus 1 to request registration as a temporary property (steps S39 and S41).

  As illustrated in FIG. 15, the schema management device 1 adds an RDF sentence including a concept class “ramen shop” equal to the transmitted property value “ramen shop” and the transmitted property “last order time” to the schema. (Step S43). The schema management apparatus 1 performs processing so that the property “last order time” becomes a temporary property.

  Next, the control unit 22 of the user apparatus 2A gives the resource URI “menmendo”, the property value “ramen restaurant”, and the property “last order time” to the metadata management unit 21 of the user apparatus 2A, and the resource URI is Request a metadata search that is not "menmendou". Further, the metadata management unit 21 of the user device 2A similarly requests a metadata search from the metadata management unit 21 of the user devices 2B and 2C (step S45).

  Each metadata management unit 21 searches for metadata including a URI of a resource whose resource URI is not “Menmendo” and a property value “Ramen shop”, and is a resource URI in the searched metadata. The metadata including the URI of the ramen shop other than the nendo and the property “last order time” is searched (step S47).

  The metadata management unit 21 of the user device 2A is directly connected and the metadata management unit 21 of the user devices 2B and 2C is searched via the metadata management unit 21 of the user device 2A (a ramen shop other than noodle hall). ) And the metadata including the property “last order time” are returned (step S49).

  If the control unit 22 of the user device 2A calculates the total number of returned metadata and determines that the total number is equal to or greater than a second threshold value (for example, “3”) stored in advance in itself. Then, the property value “ramen restaurant” and the property “last order time” are transmitted to the schema management device 1 to request registration as an official property (steps S51 and S53).

  As illustrated in FIG. 16, the schema management device 1 adds an RDF sentence including a concept class “ramen restaurant” equal to the transmitted property value “ramen restaurant” and the transmitted property “last order time” to the schema. (Step S55). The schema management apparatus 1 performs processing so that the property “last order time” becomes an official property.

  Next, the control unit 22 of the user device 2A calculates the total number of the total number obtained in step S39 and the total number obtained in step S47, and the total number obtained thereby is stored in the control unit 22 in advance. If it is determined that the value is equal to or greater than the stored third threshold value (for example, “10”), the property value “ramen restaurant” and the property “last order time” are transmitted to the schema management device 1, Registration as a temporary property is requested (steps S61 and S63).

  As illustrated in FIG. 17, the schema management device 1 searches for a concept class “Chinese restaurant” that is one level higher than the concept class “ramen restaurant” that is equal to the transmitted property value “ramen restaurant”. An RDF sentence including the class “Chinese restaurant” and the transmitted property “last order time” is added to the schema (step S65). The schema management apparatus 1 performs processing so that the property “last order time” becomes a temporary property.

  Next, as illustrated in FIG. 14, the control unit 22 of the user device 2 </ b> A transmits the property value “ramen restaurant” to the schema management device 1 to request a schema (step S <b> 71).

  As illustrated in FIG. 18, the schema management device 1 searches the conceptual class “Chinese restaurant” that is one level higher than the conceptual class “ramen restaurant” using the transmitted property value “ramen restaurant” as a conceptual class, The concept class “Dim Sum” that is one level below the concept class “Chinese restaurant” and the properties of this concept, and the concept class “Ramen restaurant” that is one level below the concept class “Chinese restaurant” and the properties of this concept The schema part consisting of is searched (step S73). Then, the retrieved schema is returned to the control unit 22 (step S75).

  The concept class “ramen restaurant” and the concept class “Dim Sum” are concepts having the concept class “Chinese restaurant” as parents, that is, concepts corresponding to siblings.

  The control unit 22 of the user apparatus 2A selects a property of one concept class in the returned schema, for example, the property “last order time” of the concept class “Ramen shop”, and also sets the property “last” to the other one concept class. If there is an “order time”, the property value “ramen shop” and the property “last order time” are transmitted to the schema management apparatus 1 to request registration as a temporary property of a higher concept class (steps S 77 and 79). ).

  As illustrated in FIG. 19, the schema management device 1 searches for a concept class “Chinese restaurant” that is one level higher than the concept class “ramen restaurant” that is equal to the transmitted property value “ramen restaurant”, and the searched concept. An RDF sentence including the class “Chinese restaurant” and the transmitted property “last order time” is added to the schema (step S81). The schema management apparatus 1 performs processing so that the property “last order time” becomes a temporary property.

  By the way, the schema can be extended only by the schema management device 1. For example, the schema management device 1 searches for a concept class “Chinese restaurant” that is one level higher than the concept class “Ramen restaurant” having the property “last order time”, and is one level lower than the concept class “Chinese restaurant”. For example, “Dim Sum”. If the concept class “Dim Sum” has the property “Last Order Time”, the property “Last Order Time” is set as the “temporary” property for the concept class “Chinese Restaurant”.

  By extending the schema as described above, as shown in FIG. 20A, the property “last order time” added later than the property “noodle type” of the conceptual class “ramen shop” in the schema. "Can be displayed above.

  In the present embodiment, as shown in FIG. 20B, the metadata managed by the user devices 2A, 2B, and 2C can be displayed together on one user device.

  As is clear from the above description, the computer system of FIG. 1 corresponds to a schema extension system. In this schema extension system, as a schema extension method, in step S37, the resource URI “Menendo” of a specific resource having the concept indicated by the concept class “ramen shop” which is the same concept class from the accumulated metadata. ”And the same property“ last order time ”are searched, the total number of the searched metadata is calculated in step S39, and the calculated first total threshold is stored in advance. If the value is greater than or equal to the value, in step S43, the schema is extended by adding a sentence including the same concept class “ramen shop” and the property “last order time” to the schema. As a result, the schema can be correctly extended based on the existing metadata.

  Further, the schema extension system, as a schema extension method, in step S47, the specific resource URI among the resource URIs of a plurality of resources having the concept indicated by the same concept class “ramen shop” from the accumulated metadata. Metadata including resource URIs other than “Menendo” and the same property “last order time” is searched, the total number of the searched metadata is calculated in step S51, and the calculated total number is calculated in advance. If it is equal to or greater than the stored second threshold value, the schema is extended by adding a sentence including the same concept class “ramen restaurant” and the property “last order time” to the schema in step S55. As a result, the schema can be correctly extended based on the existing metadata.

  Further, the schema extension system, as a schema extension method, selects one of resource URIs (resources) of a plurality of resources having the concept indicated by the same concept class “ramen shop” from the metadata accumulated in steps S37 and S47. Search for metadata including the URI “Menmendo” or any other) and the same property “last order time”, and the total number of the searched metadata is calculated in step S61. If the total number is equal to or greater than the third threshold value stored in advance, a schema including the same concept class “ramen shop” and the property “last order time” is added to the schema in step S65. To expand. As a result, the schema can be correctly extended based on the existing metadata.

  Further, the schema extension system, as a schema extension method, in step S73, a plurality of concept classes subordinate to the same concept class “Chinese restaurant” from the schema, that is, the concept class “ramen restaurant” and the concept class “Dim Sum Shop” ”And the same property“ last order time ”is included in the schema portion, the same concept class“ Chinese restaurant ”and the same property“ The schema is extended by adding to the schema a statement containing "last order time". As a result, the schema can be correctly extended based on the existing schema.

  In this embodiment, the schema extension system is configured by a plurality of computers. However, the schema extension system may be configured by a single computer.

  A computer program for configuring the schema extension system described above by a computer is stored in a computer-readable recording medium such as a semiconductor memory, a magnetic disk, an optical disk, a magneto-optical disk, or a magnetic tape, or communicated via the Internet. It can be distributed widely through the network.

It is a figure which shows the structure of the computer system to which this invention is applied. 3 is a directed graph with a label showing a part of a schema managed by the schema management device 1. It is a directed graph with a label which shows the metadata which the metadata management part 21 of 2 A of user apparatuses has memorize | stored. It is a sequence diagram when newly registering metadata including the last order time of Menmendou. It is a figure which shows the display content displayed on 2A of user apparatuses. It is a figure which shows the display content displayed on 2A of user apparatuses. It is a figure which shows the display content displayed on 2A of user apparatuses. It is a figure which shows the display content displayed on 2A of user apparatuses. It is a figure which shows the display content displayed on 2A of user apparatuses. It is a directed graph with a label which shows the metadata memorize | stored in 2A of user apparatuses after finishing step S23. It is a figure which shows the display content displayed on 2A of user apparatuses. It is a directed graph with a label which shows the metadata memorize | stored in 2A of user apparatuses after finishing step S23. It is a sequence diagram when extending the schema of the schema management apparatus 1 by the user apparatus 2A. It is a sequence diagram when extending the schema of the schema management apparatus 1 by the user apparatus 2A. It is a figure which shows the mode of a schema extension. It is a figure which shows the mode of a schema extension. It is a figure which shows the mode of a schema extension. It is a figure which shows the returned schema. It is a figure which shows the mode of a schema extension. It is a figure which shows the display content showing the effect of this Embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Schema management apparatus 2A, 2B, 2C User apparatus 21 Metadata management part 22 Control part 23 Display part

Claims (12)

A schema configured by accumulating statements including a concept class indicating a concept common to a plurality of resources and a property common to the plurality of resources is stored, and a resource URI that is a URI of one resource and the resource A schema extension method when metadata including properties of is accumulated,
The computer searches the accumulated metadata for metadata including the same resource URI and the same property, calculates the total number of the searched metadata, and the calculated total number is stored in advance. A schema extension method comprising: adding a sentence including the same concept class and the property to the schema when the threshold is equal to or greater than the threshold value. A schema configured by accumulating statements including a concept class indicating a concept common to a plurality of resources and a property common to the plurality of resources is stored, and a resource URI that is a URI of one resource and the resource A schema extension method when metadata including properties of is accumulated,
The computer searches the accumulated metadata for metadata including resource URIs other than a specific resource URI and the same property in resource URIs of a plurality of resources having the concept indicated by the same concept class, The total number of the retrieved metadata is calculated, and if the calculated total number is equal to or greater than a prestored threshold, a sentence including the same concept class and the property is added to the schema A schema extension method characterized by that. A schema configured by accumulating statements including a concept class indicating a concept common to a plurality of resources and a property shared by the plurality of resources is stored, and a resource URI that is a URI of one resource and the resource A schema extension method when metadata including properties of is accumulated,
The computer searches the accumulated metadata for metadata including any of the resource URIs of the plurality of resources having the concept indicated by the same concept class and the same property, and the total of the searched metadata A schema expansion method characterized by calculating a number and adding a statement including the same concept class and the property to the schema when the calculated total number is equal to or greater than a prestored threshold value . A schema extension method when a schema configured by storing statements including a concept class indicating a concept common to a plurality of resources and a property common to the plurality of resources is stored,
When the computer searches the schema for a schema part including a plurality of concept classes that are subordinate to the same concept class, and the same property is included in the schema part, the same concept class and A schema extension method comprising adding a sentence including the same property to the schema. A schema configured by accumulating statements including a concept class indicating a concept common to a plurality of resources and a property common to the plurality of resources is stored, and a resource URI that is a URI of one resource and the resource A schema extension system when metadata including properties of is accumulated,
The metadata including the same resource URI and the same property is searched from the accumulated metadata, the total number of the searched metadata is calculated, and the calculated total number is stored in advance. A schema extension system characterized by adding a statement including the same concept class and the property to the schema when the threshold is equal to or greater than a threshold value. A schema configured by accumulating statements including a concept class indicating a concept common to a plurality of resources and a property common to the plurality of resources is stored, and a resource URI that is a URI of one resource and the resource A schema extension system when metadata including properties of is accumulated,
From the accumulated metadata, a resource URI other than a specific resource URI and metadata including the same property in a plurality of resource URIs having a concept indicated by the same concept class are searched, and the searched metadata is searched. Calculating the total number of metadata, and adding the sentence including the same concept class and the property to the schema when the calculated total number is equal to or greater than a threshold stored in advance. Schema extension system. A schema configured by accumulating statements including a concept class indicating a concept common to a plurality of resources and a property common to the plurality of resources is stored, and a resource URI that is a URI of one resource and the resource A schema extension system when metadata including properties of is accumulated,
From the accumulated metadata, search for metadata including one of the resource URIs of the plurality of resources having the concept indicated by the same concept class and the same property, and calculate the total number of the searched metadata. When the calculated total number is greater than or equal to a threshold value stored in advance, a sentence including the same concept class and the property is added to the schema. Schema extension when a schema configured by accumulating statements that include concepts common to multiple resources or a concept class that represents a higher level concept of this concept and properties that the multiple resources have in common is stored A system,
When a schema part including a plurality of concept classes under the same concept class is searched from the schema, and the same property is included in the schema part, the same concept class and the same A schema extension system, wherein a statement including a property is added to the schema.   8. A function according to claim 5, further comprising a function of searching and displaying a part of the accumulated metadata and a function of adding new metadata to the accumulated metadata. The schema extension system described.   10. The schema extension system according to claim 5, further comprising a function for searching and displaying a part of the stored schema.   A computer program for configuring the schema extension system according to any one of claims 5 to 10 by a computer. A recording medium storing a computer program for configuring the schema extension system according to claim 5 by a computer.

Images