Annotation of OpenXM/doc/ascm2001/design-outline.tex, Revision 1.2
1.2 ! takayama 1: % $OpenXM: OpenXM/doc/ascm2001/design-outline.tex,v 1.1 2001/03/07 02:42:10 noro Exp $
1.1 noro 2:
1.2 ! takayama 3: \section{Design Outline and OpenXM Request for Comments (OpenXM-RFC)}
1.1 noro 4:
5: As Schefstr\"om clarified in \cite{schefstrom},
1.2 ! takayama 6: integration of tools and software has three dimensions:
1.1 noro 7: data, control, and user interface.
8:
9: Data integration concerns with the exchange of data between different
1.2 ! takayama 10: software or same software.
1.1 noro 11: OpenMath \cite{OpenMath} and MP (Multi Protocol) \cite{GKW} are,
12: for example, general purpose mathematical data protocols.
13: They provide standard ways to express mathematical objects.
14: For example,
15: \begin{verbatim}
16: <OMOBJ> <OMI> 123 </OMI> </OMOBJ>
17: \end{verbatim}
18: means the (OpenMath) integer $123$ in OpenMath/XML expression.
19:
20: Control integration concerns with the establishment and management of
21: inter-software communications.
22: Control involves, for example, a way to ask computations to other processes
23: and a method to interrupt computations on servers from a client.
24: RPC, HTTP, MPI, PVM are regarded as a general purpose control protocols or
25: infrastructures.
26: MCP (Mathematical Communication Protocol)
27: by Wang \cite{iamc} is such a protocol for mathematics.
28:
29: Although data and control are orthogonal to each other,
30: real world requires both.
31: NetSolve \cite{netsolve}, OpenMath$+$MCP, MP$+$MCP \cite{iamc},
32: and MathLink \cite{mathlink} provide both data and control integration.
33: Each integration method has their own features determined by their
34: own design goals.
35: OpenXM (Open message eXchange protocol for Mathematics)
36: is a project aiming to integrate data, control and user interfaces
37: with design goals motivated by the followings.
38: \begin{enumerate}
39: \item Noro has been involved in the development of
40: a computer algebra system Risa/Asir \cite{asir}.
41: An interface for interactive distributed computations was introduced
42: to Risa/Asir
43: %% version 950831 released
44: in 1995.
45: The model of computation was RPC (remote procedure call).
46: A robust interruption protocol was provided
47: by two communication channels
48: like the File Transfer Protocol (ftp).
49: As an application of this protocol,
50: a parallel speed-up was achieved for a Gr\"obner basis computation
51: to determine all odd order replicable functions
52: (Noro and McKay \cite{noro-mckay}).
53: However, the protocol was local in Asir and we thought that we should
54: design an open protocol.
55: \item Takayama has developed
56: a special purpose system Kan/sm1 \cite{kan},
57: which is a Gr\"obner engine for the ring of differential operators $D$.
58: In order to implement algorithms in $D$-modules due to Oaku
59: (see, e.g., \cite{sst-book}),
60: factorizations and primary ideal decompositions are necessary.
61: Kan/sm1 does not have an implementation for these and called
62: Risa/Asir as a UNIX external program.
63: This approach was not satisfactory.
64: Especially, we could not write a clean interface code between these
65: two systems.
66: We thought that it is necessary to provide a data and control protocol
67: for Risa/Asir to work as a server of factorization and primary ideal
68: decomposition.
69: \item We have been profited from increasing number
1.2 ! takayama 70: of mathematical software.
1.1 noro 71: These are usually ``expert'' systems in one area of mathematics
72: such as ideals, groups, numbers, polytopes, and so on.
73: They have their own interfaces and data formats,
74: which are fine for intensive users of these systems.
75: However, a unified system will be more convenient
76: for users who want to explore a new area of mathematics with these
1.2 ! takayama 77: software or users who need these systems only occasionally.
1.1 noro 78:
79: \item We believe that an open integrated system is a future of mathematical
1.2 ! takayama 80: software.
1.1 noro 81: However, it might be just a dream without realizability.
82: We want to build a prototype of such an open system by using
1.2 ! takayama 83: existing standards, technologies and several mathematical software.
1.1 noro 84: We want to see how far we can go with this approach.
85: \end{enumerate}
86:
87: Motivated with these, we started the OpenXM project with the following
1.2 ! takayama 88: fundamental architecture, which is currently described in
! 89: OpenXM RFC 100 proposed standard %% ``draft standard'' and ``standard''
! 90: ``Design and Implementation of OpenXM client-server model and common
! 91: mathematical object format''.
1.1 noro 92: \begin{enumerate}
93: \item Communication is an exchange of messages. The messages are classified into
94: three types:
95: DATA, COMMAND, and SPECIAL.
96: They are called OX (OpenXM) messages.
97: Among the three types,
98: {\it OX data messages} wrap mathematical data.
99: We use standards of mathematical data formats such as OpenMath and MP
100: as well as our own data format {\it CMO}
1.2 ! takayama 101: ({\it Common Mathematical Object format}),
! 102: which can be described in XML.
1.1 noro 103: \item Servers, which provide services to other processes, are stack machines.
104: The stack machine is called the
105: {\it OX stack machine}.
1.2 ! takayama 106: Existing mathematical software are wrapped with this stack machine.
1.1 noro 107: Minimal requirements for a target software wrapped with the OX stack machine
108: are as follows:
109: \begin{enumerate}
110: \item The target must have a serialized interface such as a character based
111: interface.
112: \item An output of the target must be understandable for computer programs;
1.2 ! takayama 113: it should follow a grammar that can be parsed with other software.
1.1 noro 114: \end{enumerate}
115: \item Any server may have a hybrid interface;
116: it may accept and execute not only stack machine commands,
117: but also its original command sequences.
118: For example,
119: if we send the following string to the {\tt ox\_asir} server
120: (OpenXM server based on Risa/Asir) \\
121: \verb+ " fctr(x^100-y^100); " + \\
122: and call the stack machine command \\
123: \verb+ SM_executeStringByLocalParser + \\
124: then the server executes the asir command \\
125: \verb+ fctr(x^100-y^100); +
126: (factorize $x^{100}-y^{100}$ over ${\bf Q}$)
127: and pushes the result onto the stack.
128: \end{enumerate}
129: OpenXM package is implemented on above fundamental architecture.
130: For example, the following is a command sequence to ask $1+1$ from
131: the Asir client to the {\tt ox\_sm1} server:
132: \begin{verbatim}
133: P = sm1_start();
134: ox_push_cmo(P,1); ox_push_cmo(P,1);
135: ox_execute_string(P,"add"); ox_pop_cmo(P);
136: \end{verbatim}
137: Here, {\tt ox\_sm1} is an OpenXM server based on Kan/sm1.
138:
1.2 ! takayama 139: The OpenXM package is implemented on the OpenXM RFC 100 for TCP/IP,
1.1 noro 140: which uses the client-server model.
1.2 ! takayama 141: In this paper, we discuss mainly on systems implementing
! 142: OpenXM RFC 100 on TCP/IP.
! 143:
! 144: Our project is taking the ``RFC'' approach, which has been
! 145: used to develop internet protocols, to integrate mathematical software
! 146: systems.
! 147: We hope that other groups, who are working on standard protocols,
! 148: take the ``RFC'' approach.
! 149:
1.1 noro 150: The OpenXM on MPI \cite{MPI} is currently running on Risa/Asir
151: as we will see in Section \ref{section:homog}.
1.2 ! takayama 152: We are now preparing the OpenXM RFC 102 ``Mathematical communication
! 153: on MPI'' (draft protocol)
! 154: based on our experiments on MPI.
! 155:
! 156:
! 157:
1.1 noro 158:
159:
160:
161:
162:
163:
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>
![[BACK]](/icons/cvsweb/back.gif){kind=icon}
Return to design-outline.tex CVS log ![[TXT]](/icons/cvsweb/text.gif){kind=icon}
![[DIR]](/icons/cvsweb/dir.gif){kind=icon}
Up to [local] / OpenXM / doc / ascm2001