The Object Exchange Model (OEM) is a model for exchanging semi-structured data

Semi-structured model

The semi-structured model is a database model. In this model, there is no separation between the data and the schema, and the amount of structure used depends on the purpose.The advantages of this model are the following:...

 between object-oriented databases. It serves as the basic Data model

Data model

A data model in software engineering is an abstract model, that documents and organizes the business data for communication between team members and is used as a plan for developing applications, specifically how data is stored and accessed....

in numerous projects of the Stanford University Database Group, including Tsimmis, Lore, and C3 .

Slight variations of OEM have evolved across different Stanford projects. In Lore, labels are actually on parent-child "links" rather than objects. For example, if an OEM object has multiple parents, different parent objects may use different labels to identify that object. An atomic value encoding a person's name might be included in one complex object using the label "Author" and in another complex object using the label "Editor." In C3, additional attributes are required for each object to annotate the changes to the object that have occurred over time .

OEM representations

Textual OEM interchange format used in Lore - The goals of this interchange format were to have textual encodings of OEM to be easy to read, easy to edit, and easy to generate or parse by a program.

External links

• A Standard Textual Interchange Format for the Object Exchange Model