Abstract

The paper discusses the potential value of a deontic approach to database specification. More specifically, some different types of integrity constraints are considered and a distinction is drawn between necessary (hard) and deontic (soft) constraints.Databases are compared with other normative systems. A deontic logic for database specification is proposed and the problems of how to react to, and of how to correct, or repair, a situation which arises through norm violation are discussed in the context of this logic. The limitations of the proposed logic and possible modifications and extensions of it are analysed.