===================================================================
RCS file: /home/cvs/OpenXM/doc/OpenXM-specs/formal-expression.tex,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -p -r1.6 -r1.7
--- OpenXM/doc/OpenXM-specs/formal-expression.tex	2000/09/09 16:32:26	1.6
+++ OpenXM/doc/OpenXM-specs/formal-expression.tex	2000/09/09 21:59:13	1.7
@@ -1,4 +1,4 @@
-%% $OpenXM: OpenXM/doc/OpenXM-specs/formal-expression.tex,v 1.5 2000/09/08 18:57:49 takayama Exp $
+%% $OpenXM: OpenXM/doc/OpenXM-specs/formal-expression.tex,v 1.6 2000/09/09 16:32:26 takayama Exp $
 //&jp \section{ CMO ¤Î·Á¼°ÅªÉ½¸½ÊýË¡ }
 //&eg \section{ A formal expression of CMO }
 
@@ -17,7 +17,8 @@ Primitive group.
 In this section, we will introduce CMOexpression which is like the 
 bracket expression of Lisp. 
 We again explain a standard encoding method of CMO,
-which we have already explained in the previous section.
+which we have already explained in the previous section, but
+the explanation is more formal.
 */
 
 /*&jp
@@ -235,7 +236,7 @@ CMOexpression ¤È, CMObject ¤Î¶èÊ̤òÍý²ò¤·¤Æ¤ª¤¯¤Î¤Ï½ÅÍ
 ½ñ¤¯.
 */
 /*&eg
-It is possible to express CMO by XML like Open Math (\cite{openmath}).
+CMO's are expressed by XML like Open Math (\cite{openmath}).
 See example below.
 */
 
@@ -256,7 +257,7 @@ See example below.
 */
 
 //&jp \noindent cmo\_string ¤Ï¼¡¤Î¤è¤¦¤Ë¤¢¤é¤ï¤·¤Æ¤â¤è¤¤.
-//&eg \noindent cmo\_string can also be expressed as follows.
+//&eg \noindent cmo\_string may be expressed as follows.
 /*&C
 \begin{verbatim}
 
@@ -304,17 +305,19 @@ and byte data are encoded as it is.
 100Mbps ¤ÎÄÌ¿®Ï©¤Ç 12Mbytes ¤Î {\tt CMO\_ZZ} ¤ÎžÁ÷¤Ç¤Ï 
 Ìó 90\% ¤Î»þ´Ö¤¬ network byte order ¤Ø¤ÎÊÑ´¹¤Ë¤Ä¤¤¤ä¤µ¤ì¤Æ¤¤¤ë¤È¤¤¤¦
 ¼Â¸³¥Ç¡¼¥¿¤â¤¢¤ë.
-¸úΨ¤ò½Å»ë¤·¤¿ encoding Ë¡¤Ë¤Ä¤¤¤Æ¤Ï¸å½Ò¤¹¤ë.
+¸úΨ¤ò½Å»ë¤·¤¿ encoding Ë¡¤Ë¤Ä¤¤¤Æ¤Ï¸å½Ò¤¹¤ë \ref{subsection:byteorder}.
 */
 /*&eg
 When we are using a high speed network,
 the translation from the internal expression of 32 bit integers to
 network byte order may become a bottle neck.
 There are experimental data which presents that 90 percents of the transmission
-time are
+time are used
 for the translation to the network byte order to send {\tt CMO\_ZZ} of size
-12M bytes on a 100Mbps network.
-In a later section, we will discuss a protocol to avoid the translation.
+12M bytes.
+We used a 100Mbps network.
+In a later section \ref{subsection:byteorder}, 
+we will discuss a protocol to avoid the translation.
 */
 
 /*&C
@@ -363,14 +366,14 @@ is the encoding of the CMOexpression
 
 /*&jp
 (¼Â¸³Åª)
-CMO ¤ª¤è¤Ó OX packets ¤Ï XML µ¬³Ê¤Ë½àµò¤·¤Æ¤¤¤ë.
+CMO ¤ª¤è¤Ó OX packets ¤Ï XML µ¬³Ê \cite{xml} ¤Ë½àµò¤·¤Æ¤¤¤ë.
 XML µ¬³Ê¤Î Attribute ¤ò binary encode ¤¹¤ë¤¿¤á¤Ë
 ÆÃÊ̤ʥ¿¥° \\
 */
 /*&eg
 (Experimental)
-CMO and OX packets are complient to XML specification.
-In order to encode ``Attribute'' in XML in a binary format,
+CMO and OX packets are complient to XML specification \cite{xml}.
+In order to encode ``Attribute'' in XML in our binary format,
 we have a tag: \\
 */
 //&C \verb! #define CMO_ATTRIBUTE_LIST  (LARGEID+3) !  \\
@@ -401,4 +404,11 @@ XML ɽ¸½¤Ç¤Ï XML ¤Î¥¿¥°¤È¤·¤ÆÍý²ò¤µ¤ì¤ë.
 All tags except this special CMO tag {\tt CMO\_ATTRIBUTE\_LIST}
 are XML tags in the CMO/XML expression.
 */
-
+/*&jp
+CMO/XML ¤Ç {\it comment}, {\it for} ¤È̾Á°¤¬¤Ä¤¤¤¿
+attributes ¤Ï CMO binary expression ¤Ë¤Ï¥¨¥ó¥³¡¼¥É¤µ¤ì¤Ê¤¤.
+*/
+/*&eg
+CMO/XML attributes such as {\it comment}, {\it for}
+are not encoded in the CMO binary expression.
+*/