O2, an object-oriented data model

Abstract

The Altair group is currently designing an object-oriented data base system called O 2 . This paper presents a formal description of the object-oriented data model of this system. It proposes a type system defined in the framework of a set-and-tuple data model. It models the well known inheritance mechanism and enforces strong typing.

Normalizing object classes in fuzzy object-oriented database schema

“…Mët èi t÷ñng mí l mët bë o = (id, v), id l mët ph¦n tû cõa OID, v l mët gi¡ trà mí (rã). val(o) biºu thà gi¡ trà v èi vîi o, ÷ñc ành ngh¾a nh÷ sau [4] (a) mët ph¦n tû cõa dom, mët ph¦n tû cõa OID v nil l c¡c gi¡ trà.…”

Querying RDF Data from a Graph Database Perspective

“…On the other hand, in many semantic and object oriented data models the conceptual representation of data is transparently graph-based. For example O 2 [39] defines basic, tuple-structured, and set-structured types (the first type is similar to an RDF blank node and the remainder two can be modeled as relations in RDF); GOOD [27] is oriented primarily to graphical user interfaces; OEM [32] addresses the information exchange problem, and is oriented to express resources and relations in a standard way (in agreement to the RDF philosophy); GDM [40] defines instances and schema graphs with features similar to RDF (e.g. domain and range of relations, typeOf properties).…”

A Review of Object Oriented Database Concepts and their Implementation

“…O2 was designed with the purpose of integrating data base technology with the object-oriented approach, all in one system (Lecluse, et al, 1988). This language is also data model where objects may have a tuple or set structure, or be atomic.…”