RFC1197 Using ODA for translating multimedia information

1197 Using ODA for translating multimedia information. M. Sherman. December 1990. (Format: TXT=3620 bytes) (Status: INFORMATIONAL)

日本語訳
RFC一覧

参照

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



Sherman                                                         [Page 1]

RFC 1197                       Using ODA                   December 1990


   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


















一覧

 RFC 1〜100  RFC 1401〜1500  RFC 2801〜2900  RFC 4201〜4300 
 RFC 101〜200  RFC 1501〜1600  RFC 2901〜3000  RFC 4301〜4400 
 RFC 201〜300  RFC 1601〜1700  RFC 3001〜3100  RFC 4401〜4500 
 RFC 301〜400  RFC 1701〜1800  RFC 3101〜3200  RFC 4501〜4600 
 RFC 401〜500  RFC 1801〜1900  RFC 3201〜3300  RFC 4601〜4700 
 RFC 501〜600  RFC 1901〜2000  RFC 3301〜3400  RFC 4701〜4800 
 RFC 601〜700  RFC 2001〜2100  RFC 3401〜3500  RFC 4801〜4900 
 RFC 701〜800  RFC 2101〜2200  RFC 3501〜3600  RFC 4901〜5000 
 RFC 801〜900  RFC 2201〜2300  RFC 3601〜3700  RFC 5001〜5100 
 RFC 901〜1000  RFC 2301〜2400  RFC 3701〜3800  RFC 5101〜5200 
 RFC 1001〜1100  RFC 2401〜2500  RFC 3801〜3900  RFC 5201〜5300 
 RFC 1101〜1200  RFC 2501〜2600  RFC 3901〜4000  RFC 5301〜5400 
 RFC 1201〜1300  RFC 2601〜2700  RFC 4001〜4100  RFC 5401〜5500 
 RFC 1301〜1400  RFC 2701〜2800  RFC 4101〜4200 

スポンサーリンク

mktemp 適当なファイル名の空ファイルを作成する

ホームページ製作・web系アプリ系の製作案件募集中です。

上に戻る