Highly declarative end user specification, execution and explanation of master-detail applications of relational databases

• US 20030176998A1
• Filed: 12/31/2001
• Published: 09/18/2003
• Est. Priority Date: 12/31/2001
• Status: Abandoned Application

• Current Assignee: Adrian Walker
• Original Assignee: Adrian Walker
• Inventors: Walker, Adrian
• Application Number:
  US10/039,534
• Publication Number:
  US 20030176998A1
• Time in Patent Office: Days
• US Class Current: 704/9
• CPC Class Codes: G06F 16/288 Entity relationship models
• CPC Class Codes: G06F 8/31 Programming languages or programming paradigms
• CPC Class Codes: G06F 8/313 Logic programming, e.g. PROLOG programming language

Abstract

A method and system are described for highly declarative specification of master-detail applications of relational databases, by end users who need not be trained in programming or in database administration. The method and system includes a notation in which end users can specify applications using their own English words and phrases, and by using place holders that are set out on indented lines to specify a master-detail hierarchy. The invention improves on the prior art by allowing a wider range of applications to be specified without programming, and without work by database administrators. The invention also improves on the prior art by automatically generating explanations showing what parts of the specification, and what supporting facts from the database, have been used in obtaining an answer to a question.

Claims

1. A computer-implemented method and system to allow an end user, who need not be trained as a database administrator or as an application programmer, to write a highly declarative specification of a master-detail application of a relational database, using sentences containing his own natural language words and phrases and place-holders, to directly run the specification as though it were a program, and to directly and automatically obtain explanations of the results.

2. The method of claim 1, further comprising a notation in which an end user can specify an application over a database using his own natural-language words and phrases in syllogisms containing place holders, including master-detail syllogisms containing indented conclusion lines, and in which an end user can write tables of data with heading lines containing his own natural-language words and phrases and place holders.

3. The method of claim 1, further comprising a step in which the method and system maintain a correspondence between (a) a sentence containing one or more place-holders, the sentence having been written by the end user using natural language words and phrases of his own choosing, and (b) an internal notation consisting of a logical predicate in which variables correspond respectively to the place holders, and in which the predicate name corresponds to the rest of the sentence;

the correspondence being maintained automatically by the method without necessarily requiring the separate maintenance of any natural language dictionary or grammar.

4. The method of claim 1, further comprising a step in which a master-detail syllogism is compiled into a hierarchical data structure containing variables.

5. The method of claim 1, further comprising a method of directly executing a highly declarative specification of a master-detail application of a relational database, such that an answer to an input question is a master-detail hierarchy that logically follows from the specification and the database.

6. The method of claim 1, further comprising a method of directly and automatically providing explanations of results obtained from highly declarative end user specifications of master-detail applications of relational databases.

7. The method of claim 1, further comprising steps such that, the range of applications that an end user can specify is not limited by a logical schema that must be pre-written, and maintained, by a Database Administrator.

8. The method of claim 1, further comprising steps such that the range of applications that an end user can specify is not limited by components that must be written and maintained by an application programmer.

9. The method of claim 1, further comprising steps such that, parts or all of the direct execution method for, and of the direct explanation method for, a highly declarative end user specification of a master-detail application of relational databases, are automatically compiled, for efficiency, into the database access language SQL.

10. The method of claim 1, further comprising steps such that, the input master-detail and other information is made available to the direct execution method, and to the direct explanation method, in the notation known as XML, or in the notation known as HTML, or in other similar tagged notation.

11. The method of claim 1, further comprising steps such that, the input table information is made available to the direct execution method, and to the direct explanation method, in the notation known as XML, or in the notation known as HTML, or in other similar tagged notation.

12. The method of claim 1, further comprising steps such that, the output master-detail and other information is made available from the direct execution method, and from the direct explanation method, in the notation known as XML, or in the notation known as HTML, or in other similar tagged notation.

13. The method of claim 1, further comprising steps such that, the output master-detail and other information is made available from the direct execution method, and from the direct explanation method, in end user readable displays containing nested master-detail tables.