===================================================================
RCS file: /home/cvs/OpenXM/doc/issac2000/data-format.tex,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -p -r1.6 -r1.7
--- OpenXM/doc/issac2000/data-format.tex	2000/01/15 03:18:27	1.6
+++ OpenXM/doc/issac2000/data-format.tex	2000/01/15 12:18:42	1.7
@@ -1,25 +1,23 @@
-% $OpenXM: OpenXM/doc/issac2000/data-format.tex,v 1.5 2000/01/13 10:58:16 ohara Exp $
+% $OpenXM: OpenXM/doc/issac2000/data-format.tex,v 1.6 2000/01/15 03:18:27 noro Exp $
 
-\section{Data Format}   (Ohara)
+\section{Data Format}   
 
 OpenXM admits multiple mathematical encodings such as OpenMath, MP, CMO
 (Common Mathematical Object format).
 OpenXM itself does not exhibit a bias towards a particular encodings 
 as a main mathematical data carrier and an OpenXM compliant system do not need to
 implement all possible data formats.
-A server or a client does not necessarily implement full specifications
-of OpenXM. However  they should at least implement seven primitive 
+However  they should at least implement seven primitive 
 data types of the CMO, which are necessary to 
 carry several control informations such as a {\it mathcap}.
 Mathcap is a list of supported CMO's, OpenXM stack machine codes, 
 and necessary extra informations.
-If a program sends an OX messages to its peer, 
+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 
 and such an error can be avoided.
-Mathcap is also defined as a CMO and the CMO has a structure of a nest
-of lists.  its leafs of the end are also a CMO which tags with
-CMO\_INT32 or CMO\_STRING.
+Mathcap is also defined as a CMO.
+See \cite{noro-takayama} for the details.
 
 Mathematical encoding types of OX data are distinguished with tags
 of OX messages.
@@ -28,14 +26,14 @@ an OX message with the tag 
 OX\_DATA is followed by a CMO packet.
 An OX message with the tag 
 OX\_DATA\_OPENMATH\_XML is followed by 
-an OpenMath XML string and its length.
+an OpenMath XML string.
 
 Let us explain the data format of CMO.
 Any CMO packet consists of a header and a body.
 The size of the header is 4 bytes that tags the data type of the body.
 Data type tags are signed 32 bit integers which is called {\sl int32} in this
 paper.
-Following tags are registered in the OpenXM for now.
+Following tags are registered in the OpenXM.
 \begin{verbatim}
 #define CMO_ERROR2                         0x7f000002
 #define CMO_NULL                           1
@@ -60,16 +58,15 @@ Following tags are registered in the OpenXM for now.
 #define CMO_RATIONAL                       34
 #define CMO_64BIT_MACHINE_DOUBLE           40
 #define CMO_ARRAY_OF_64BIT_MACHINE_DOUBLE  41
-#define CMO_128BIT_MACHINE_DOUBLE          42
-#define CMO_ARRAY_OF_128BIT_MACHINE_DOUBLE 43
 #define CMO_BIGFLOAT                       50
 #define CMO_IEEE_DOUBLE_FLOAT              51
 #define CMO_INDETERMINATE                  60
 #define CMO_TREE                           61
 #define CMO_LAMBDA                         62
 \end{verbatim}
-The first seven types should be implemented on all OpenXM compliant systems.
-The format of the first seven CMO's are as follows. \\
+The first seven primitive types should be implemented 
+on all OpenXM compliant systems.
+The formats are as follows. \\
 \begin{tabular}{|c|c|}
 \hline
 {\sl int32} {\tt CMO\_ERROR2} & {\sl CMObject} {\rm ob} \\ 
@@ -112,11 +109,11 @@ $\cdots$ & {\sl CMObject} {\rm ob[n-1]} \\ 
 \cline{1-2}
 \end{tabular} \\
 
-A mathematical programmer who wants to implement CMO on a server proceeds 
+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}.
-If there is a CMO that fits to her or his requirement, then use this CMO.     
+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.
 \end{enumerate}