Return-Path: <@FINHUTC.HUT.FI:LOJBAN@CUVMB.BITNET> Received: from FINHUTC.hut.fi by xiron.pc.helsinki.fi with smtp (Linux Smail3.1.28.1 #14) id m0pitc8-0000PYC; Tue, 22 Mar 94 01:42 EET Message-Id: Received: from FINHUTC.HUT.FI by FINHUTC.hut.fi (IBM VM SMTP V2R2) with BSMTP id 6108; Tue, 22 Mar 94 01:42:20 EET Received: from SEARN.SUNET.SE (NJE origin MAILER@SEARN) by FINHUTC.HUT.FI (LMail V1.1d/1.7f) with BSMTP id 6104; Tue, 22 Mar 1994 01:42:19 +0200 Received: from SEARN.SUNET.SE (NJE origin LISTSERV@SEARN) by SEARN.SUNET.SE (LMail V1.2a/1.8a) with BSMTP id 0631; Tue, 22 Mar 1994 00:41:13 +0100 Date: Mon, 21 Mar 1994 17:39:48 -0500 Reply-To: Logical Language Group Sender: Lojban list From: Logical Language Group Subject: Re: TECH: Various X-To: lojban@cuvmb.cc.columbia.edu To: Veijo Vilva In-Reply-To: <199403212150.AA08465@nfs1.digex.net> from "Matthew Faupel" at Mar 21, 94 09:48:21 pm Content-Length: 814 Lines: 22 la matius. cusku di'e > 1. Use of "dakau" to specify exactly what sort of a property abstraction is > being created. > > Seems fine to me. Would the omission of "dakau" result in the assumption of > x1 being the place in question or of it being left to the hearer to > interpret from context? Interpret from context, as almost always in Lojban. The only time x1 is magic is in descriptions. > What effect does this have on existing text? Very little. The problem which led to the "old" convention wasn't discovered until a few months ago (although adumbrations of it have existed since 1975 or even earlier, as with most Lojban problems). Possibly no text needs to change at all. -- John Cowan sharing account for now e'osai ko sarji la lojban.