Ontology data import/export method and apparatus

• US 8,078,647 B2
• Filed: 09/26/2008
• Issued: 12/13/2011
• Est. Priority Date: 09/27/2007
• Status: Expired due to Fees

• Current Assignee: NEC China Co Ltd (NEC Corporation)
• Original Assignee: NEC China Co Ltd (NEC Corporation)
• Inventors: Liang, Bangyong, Qi, Hongwei, Feng, Qiangze
• Primary Examiner(s): Nguyen, Cam-Linh
• Application Number:
  US12/238,626
• Publication Number:
  US 20090112903A1
• Time in Patent Office: 1,173 Days
• Field of Search: 707/661, 707/688, 707/701, 707/737, 707/749, 707791-792, 707/796, 707802-803, 707/809, 707810-811, 717/105
• US Class Current: 707/802
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

Abstract

The present invention provides a flexible ontology data import/export method and apparatus. The ontology data import apparatus comprises: an ontology data format analyzer for analyzing a format of input ontology data, and performing format determination by utilizing an ontology format database which stores formats of those successfully imported ontologies if it is a private unknown format; and an unknown format data importer for separating and importing the data into an ontology database which stores ontologies, in accordance with a result of the format determination by the ontology data format analyzer. Further, the ontology data export apparatus comprises a keyword-based and query-language-combined ontology exporter and an ontology data export format analyzer, and the keyword-based and query-language-combined ontology exporter outputs a query result returned from the ontology database in accordance with the export format returned from the ontology data export format analyzer.

Claims

1. An ontology data import apparatus, comprising:

an ontology data format analyzer device configured to analyze a format in which input ontology data is encoded, and perform format determination by utilizing an ontology format database which stores decoding information for decoding formats of successfully imported ontologies, the decoding information including decoding information for decoding a private unknown format; and

a private unknown format data importer device configured to decode, separate and import the encoded ontology data into an ontology database, which stores ontologies, in accordance with a result of the format determination by the ontology data format analyzer device,

wherein when analyzing the format in which the input ontology data is encoded, for a private unknown format, if the private unknown format contains format decoding information, then the ontology data format analyzer device directly extracts the format decoding information and adds the private unknown format into the ontology format database, and provides the contents and format decoding information of the ontology data directly to the private unknown format data importer device,

wherein when analyzing the format in which the input ontology data is encoded, for a private unknown format, if the private unknown format does not contain format decoding information, then the ontology data format analyzer device gets decoding information for decoding all private unknown formats stored in the ontology format database,

wherein if the private unknown format in which the input ontology data is encoded matches with any of the stored decoding information for decoding private unknown formats, then the ontology data format analyzer device decides to use this matched decoding information for decoding the private unknown format, and provides the contents and format decoding information of the ontology data to the private unknown format data importer device,

wherein when analyzing the format in which the input ontology data is encoded, for a private unknown format, if the private unknown format does not contain format decoding information, then the ontology data format analyzer device extracts decoding information for decoding all private unknown formats stored in the ontology format database, and

wherein if the input private unknown format does not match with any of the stored decoding information for decoding private unknown formats, then the ontology data format analyzer device extracts n most-frequently used separators from a separator database in the ontology format database, and for each of the n separators, repeatedly performs the following operations;

in the input contents, a search for this separator is performed;

if a position of this separator is correspondingly found, then forward and backward separator detections are continuously performed from this position;

an area consisting of continuous separators is determined as a separation area;

if two separation areas are found, then a corresponding separation format is determined and generated as a detected private unknown format; and

the ontology data format analyzer device provides the contents and format decoding information of the ontology data to the private unknown format data importer device.

2. The ontology data import apparatus according to claim 1, wherein:

the ontology database contains concepts, properties and instances respectively represented by triples each of which consists of a subject, a predicate and an object.

3. The ontology data import apparatus according to claim 2, wherein the ontology data format analyzer device directly returns the requested format if it is a standard known format,

wherein the ontology data import apparatus further comprises:

a known format data importer device configured to import ontology data encoded in known formats into the ontology database,

wherein the decoding information for decoding formats of successfully imported ontologies that is stored in the ontology format database includes registered known ontology types and formats, previously used private unknown formats and statistics information, and

wherein the statistics information includes statistics records for successfully imported private unknown formats and for separators used in the private unknown formats.

4. The ontology data import apparatus according to claim 3, wherein:

the private unknown formats are respectively represented as triples each of which is separated by specific separators.

5. The ontology data import apparatus according to claim 2, wherein:

when importing the input data, the private unknown format data importer device firstly imports the subject, and then determines a type property of the predicate and generates a range of values for the property, and finally imports the object in accordance with the determined type property of the predicate.

6. The ontology data import apparatus according to claim 5, wherein:

the private unknown format data importer device analyzes whether there is a numerical value as the object present in the triples having the predicate or not, and if there is a numerical value present as the object for the predicate, then it is determined that the predicate is of a numerical type property, and the range of values for the property is defined into a numerical type.

7. The ontology data import apparatus according to claim 6, wherein:

the private unknown format data importer device analyzes whether there is a numerical value for the predicate present in the triples having the predicate or not, and if there is not a numerical value present for the predicate, then it is further judged whether any object associated with the predicate can be found in the subjects;

if it can be found in the subject, it is determined that the predicate is of an objective type property; and

otherwise, if it can not be found, then it is determined that the predicate is of a numerical type property, and the range of values for the property is defined into a character string type.

31. An ontology data import/export apparatus, comprising:

an ontology data import apparatus according to claim 1; and

an ontology data export apparatus according to claim 15.

8. An ontology data import method, comprising:

analyzing, by at least one processor, a format in which input ontology data is encoded, and performing format determination by utilizing an ontology format database which stores decoding information for decoding formats of successfully imported ontologies, the decoding information including decoding information for decoding a private unknown format; and

decoding, separating and importing, by the at least one processor, the encoded ontology data into an ontology database, which stores ontologies, in accordance with a result of the format determination,

wherein when analyzing the format in which the input ontology data is encoded, for a private unknown format, if the private unknown format contains format decoding information, then the format decoding information is directly extracted and the private unknown format is added into the ontology format database,

wherein when analyzing the format in which the input ontology data is encoded, for a private unknown format, if the private unknown format does not contain format decoding information, then the decoding information for decoding all private unknown formats stored in the ontology format database is fetched,

wherein if the private unknown format in which the input ontology data is encoded matches with any of the stored decoding information for decoding private unknown formats, then it is decided to use this matched decoding information for decoding the private unknown format,

wherein when analyzing the format in which the input ontology data is encoded, for a private unknown format, if the private unknown format does not contain format decoding information, then decoding information for decoding all private unknown formats stored in the ontology format database is fetched, and

wherein if the input private unknown format does not match with any of the stored decoding information for decoding private unknown formats, then n most-frequently used separators are extracted from a separator database in the ontology format database, and for each of the n separators, the following operations are repeatedly performed;

in the inputted contents, a search for this separator is performed;

if a position of this separator is correspondingly found, then forward and backward separator detections are continuously performed from this position;

an area consisting of continuous separators is determined as a separation area; and

if two separation areas are found, then a corresponding separation format is determined and generated as a detected private unknown format.

9. The ontology data import method according to claim 8, wherein:

the ontology database contains concepts, properties and instances respectively represented by triples each of which consists of a subject, a predicate and an object.

10. The ontology data import method according to claim 9, wherein the requested format is directly returned if it is a standard known format,

wherein the ontology data import method further comprises importing ontology data encoded in known formats into the ontology database,

wherein the decoding information for decoding formats of successfully imported ontologies that is stored in the ontology format database includes registered known ontology types and formats, previously used private unknown formats and statistics information, and

wherein the statistics information includes statistics records for successfully imported private unknown formats and for separators used in the private unknown formats.

11. The ontology data import method according to claim 10, wherein:

the private unknown formats are respectively represented as triples each of which is separated by specific separators.

12. The ontology data import method according to claim 9, wherein:

when importing the inputted data, the subject is firstly imported, and then a type property of the predicate is determined and a range of values for the property is generated, and finally the object is imported in accordance with the determined type property of the predicate.

13. The ontology data import method according to claim 12, wherein:

it is analyzed whether there is a numerical value as the object present in the triples having the predicate or not, and if there is a numerical value as the object present for the predicate, then it is determined that the predicate is of a numerical type property, and the range of values for the property is defined into a numerical type.

14. The ontology data import apparatus according to claim 13, wherein:

it is analyzed whether there is a numerical value as the object present in the triples having the predicate or not, and if there is not a numerical value as the object present for the predicate, then it is further judged whether any object associated with the predicate can be found in the subjects;

if it can be found in the subject, it is determined that the predicate is of an objective type property; and

otherwise, if it can not be found, then it is determined that the predicate is of a numerical type property, and the range of values for the property is defined into a character string type.

15. An ontology data export apparatus, comprising:

an ontology data export format analyzer device;

a combined keyword-based and query-language ontology exporter device configured to;

receive a keyword and/or an export format for encoding ontology data that is to be exported;

after processing the received keyword and/or export format into a query language, query ontology data stored in an ontology database which stores ontologies; and

request an export format for encoding ontology data that is to be exported from the ontology data export format analyzer device;

wherein the ontology data export format analyzer device is configured to directly return the requested export format, or obtain the requested export format, by a query utilizing an ontology format database which stores decoding information for decoding formats of successfully imported ontologies, in accordance with the request from the combined keyword-based and query-language ontology exporter device;

wherein the combined keyword-based and query-language ontology exporter device is further configured to output a query result returned from the ontology database in accordance with the export format returned from the ontology data export format analyzer device,

wherein the ontology data export format analyzer device is configured to judge whether or not the export command contains an export format for encoding ontology data that is to be exported, and if an export format for encoding ontology data that is to be exported is contained, then directly returns the requested export format,

wherein if it is judged that the export command does not contain an export format for encoding ontology data that is to be exported, then the ontology data export format analyzer device returns the most-recently and most-frequently used import format in the ontology format database, and

wherein the ontology data export format analyzer device is configured to determine the most-recently and most-frequently used import format as follows;

selecting all formats which have been used for successfully importing the private unknown format ontologies within a predetermined time period n from the ontology format database, denoted as a set of formats rs;

for each format r in the set of formats rs, calculating a usage rate rate thereof; and

selecting a format corresponding to the maximum usage rate rate_max, as the export format for encoding ontology data that is to be exported, and returning it to the combined keyword-based and query-language ontology exporter device.

16. The ontology data export apparatus according to claim 15, wherein:

the ontology database contains concepts, properties and instances respectively represented by triples each of which consists of a subject, a predicate and an object.

17. The ontology data export apparatus according to claim 16, wherein the decoding information for decoding formats of successfully imported ontologies that is stored in the ontology format database includes registered known ontology types and formats, previously used private unknown formats and statistics information, and

wherein the statistics information includes statistics records for successfully imported private unknown formats and for separators used in the private unknown formats.

18. The ontology data export apparatus according to claim 17, wherein:

the private unknown formats are respectively represented as triples each of which is separated by specific separators.

19. The ontology data export apparatus according to claim 15, wherein:

the combined keyword-based and query-language ontology exporter device is configured to generate the query language by the following operations;

acquiring and listing all domain ontologies in the ontology database;

acquiring and listing all concepts in the user selected domain ontology;

acquiring and listing all properties for the user selected concept;

adding a query condition consisting of the user selected property and a keyword inputted by the user for the property; and

generating the query language in accordance with all the query conditions added by the user.

20. The ontology data export apparatus according to claim 19, wherein:

the combined keyword-based and query-language ontology exporter device is configured to generate the query language by the following further operations;

before the user confirms that all the query conditions have been added, allowing the user to delete and edit any of the added query conditions selected by the user; and

after the user confirms that all the query conditions are ready, generating the query language.

21. The ontology data export apparatus according to claim 15, wherein:

if and only if the maximum usage rate rate_max is larger than a predetermined threshold, then the ontology data export format analyzer device considers the format corresponding to the maximum usage rate rate_max as the export format for encoding ontology data that is to be exported.

22. The ontology data export apparatus according to claim 21, wherein:

if the maximum usage rate rate_max is not larger than the predetermined threshold, then the ontology data export format analyzer device increases a duration of the predetermined time period n, decreases the predetermined threshold, and then resumes the selection of the export format for encoding ontology data that is to be exported.

23. An ontology data export method, comprising:

receiving, by at least one processor, a keyword and/or an export format for encoding ontology data that is to be exported;

after processing, by the at least one processor, the received keyword and/or export format into a query language, querying, by the at least one processor, ontology data stored in an ontology database which stores ontologies, and requesting an export format for encoding ontology data that is to be exported;

directly returning, by the at least one processor, the requested export format or obtaining, by the at least one processor, the requested export format by a query utilizing an ontology format database which stores decoding information for decoding formats of successfully imported ontologies, in accordance with the request for the export format; and

outputting, by the at least one processor, a query result returned from the ontology database in accordance with the returned export format,

wherein it is judged whether or not the export command contains an export format for encoding ontology data that is to be exported, and if an export format for encoding ontology data that is to be exported is contained, then the requested export format is directly returned,

wherein if it is judged that the export command does not contain an export format for encoding ontology data that is to be exported, then the most-recently and most-frequently used import format in the ontology format database is returned, and

wherein the determining the most-recently and most-frequently used import format comprises the following;

selecting all formats which have been used for successfully importing the private unknown format ontologies within a predetermined time period n from the ontology format database, denoted as a set of formats rs;

for each format r in the set of formats rs, calculating a usage rate rate thereof; and

selecting a format corresponding to the maximum usage rate rate_max, as the export format for encoding ontology data that is to be exported.

24. The ontology data export method according to claim 23, wherein:

the ontology database contains concepts, properties and instances respectively represented by triples each of which consists of a subject, a predicate and an object.

25. The ontology data export method according to claim 24, wherein the decoding information for decoding formats of successfully imported ontologies that is stored in the ontology format database includes registered known ontology types and formats, previously used private unknown formats and statistics information, and

wherein the statistics information includes statistics records for successfully imported private unknown formats and for separators used in the private unknown formats.

26. The ontology data export method according to claim 25, wherein:

the private unknown formats are respectively represented as triples each of which is separated by a specific separator.

27. The ontology data export method according to claim 23, wherein:

the generating the query language comprises the following;

acquiring and listing all domain ontologies in the ontology database;

acquiring and listing all concepts in the user selected domain ontology;

acquiring and listing all properties for the user selected concept;

adding a query condition consisting of the user selected property and a keyword inputted by the user for the property; and

generating the query language in accordance with all the query conditions added by the user.

28. The ontology data export method according to claim 27, wherein:

the generating the query language further comprises the following;

before the user confirms that all the query conditions have been added, allowing the user to delete and edit any of the added query conditions selected by the user; and

after the user confirms that all the query conditions are ready, generating the query language.

29. The ontology data export method according to claim 23, wherein:

if and only if the maximum usage rate rate_max is larger than a predetermined threshold, then the format corresponding to the maximum usage rate rate_max is considered as the export format for encoding ontology data that is to be exported.

30. The ontology data export method according to claim 29, wherein:

if the maximum usage rate rate_max is not larger than the predetermined threshold, then a duration of the predetermined time period n is increased, the predetermined threshold is decreased, and then the selection of the export format for encoding ontology data that is to be exported is resumed.