From pycyn@aol.com Thu Apr 13 01:59:47 2000 Return-Path: Received: (qmail 25281 invoked from network); 13 Apr 2000 08:59:46 -0000 Received: from unknown (10.1.10.26) by m1.onelist.org with QMQP; 13 Apr 2000 08:59:46 -0000 Received: from unknown (HELO imo27.mx.aol.com) (152.163.225.71) by mta1 with SMTP; 13 Apr 2000 08:59:46 -0000 Received: from Pycyn@aol.com by imo27.mx.aol.com (mail_out_v25.3.) id h.8a.26ab07a (3892) for ; Thu, 13 Apr 2000 04:59:43 -0400 (EDT) Message-ID: <8a.26ab07a.2626e67f@aol.com> Date: Thu, 13 Apr 2000 04:59:43 EDT Subject: RECORD:za'o To: lojban@onelist.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 4.0 for Windows sub 33 X-eGroups-From: Pycyn@aol.com From: pycyn@aol.com What is gone beyond is anything that would be expected to end what in fact continues. In processes, this is most naturally the completion of the product, but destroying the machinery, for example, also will do. For states and activities (I don't think achievements can go on overtime since they don't go on at all), anything will do: presumed interruptions, length of time, ... The most useful task for za'o as a sumti tag is, therefore, to indicate the obstacle overcome (or ignored) in the ongoing.