Jump to content

Object Exchange Model

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Citation bot (talk | contribs) at 20:03, 22 February 2019 (Alter: isbn, template type. Add: citeseerx. | You can use this bot yourself. Report bugs here. | User-activated.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The Object Exchange Model[1] (OEM) is a model for exchanging semi-structured data between object-oriented databases. It serves as the basic data model in numerous projects of the Stanford University Database Group, including Tsimmis, Lore, and C3.[2]

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.[3]

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.

See also

References

  • ^ Papakonstantinou, Y. and Garcia-Molina, H. and Widom, J. (1995). Object exchange across heterogeneous information sources. pp. 251–260. CiteSeerX 10.1.1.47.5182. doi:10.1109/ICDE.1995.380386. ISBN 978-0-8186-6910-1. {{cite book}}: |journal= ignored (help)CS1 maint: multiple names: authors list (link)
  • ^ http://infolab.stanford.edu/~mchughj/oemsyntax/oemsyntax.html