System for accessing a relational database using semantic queries

• US 10,216,860 B2
• Filed: 05/26/2016
• Issued: 02/26/2019
• Est. Priority Date: 10/22/2010
• Status: Active Grant

• Current Assignee: Data.World, Inc.
• Original Assignee: Capsenta, Inc. (Data.World, Inc.)
• Inventors: Miranker, Daniel Paul, Sequeda, Juan Federico
• Primary Examiner(s): Khong, Alexander
• Application Number:
  US15/165,775
• Publication Number:
  US 20160275204A1
• Time in Patent Office: 1,006 Days
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06F 16/353 into predefined classes
• CPC Class Codes: G06F 16/81 Indexing, e.g. XML tags; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/8358 Query translation
• CPC Class Codes: G06F 16/8365 Query optimisation
• CPC Class Codes: G06F 16/86 Mapping to a database
• CPC Class Codes: G06F 16/90332 Natural language query formulation or dialogue systems

Abstract

This invention is a system for integrating relational databases into a semantic web framework utilizing a simple mapping process and the SQL query optimizer present in the SQL database engine.

Claims

1. A system comprised of one or more computers for executing a digitally encoded first query that is expressed in a query language operable on a graph representation of data, on the data contents of a pre-existing relational database with comprised of a corresponding relational database schema, said system comprising:

a computer memory comprised of stored data encoding the first query, said stored first query being expressed in a query language operable on a graph representation of data;

a translating module comprised of logic configured to automatically translate the stored first query into a second digitally encoded database query expressed in a relational query language by using a mapping data structure stored in a computer memory comprising said system, said data structure embodying a graph that represents a synthetic domain model representation of the relational database schema, in order to create a data object representing the second translated relational query; and

a relational database system comprised of the pre-existing relational database configured by logic to execute the second translated relational query on the pre-existing relational database.

2. The system of claim 1 further comprising an optimizing a module comprised of logic configured to optimize the second translated query prior to its execution on the relational database.

3. The system of claim 2 where the optimizing module is further configured to detect an at least one unsatisfiable condition.

4. The system of claim 2 where the optimizing module is further configured to execute a self-join elimination.

5. The system of claim 2 where the optimizing module is further configured to execute a self outer join elimination.

6. The system of claim 1 where the translating module is further configured to use a data structure representing the synthetic domain model expressed in OWL (Web Ontology Language).

7. The system of claim 1 where the translating module is further configured to use a data structure representing the synthetic domain model expressed in RDFS (Resource Description Framework Schema).

8. The system of claim 1 further comprising a generating module adapted by logic to generate from the representation of the synthetic domain model a data structure embodying an RDF (Resource Description Framework) logical representation of the pre-existing relational database data that conforms to the synthetic domain model.

9. The system of claim 1 further comprising a generating module adapted by logic to generate a data structure representing an RDF (Resource Description Framework) logical representation using a view definition associated with the pre-existing relational database.

10. The system of claim 9 where the view definition is a SQL view definition.

11. The system of claim 9 where the view definition is logical.

12. The system of claim 9 where the view definition is materialized.

13. The system of claim 10 where the SQL view definition is comprised of a body nested in the translated query.

14. The system of claim 1 where the translating module is further configured to output data representing the second translated relational query where the arguments of the second translated relational query are at least one column of a RDF (Resource Description Framework) logical representation of at least a portion of the data contents of the pre-existing relational database.

15. The system of claim 1 where the translating module is further configured to convert a unique resource identifier into a string comprised of a combination of a table name identifying a data table and a column label associated with the data table identified by the table name.

16. The system of claim 1 where the translating module is further configured to materialize into a data structure a plurality of database records comprising the pre-existing relational database as an RDF (Resource Description Framework) representation.

17. The system of claim 1 where the translating module is further configured to determine component substitutions of an at least one component comprising the stored first query.

18. The system of claim 1 further comprising a second translating module comprised of logic configured to translate the output of the relational database executing the second translated relational query into a data output that conforms to the query language operable on a graph representation of data.

19. The system of claim 1 where the graph representation of data is a property graph.

20. The system of claim 1 where the first query is expressed in a query language operable on a semantic graph representation of data.

21. The system of claim 1 where the first query is expressed in a query language operable on a property graph representation of data.

22. The system of claim 1 where the first query is expressed in a query language operable on a RDF representation of data.

23. The system of claim 1 where the first query is expressed in a query language operable on a triple table representation of data.

24. The system of claim 23 where the triple table has more than three columns.

34. The method of claim 22 where the view definition is a SQL view definition.

37. The method of claim 34 where the SQL view definition is comprised of a body nested in the translated query.

25. A method executed by a computer system comprised of one or more computers, for executing a digitally encoded first query that is expressed in a query language operable on a graph representation of data, on the data contents of a pre-existing relational database comprised of a corresponding relational database schema, said method comprising:

retrieving from a data storage device data encoding the first query, said first query being expressed in a query language operable on a graph representation of data

automatically translating the first database query into a second digitally encoded translated database query expressed in a relational query language by using a mapping data structure stored in a computer memory comprising said computer system, said data structure embodying a graph that represents a synthetic domain model representation of the relational database schema in order to create a data object representing the second translated relational query; and

executing the second translated relational query on the pre-existing relational database.

26. The method of claim 25 further comprising the step of:

optimizing the second translated query prior to its execution on the pre-existing relational database.

27. The method of claim 26 further comprising the step of:

detecting an at least one unsatisfiable condition.

28. The method of claim 26 further comprising the step of:

executing a self-join elimination.

29. The method of claim 26 further comprising the step of:

executing a self outer join elimination.

30. The method of claim 25 further comprising the step of:

generating a data structure representing the synthetic domain model expressed in OWL (Web Ontology Language).

31. The method of claim 25 further comprising the step of:

generating a data structure representing the synthetic domain model expressed in RDFS (Resource Description Framework Schema).

32. The method of claim 25 further comprising the step of:

generating a data structure embodying an RDF (Resource Description Framework) logical representation of the pre-existing relational database data that conforms to the synthetic domain model.

33. The system of claim 25 further comprising the step of:

generating a data structure representing an RDF (Resource Description Framework) logical representation of a portion of the pre-existing relational database using a view definition associated with the pre-existing relational database.

35. The method of claim 33 where the view definition is logical.

36. The method of claim 33 where the view definition is materialized.

38. The method of claim 25 further comprising the step of:

generating data representing the second translated relational query where the arguments of the second translated query are at least one column of a RDF (Resource Description Framework) logical representation of at least a portion of the data contents of the pre-existing relational database.

39. The method of claim 25 further comprising the step of:

converting a unique resource identifier into a string comprised of a combination of a table name identifying a data table and a column label associated with the data table identified by the table name, said data table being a component of the pre-existing relational database.

40. The method of claim 25 further comprising the step of:

materializing in a data structure a plurality of database records comprising the pre-existing relational database as an RDF (Resource Description Framework) representation.

41. The method of claim 25 further comprising the step of:

determining the component substitutions of an at least one component comprising the retrieved first query.

42. The method of claim 25 further comprising the step of:

translating the output of the relational database executing the second translated relational query into a data output that conforms to the query language operable on a graph representation of data.

43. The method of claim 25 where the graph representation of data is a property graph.

44. The method of claim 25 where the first query is expressed in a query language operable on a semantic graph representation of data.

45. The method of claim 25 where the first query is expressed in a query language operable on a property graph representation of data.

46. The method of claim 25 where the first query is expressed in a query language operable on a RDF representation of data.

47. The method of claim 25 where the first query is expressed in a query language operable on a triple table representation of data.

48. The method of claim 47 where the triple table has more than three columns.