Object-Oriented Constraints for XML Schema

Alagić, Suad; Bernstein, Philip A.; Jairath, Ruchi

doi:10.1007/978-3-642-16092-9_11

Cited by 3 publications

(6 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Our goals are object-oriented schemas with general integrity constraints, transactions written in a mainstream object-oriented language, and their static verification that guarantees ACID properties in an implementation based on an object-oriented database management system. These goals represent a significant advancement of our previous results reported in [2].…”

Section: Introductionmentioning

confidence: 67%

“…Our most recent results that apply to XML Schema constraints and the associated transactions are based on Spec# [2]. Reflective constraint management, static and dynamic techniques for enforcing constraints, and transaction verification technology are presented in [3,4,22].…”

Section: Related Researchmentioning

confidence: 99%

“…General integrity constraints are missing from most persistent and database object models with rare exceptions such as [2,4,8]. This specifically applies to the ODMG model [9,5], PJama [18], Java Data Objects [12], and just as well to the current generation of systems such as Db4 Objects [10], Objectivity [20] or LINQ [17].…”

Section: Related Researchmentioning

confidence: 99%

“…In a typed constraint-based database technology, the constraints would fit into the type systems of object-oriented languages and they should be integrated with reflective capabilities of those languages [22] so that they can be introspected at run-time. Most importantly, all of that is not sufficient if there is no technology to enforce the constraints, preferably statically, so that expensive recovery procedures will not be required when a transaction violates the constraints at run-time [2,3].…”

Section: Introductionmentioning

confidence: 99%

“…No industrial database technology allows object-oriented schemas equipped with general integrity constraints. In addition to keys and referential integrity, such constraints include ranges of values or number of occurrences, ordering, constraints that apply to inheritance, and the integrity requirements for complex objects obtained by aggregation [2]. More general constraints that are not necessarily classical database constraints come from complex application environments and they are often critical for correct functioning of those applications [3].…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Verifiable Object-Oriented Transactions

Alagić

Fazeli

2014

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. Unlike the existing object-oriented and other database technologies, database schemas in the technology developed in this research are equipped with very general integrity constraints specified in a declarative, logic-based fashion. These declarative specifications are expressed in object-oriented assertion languages and they apply to transactions that are implemented in a full-fledged, mainstream object-oriented programming language. The model of transactions is based on more advanced features of object-oriented type systems, the ownership model, and very general constraints. The main distinction in comparison with other database technologies is that transactions can be verified to satisfy the schema integrity constraints. The two main contributions of this paper are object-oriented schemas equipped with integrity constraints and static verification of transactions with respect to the integrity constraints. Solutions to these open problems have been out of reach so far. Furthermore, transaction verification is not only largely static, but it is also automatic, so that the subtleties of the underlying verification technology are hidden from the users. In addition to static verification, the technology offers dynamic enforcement of the integrity constraints when necessary. The overall outcome is a significant increase in data integrity along with run-time efficiency and reliability of transactions.

show abstract

Section: Introductionmentioning

confidence: 67%

Section: Related Researchmentioning

confidence: 99%

Section: Related Researchmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Verifiable Object-Oriented Transactions

Alagić

Fazeli

2014

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

show abstract

Types and Constraints

Alagić

2015

Object-Oriented Technology

View full text Add to dashboard Cite

Automatic versus interactive program verification

Alagić

2013

Proceedings of the 2013 ACM SIGAda Annual Conference on High Integrity Language Technology

View full text Add to dashboard Cite

We report on experiences in using two very different program verification technologies. One of them is based on object-oriented assertion languages and it comes with automatic static verification of object-oriented programs. The other technology is independent of a programming language or programming paradigm and it offers static interactive verification of very complex constraints. These two technologies were applied to the problem of static verification of object-oriented transactions. The problem was chosen because database technologies are not equipped to handle general integrity constraints and verification technologies are not used to verify transactions. The implications of static verification on data integrity, efficiency, and reliability of transactions are significant.

show abstract

Object-Oriented Constraints for XML Schema

Cited by 3 publications

References 9 publications

Verifiable Object-Oriented Transactions

Verifiable Object-Oriented Transactions

Types and Constraints

Automatic versus interactive program verification

Contact Info

Product

Resources

About