[BACK]Return to design-outline.tex CVS log [TXT][DIR] Up to [local] / OpenXM / doc / ascm2001p

Diff for /OpenXM/doc/ascm2001p/design-outline.tex between version 1.3 and 1.4

version 1.3, 2001/06/20 02:40:09 version 1.4, 2001/06/20 03:08:05
Line 1 
Line 1 
 % $OpenXM: OpenXM/doc/ascm2001p/design-outline.tex,v 1.2 2001/06/20 02:09:45 takayama Exp $  % $OpenXM: OpenXM/doc/ascm2001p/design-outline.tex,v 1.3 2001/06/20 02:40:09 takayama Exp $
   
 \section{Design Outline and OpenXM Request for Comments (OpenXM-RFC)}  \section{Design Outline and OpenXM Request For Comments}
   
 As Schefstr\"om\cite{schefstrom}, clarified,  As Schefstr\"om\cite{schefstrom} clarified,
 integration of tools and software has three dimensions:  integration of tools and software has three dimensions:
 data, control, and user interface.  data, control, and user interface.
   
Line 59  software.
Line 59  software.
 However, we found that it might be just a dream without realizability  However, we found that it might be just a dream without realizability
 and that it is an important research subject to  and that it is an important research subject to
 build a prototype of such an integrated system. % Project X  build a prototype of such an integrated system. % Project X
   
 We started the OpenXM project with the following  We started the OpenXM project with the following
 fundamental architecture, which is currently described in  fundamental architecture, which is currently described in
 OpenXM-RFC 100  proposed standard %% ``draft standard'' and ``standard''  OpenXM-RFC 100  proposed standard %% ``draft standard'' and ``standard''
Line 81  The stack machine is called the
Line 80  The stack machine is called the
 Existing mathematical software systems are wrapped with this stack machine.  Existing mathematical software systems are wrapped with this stack machine.
 Minimal requirements for a target software wrapped with the OX stack machine  Minimal requirements for a target software wrapped with the OX stack machine
 are as follows:  are as follows:
 \begin{enumerate}  (a) The target must have a serialized interface such as a character based
 \item The target must have a serialized interface such as a character based  
 interface.  interface.
 \item An output of the target must be understandable for computer programs;  (b) An output of the target must be understandable for computer programs;
 it should follow a grammar that can be parsed with other software.  it should follow a grammar that can be parsed with other software.
 \end{enumerate}  
 \item Any server may have a hybrid interface;  \item Any server may have a hybrid interface;
 it may accept and execute not only stack machine commands,  it may accept and execute not only stack machine commands,
 but also its original command sequences.  but also its original command sequences.
 For example,  For example,
 if we send the following string to the {\tt ox\_asir} server  if we send the following string to the {\tt ox\_asir} server
 (OpenXM server of Risa/Asir) \\  (OpenXM server of Risa/Asir)
 \verb+        " fctr(x^100-y^100); "      + \\  \verb+" fctr(x^100-y^100); "+
 and call the stack machine command  \\  and call the stack machine command
 \verb+        SM_executeStringByLocalParser    + \\  \verb+SM_executeStringByLocalParser+
 then the server executes the asir command \\  then the server executes the asir command
 \verb+ fctr(x^100-y^100); +  \verb+ fctr(x^100-y^100); +
 (factorize $x^{100}-y^{100}$ over ${\bf Q}$)  (factorize $x^{100}-y^{100}$ over ${\bf Q}$)
 and pushes the result onto the stack.  and pushes the result onto the stack.
Line 106  and 101 \cite{ox-rfc-101} based on
Line 103  and 101 \cite{ox-rfc-101} based on
 the above fundamental architecture.  the above fundamental architecture.
 In this paper, we discuss mainly on systems implementing  In this paper, we discuss mainly on systems implementing
 OpenXM-RFC 100 and 101 on TCP/IP.  OpenXM-RFC 100 and 101 on TCP/IP.
 For example, the following is a command sequence to ask $1+1$ from  %For example, the following is a command sequence to ask $1+1$ from
 the Asir client to the {\tt ox\_sm1} server through TCP/IP:  %the Asir client to the {\tt ox\_sm1} server through TCP/IP:
 \begin{verbatim}  %\begin{verbatim}
   P = sm1_start();  %  P = sm1_start(); ox_push_cmo(P,1); ox_push_cmo(P,1);
   ox_push_cmo(P,1); ox_push_cmo(P,1);  %  ox_execute_string(P,"add"); ox_pop_cmo(P);
   ox_execute_string(P,"add"); ox_pop_cmo(P);  %\end{verbatim}
 \end{verbatim}  %Here, {\tt ox\_sm1} is an OpenXM server of Kan/sm1.
 Here, {\tt ox\_sm1} is an OpenXM server of Kan/sm1.  
   
 Our project of integrating mathematical software  Our project of integrating mathematical software
 systems is taking the ``RFC'' approach, which has been  systems is taking the ``RFC'' approach, which has been
 used to develop internet protocols.  used to develop internet protocols.
 We think that ``RFC'' approach is an excellent way and  
 we hope that other groups, who are working on standard protocols,  
 take this ``RFC'' approach, too.  
   
 The OpenXM on MPI \cite{MPI} is currently running on Risa/Asir  The OpenXM on MPI \cite{MPI} is currently running on Risa/Asir
 as we will see in Section \ref{section:homog}.  as we will see in Section \ref{section:homog}.
 We are now preparing the OpenXM-RFC 102 ``Mathematical communication  We are now preparing the OpenXM-RFC 102 ``Mathematical communication
 on MPI'' (draft protocol)  on MPI'' (draft protocol).
 based on our experiments on MPI.  
   
 In the rest of the paper, we abbreviate  In the rest of the paper, we abbreviate
 OpenXM-RFC 100 and 101 to OpenXM if no confusion arises.  OpenXM-RFC 100 and 101 to OpenXM if no confusion arises.
   
   
   
   
   
   
   
   
Legend:
Removed from v.1.3  
changed lines
  Added in v.1.4
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>