From beringer@DB.Stanford.EDU Mon Jan 12 14:00:24 1998
Received: from Sealion.Stanford.EDU (Sealion.Stanford.EDU [171.64.75.55]) by DB.Stanford.EDU (8.8.5/8.7.1) with SMTP id OAA24446 for <chaims>; Mon, 12 Jan 1998 14:00:20 -0800
Sender: beringer@DB.Stanford.EDU
Message-ID: <34BA92F8.1C4A@db.stanford.edu>
Date: Mon, 12 Jan 1998 14:02:32 -0800
From: Dorothea Beringer <beringer@DB.Stanford.EDU>
X-Mailer: Mozilla 3.01Gold (X11; I; HP-UX A.09.05 9000/712)
MIME-Version: 1.0
To: chaims@DB.Stanford.EDU
Subject: Minutes of 1/12/98
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mozilla-Status: 0001
Content-Length: 1863

Minutes of 1/12/98
==================

Meetings:
The meetings this quarter will probably be Wednesday, 11:15 (maybe
10:15).

ASN.1:
We need two things for CHAIMS. First we need an ASN.1-compiler that
compiles ASN.1-definition files into e.g. C. This C-library then
provides routines for decoding and encoding the data-structures
specified in the ASN.1-definition file from C-data to encoded data and
from encoded data to C-data. These C-libraries would be linked to the
appropriate megamodules. Thus the ASN.1-compiler will help us to wrap
the megamodules. Suggestion of Pankaj: a ASN.1-interpreter that could
dynamically take C-data, read the ASN.1-definitions and generate encoded
data would be even nicer than a compiler, because it could be built into
the wrapper.
Secondly we need a BER-interpreter. This interpreter takes ASN.1-encoded
data, analysis it and outputs its content (e.g. as strings that can be
displayed on a screen). This interpreter is needed for the general
I/O-megamodule. If none such interpreter exists, we will write one
ourselves.

General I/O-megamodule: 
For the general I/O-megamodule we assume that no lookup of
ASN.1-definition files is necessary. It is the responsibility of the
other megamodules to add any necessary names and descriptions of data to
the effective data itself, so that the ASN.1-data will contain both, the
names in a user-presentable way and the desired values. 

CHAIMS-architecture:
There seems to exist some confusion about the architecture of CHAIMS. I
will try to present an overview of the architecture in our next meeting,
so we can discuss it.

Next CHAIMS meeting: Wednesday, Jan 14, 11:10, room 359 (3rd floor!).
Agenda: Overview of the CHAIMS architecture, work assignment for Mehul,
decision concerning the ASN.1-compiler and BER-interpreter.


Comments to these minutes welcome any time.

Dorothea