[BACK]Return to data-format.tex CVS log [TXT][DIR] Up to [local] / OpenXM / doc / ascm2001

Diff for /OpenXM/doc/ascm2001/data-format.tex between version 1.1 and 1.3

version 1.1, 2001/03/07 02:42:10 version 1.3, 2001/03/08 04:24:09
Line 1 
Line 1 
 % $OpenXM$  % $OpenXM: OpenXM/doc/ascm2001/data-format.tex,v 1.2 2001/03/08 00:49:29 takayama Exp $
   
 \section{Data Format}  \section{Data Format}
   
Line 17  an unrecoverable error may occur. 
Line 17  an unrecoverable error may occur. 
 By exchanging mathcaps, a program knows its peer's capability  By exchanging mathcaps, a program knows its peer's capability
 and such an error can be avoided.  and such an error can be avoided.
 Mathcap is also defined as a CMO.  Mathcap is also defined as a CMO.
 See \cite{noro-takayama} for the details.  See \cite{ox-rfc-100} for the details.
   
 Encoding types of OX data are distinguished with tags  Encoding types of OX data are distinguished with tags
 of OX messages.  of OX messages.
Line 108  $\cdots$ & {\sl byte} {\rm data[n-1]} \\ 
Line 108  $\cdots$ & {\sl byte} {\rm data[n-1]} \\ 
 $\cdots$ & {\sl CMObject} {\rm ob[n-1]} \\  $\cdots$ & {\sl CMObject} {\rm ob[n-1]} \\
 \cline{1-2}  \cline{1-2}
 \end{tabular} \\  \end{tabular} \\
   CMO's can be expressed in terms of XML.
 As to the formats of other CMO's, see \cite{noro-takayama}.  For example, {\tt (CMO\_INT32} $1234${\tt )} can be expressed by
   {\footnotesize
   \begin{verbatim}
   <cmo>
    <cmo_int32>
      <int32> 1234 </int32>
    </cmo_int32>
   </cmo>
   \end{verbatim}
   }
   As to the formats of other CMO's and XML, see \cite{ox-rfc-100}.
   
 When one wants to implement CMO on a server, the person proceeds  When one wants to implement CMO on a server, the person proceeds
 as follows.  as follows.

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.3

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>