Intensional Encapsulations of Database Subsets via Genetic Programming
Finding intensional encapsulations of database subsets is the inverse of query evaluation. Whereas query evaluation transforms an intensional expression (the query) to its extension (a set of data values), intensional encapsulation assigns an intensional expression to a given set of data values. We describe a method for deriving intensional representations of subsets of records in large database tables. Our method is based on the paradigm of genetic programming. It is shown to achieve high accuracy and maintain compact expression size, while requiring cost that is acceptable to all applications, but those that require instantaneous results. Intensional encapsulation has a broad range of applications including cooperative answering, information integration, security and data mining.
KeywordsGenetic Programming Query Evaluation Query Tree Direct Combination Compact Description
Unable to display preview. Download preview PDF.
- 1.Acar, A.C., Motro, A.: Why is this User Asking so Many Questions? Explaining Sequences of Queries. In: Proceedings of the 18th Annual IFIP WG 11.3 Working Conference on Data and Applications Security, pp. 159–176. Kluwer, Dordrecht (2004)Google Scholar
- 3.Carvalho, D.R., Freitas, A.A.: A Hybrid Decision Tree/Genetic Algorithm for Coping with the Problem of Small Disjuncts in Data Mining. In: Proceedings of the 2000 Genetic and Evolutionary Computation Conference, pp. 1061–1068. Morgan Kaufmann, San Francisco (2000)Google Scholar
- 4.Freitas, A.A.: A Survey of Evolutionary Algorithms for Data Mining and Knowledge Discovery. In: Advances in Evolutionary Computing: Theory and Applications, pp. 819–845. Springer, Heidelberg (2003)Google Scholar
- 9.Shum, C.D., Muntz, R.: Implicit Representation for Extensional Answers. In: Proceedings of the Second International Conference on Expert Database Systems, Benjamin Cummings, pp. 497–522 (1988)Google Scholar
- 10.Transaction Processing Performance Council. TPC Benchmark H Rev. 2.1.0. Technical Report, TPC (2002)Google Scholar