From lojban-out@lojban.org Mon Apr 12 21:35:44 2004 Return-Path: X-Sender: lojban-out@lojban.org X-Apparently-To: lojban@yahoogroups.com Received: (qmail 78748 invoked from network); 13 Apr 2004 04:35:43 -0000 Received: from unknown (66.218.66.172) by m8.grp.scd.yahoo.com with QMQP; 13 Apr 2004 04:35:43 -0000 Received: from unknown (HELO chain.digitalkingdom.org) (64.81.49.134) by mta4.grp.scd.yahoo.com with SMTP; 13 Apr 2004 04:35:43 -0000 Received: from lojban-out by chain.digitalkingdom.org with local (Exim 4.30) id 1BDFe9-0007Sv-Ql for lojban@yahoogroups.com; Mon, 12 Apr 2004 21:35:41 -0700 Received: from dsl081-049-134.sfo1.dsl.speakeasy.net ([64.81.49.134] helo=chain.digitalkingdom.org) by chain.digitalkingdom.org with esmtp (Exim 4.30) id 1BDFdC-0007SC-Hj; Mon, 12 Apr 2004 21:34:42 -0700 Received: with ECARTIS (v1.0.0; list lojban-list); Mon, 12 Apr 2004 21:34:38 -0700 (PDT) Received: from fort-point-station.mit.edu ([18.7.7.76]) by chain.digitalkingdom.org with esmtp (Exim 4.30) id 1BDFd1-0007S1-RX for lojban-list@lojban.org; Mon, 12 Apr 2004 21:34:31 -0700 Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82]) by fort-point-station.mit.edu (8.12.4/8.9.2) with ESMTP id i3D4YTZR023229 for ; Tue, 13 Apr 2004 00:34:30 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86]) by grand-central-station.mit.edu (8.12.4/8.9.2) with ESMTP id i3D4YT0d002449 for ; Tue, 13 Apr 2004 00:34:29 -0400 (EDT) Received: from torg.mit.edu (TORG.MIT.EDU [18.208.0.57]) ) by melbourne-city-street.mit.edu (8.12.4/8.12.4) with ESMTP id i3D4YSUa022088 for ; Tue, 13 Apr 2004 00:34:28 -0400 (EDT) Received: from rob by torg.mit.edu with local (Exim 3.36 #1 (Debian)) id 1BDFcz-0002Nl-00 for ; Tue, 13 Apr 2004 00:34:29 -0400 Date: Tue, 13 Apr 2004 00:34:29 -0400 Message-ID: <20040413043429.GA9141@mit.edu> Mail-Followup-To: lojban-list@lojban.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Is-It-Not-Nifty: www.sluggy.com User-Agent: Mutt/1.5.5.1+cvs20040105i X-archive-position: 7532 X-ecartis-version: Ecartis v1.0.0 Sender: lojban-list-bounce@lojban.org Errors-to: lojban-list-bounce@lojban.org X-original-sender: rspeer@MIT.EDU X-list: lojban-list To: lojban@yahoogroups.com X-eGroups-Remote-IP: 64.81.49.134 X-eGroups-From: Rob Speer From: Rob Speer Reply-To: rspeer@MIT.EDU Subject: [lojban] Scope of ko X-Yahoo-Group-Post: member; u=116389790 X-Yahoo-Profile: lojban_out X-Yahoo-Message-Num: 22006 It seems like the "personal pro-sumti" checkpoint of the BPFK should be fairly easy to complete, with just one exception: ko. I remember some disagreement about the scope of ko, and I'm not sure it was ever resolved. Does ko cross ije-connectives? If so, how do you connect a non-imperative statement to an imperative one? As an example of where the scope of ko really matters, compare these two sentences: 1. Don't sleep with her just because you want to. 2. Don't sleep with her, because you'll catch an STD. They require different scopes of a command. How would each one be expressed? -- Rob Speer