Received: by ATHENA-PO-2.MIT.EDU (5.45/4.7) id AA07883; Tue, 14 Jun 88 13:23:33 EDT
From: <mackay@ATHENA.MIT.EDU>
Received: by ATHENA.MIT.EDU (5.45/4.7) id AA27445; Tue, 14 Jun 88 13:23:28 EDT
Received: by E40-368-1 (5.45/4.7)
	id AA02591; Tue, 14 Jun 88 13:23:00 EDT
Message-Id: <8806141723.AA02591@E40-368-1>
To: rap@ATHENA.MIT.EDU, bgardner@ATHENA.MIT.EDU, jbs@ATHENA.MIT.EDU
Subject: This is Jeff's project plan.  W
Date: Tue, 14 Jun 88 13:22:57 EDT


------- Forwarded Message
Wendy,

As we discussed, I will be working on developing a prototype design
and implementation of message types for the Unix lens system.  Target
date for completion is June 13, although I will let you know more
about the rate of progress as the work develops.

Jeff
- ---
Message type design and prototype:

	1. A document defining what the concept or a message 
	   type means for this project.

	2. Several paragraphs on each of the following
	   aspects of message type handling:

		a. Editing message types (including creating
 		   and displaying).
		b. Storing message types.
		c. Messages (instances), and associating
		   them with their type.
		d. Running rules on an instance.

	3. Prototype implementation and demo:

		a. Code to create, store, and display
		   message types.
		b. Code to create a message instance
		   from an ASCII text message.
		c. Code to run a set of rules.
		d. 3 message types.
		e. 5 actual messages.
		f. 1 or 2 rules (including selection criteria
		   and actions), coded as prototypes only.

------- End of Forwarded Message

