Return-Path: <@CUNYVM.CUNY.EDU:LOJBAN@CUVMB.BITNET> Received: from kantti.helsinki.fi by xiron.pc.helsinki.fi with smtp (Linux Smail3.1.28.1 #1) id m0sszk8-0000ZLC; Thu, 14 Sep 95 00:53 EET DST Received: from fiport.funet.fi (fiport.funet.fi [128.214.109.150]) by kantti.helsinki.fi (8.6.12+Emil1.1/8.6.5) with ESMTP id AAA25728 for ; Thu, 14 Sep 1995 00:53:19 +0300 Received: from CUNYVM.CUNY.EDU (MAILER@CUNYVMV2) by FIPORT.FUNET.FI (PMDF V5.0-3 #2494) id <01HV8X8YT8TC0006Z9@FIPORT.FUNET.FI> for veion@XIRON.PC.HELSINKI.FI; Thu, 14 Sep 1995 00:54:10 +0200 (EET) Received: from CUNYVM.CUNY.EDU (NJE origin LISTSERV@CUNYVM) by CUNYVM.CUNY.EDU (LMail V1.2a/1.8a) with BSMTP id 6870; Wed, 13 Sep 1995 17:52:24 -0400 Date: Wed, 13 Sep 1995 22:51:50 +0100 From: ucleaar Subject: afterthought scope retraction Sender: Lojban list To: Veijo Vilva Reply-to: ucleaar Message-id: <01HV8X8YZ00I0006Z9@FIPORT.FUNET.FI> Content-transfer-encoding: 7BIT X-To: lojban@cuvmb.cc.columbia.edu MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Length: 894 Lines: 21 A while back I made a number of proposals for how to indicate scope in afterthought (when the desired scope is not indicated by left-to- right order). The proposals were intended to state the scope relationship between sumti. I failed to take into account that scope concerns not only quantifiers but also connectives. My proposals are therefore insufficiently general as a solution, so I withdraw them. Looking at Lojban/Loglan with 30 years hindsight, I'd say that if one wishes to develop a logical language (that is a bit more flexible than pred logic notation) then one should start with scope, and only then tackle the predicate-argument structure. It is too late for that now, of course. So instead I'd argue that Lojban is a fixed word-order language, with word order determined by scope, but within those constraints there is some flexibility when scope is not involved. --- And