Using ODA for translating multimedia information
Lessons from using ISO ODA for multimedia document exchange
Sherman, M., "Using ODA for translating multimedia information", RFC 1197, DOI 10.17487/RFC1197, December 1990, <https://www.rfc-editor.org/info/rfc1197>.
@misc{rfc1197,
series = {Request for Comments},
number = 1197,
howpublished = {RFC 1197},
publisher = {RFC Editor},
doi = {10.17487/RFC1197},
url = {https://www.rfc-editor.org/info/rfc1197},
author = {M. Sherman},
title = {{Using ODA for translating multimedia information}},
pagetotal = 2,
year = 1990,
month = dec,
} RFC text
Contents
Network Working Group M. Sherman
Request for Comments: 1197 CMU
December 1990
Using ODA for Translating Multimedia Information
1. Status of this Memo
The purpose of this RFC is to inform implementors of multimedia
systems about our experiences using ISO 8613: Office Document
Architecture (ODA). Because ODA is being proposed as an encoding
format for use in multimedia mail and file exchange, implementors
wishing to use ODA in an open systems environment may profit from our
experiences. This memo provides information for the Internet
community. It does not specify any standard. Distribution of this
memo is unlimited.
2. Overview
ODA is a recently approved ISO (8613) and CCITT (T.410) standard for
representing documents containing multifont text, raster images and
geometric graphics. This encoding has been specified for use in a
number of related standards, such as X.400.
However, ODA is a very abstract standard, defining entities such as
"composite logical object classes" and not common entities, such as
"paragraphs". Therefore, effective use of ODA as an interchange
medium requires the definition of a document application profile
(dap) that defines some common entities and a map between ODA
entities defined in the dap and entities used in the interchanged
systems.
3. EXPRES Experiences
The National Science Foundation funded the EXPRES project, which
consisted of groups at Carnegie Mellon University (Information
Technology Center) and the University of Michigan (Center for
Information Technology Integration). These two groups collaborated
with groups at McDonnell-Douglas Aerospace Information Systems, NIST,
and Interleaf. Together, the five groups investigated the use of ODA
as an interchange medium for submitting research proposals by
electronic mail to the National Science Foundation.
Part of the investigations yielded strategies for using ODA. We based
our strategies on the NIST dap and the features provided by the
Andrew, Diamond, and Interleaf systems. Our experiences been
documented and published in a book [1]. The discussion may be
valuable for others who wish to use ODA as an interchange medium.
4. Disclaimer
The information provided in [1] is the opinion only of the authors
and does not represent the opinions or policies of Carnegie Mellon
University, the University of Michigan, McDonnell-Douglas Aerospace
Information Systems, NIST, Interleaf, or the National Science
Foundation.
5. References
[1] Jonathan Rosenberg, Mark Sherman, Ann Marks & Jaap Akkerhuis,
"Multi-media Document Translation: ODA and the EXPRES Project",
Springer-Verlag (New York), 1991, ISBN 0-387-97397-4,
3-540-97397-4.
Security Considerations
Security issues are not discussed in this memo.
Author's Address
Mark Sherman
Information Technology Center
Carnegie Mellon University
4910 Forbes Avenue
Pittsburgh, PA 15213
Phone: (412) 268-6727
Fax: (412) 268-6787
EMail: mss+@andrew.cmu.edu
AI ELI5
On this page
§1ISO Office Document Architecture
The ISO 8613 standard for Office Document Architecture (ODA) defines a way to represent documents containing multifont text, raster images and geometric graphics. ODA was also standardized by CCITT as T.410 and was being considered for use in email and file exchange systems.
However, ODA is highly abstract, defining complex entities like "composite logical object classes" rather than concepts users understand, such as paragraphs. This abstraction made ODA difficult to use without additional guidance.
ODA is a very detailed blueprint for how to describe pictures and text, but it is so complicated that people needed help using it.
§2The EXPRES Project
The National Science Foundation funded the EXPRES project to investigate practical use of ODA for exchanging research proposals via electronic mail. Teams from Carnegie Mellon University and the University of Michigan collaborated with McDonnell-Douglas Aerospace Information Systems, NIST, and Interleaf.
The groups developed strategies for using ODA based on the NIST document application profile (DAP) and features provided by real systems (Andrew, Diamond, and Interleaf). These experiences were documented in a published book.
A group of universities and companies worked together to figure out how to actually use ODA for sending documents through email.
§3Key Findings
The RFC references a book that documents the EXPRES findings, describing strategies for using ODA and lessons from the implementation work. The group's discussion of what worked and what did not is intended to be valuable for others considering ODA as an interchange format.
The main lesson is that a document application profile (DAP) is essential: it must define common, recognizable concepts and provide clear mapping between ODA entities and the formats used in systems that want to interchange documents.
To make ODA actually work, you have to create a simpler profile that defines real things like "paragraph" and "heading" that people understand.