What should a database know?

The Journal of Logic Programming

Volumn 14, Issue 1-2, 1992, Pages 127-153

  Reiter, Raymond ^a  

^a NONE

Author keywords

[No Author keywords available]

Indexed keywords

EID: 44049112934     PISSN: 07431066     EISSN: None     Source Type: Journal    
DOI: 10.1016/0743-1066(92)90049-9     Document Type: Article

References (26)

1. Amalgamating Language and Meta-Language in Logic Programming
2. Logic Based Approach to Semantic Query Optimization
3. Process Management and Assertion Enforcement for a Semantic Data Model
4. Negation as Failure
5. Syntactical Characterization of a Subset of Domain Independent Formulas
6. Horn Clauses and Database Dependencies
7. A Guide to the Model Logics of Knowledge and Belief: Preliminary Report
8. Logic for Data Description
9. A Formal Treatment of Incomplete Knowledge Bases
10. Foundations of a Functional Approach to Knowledge Representation
11. All I Know: A Study in Autoepistemic Logic
12. Closed World Databases and Circumscription
13. Making Prolog More Expressive
14. A Basis for Deductive Database Systems
15. On Indefinite Databases and the Closed World Assumption
16. Data Base: Theory vs. Interpretation
17. Integrity Checking in Deductive Data Bases
18. Logic for Improving Integrity Checking in Relational Databases
19. On Closed World Data Bases
20. Towards a Logical Reconstruction of Relational Database Theory
21. A Sound and Sometimes Complete Query Evaluation Algorithm for Relational Databases with Null Values
22. On Integrity Constraints
23. On Asking a Database What It Knows
24. Theorem-Proving Approach to Database Integrity