===================================================================
RCS file: /home/cvs/OpenXM/doc/issac2000/data-format.tex,v
retrieving revision 1.7
retrieving revision 1.9
diff -u -p -r1.7 -r1.9
--- OpenXM/doc/issac2000/data-format.tex	2000/01/15 12:18:42	1.7
+++ OpenXM/doc/issac2000/data-format.tex	2000/01/16 10:55:40	1.9
@@ -1,4 +1,4 @@
-% $OpenXM: OpenXM/doc/issac2000/data-format.tex,v 1.6 2000/01/15 03:18:27 noro Exp $
+% $OpenXM: OpenXM/doc/issac2000/data-format.tex,v 1.8 2000/01/16 06:02:41 takayama Exp $
 
 \section{Data Format}   
 
@@ -14,18 +14,18 @@ Mathcap is a list of supported CMO's, OpenXM stack mac
 and necessary extra informations.
 If a program sends an OX messages unknown to its peer, 
 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.
 Mathcap is also defined as a CMO.
 See \cite{noro-takayama} for the details.
 
-Mathematical encoding types of OX data are distinguished with tags
+Encoding types of OX data are distinguished with tags
 of OX messages.
 For example,
 an OX message with the tag 
-OX\_DATA is followed by a CMO packet.
+{\tt OX\_DATA} is followed by a CMO packet.
 An OX message with the tag 
-OX\_DATA\_OPENMATH\_XML is followed by 
+{\tt OX\_DATA\_OPENMATH\_XML} is followed by 
 an OpenMath XML string.
 
 Let us explain the data format of CMO.
@@ -109,10 +109,12 @@ $\cdots$ & {\sl CMObject} {\rm ob[n-1]} \\ 
 \cline{1-2}
 \end{tabular} \\
 
+As to the formats of other CMO's, see \cite{noro-takayama}.
+
 When one wants to implement CMO on a server, the person proceeds 
 as follows.
 \begin{enumerate}
-\item Look for the CMO list at the web cite \cite{openxm-web}.
+\item Look for the list of CMO's at the web cite \cite{openxm-web}.
 If there is a CMO that fits to one's requirement, then use this CMO.     
 \item If there is no suitable CMO, design a new CMO and register 
 the new CMO to \cite{openxm-web} with a description and examples.