Object Exchange Model

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

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.

gollark: It makes no sense. Dimmer lighting should mean longer exposure.
gollark: What? It should be the other way round.
gollark: Any recent computer will have hardware video encoders for at least H.264 also.
gollark: It would be weird if it wasn't.
gollark: But imagine if you could watch the trees experience wind or whatever at 30 FPS.

See also

References
  1. Papakonstantinou, Y.; Garcia-Molina, H.; Widom, J. (1995). "Object exchange across heterogeneous information sources". Proceedings of the Eleventh International Conference on Data Engineering. Taipei, Taiwan: IEEE Comput. Soc. Press: 251–260. CiteSeerX 10.1.1.47.5182. doi:10.1109/ICDE.1995.380386. ISBN 978-0-8186-6910-1.
  2. "A Standard Textual Interchange Format for the Object Exchange Model (OEM)". infolab.stanford.edu. Retrieved 2020-02-07.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.