Received: from mail-oi0-f63.google.com ([209.85.218.63]:37169) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XfGwz-00054i-QS for lojban-list-archive@lojban.org; Fri, 17 Oct 2014 16:28:54 -0700 Received: by mail-oi0-f63.google.com with SMTP id u20sf201110oif.28 for ; Fri, 17 Oct 2014 16:28:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe; bh=JfpHkTe08pAVNxYvSaojOmuqBo3INoOplLG9IaGMKSY=; b=PfE5AIu3q8v7ne4QOFvfoY2zwLdRw7iwzttchm9qGD/3A0jyXoGJjDlF694avCAJIV ODzB21zKvSvjVcw4HcTgesAnpgQgrzHyB5k/Ctf6CYqC3/HD99RD7sa3AhizI1XdUknL r8TdvNt4M2YIAGsiGYYCCXYHqzRxB7AhEV36sebMOdGJz/L50myVrIOuO5I/ybYf2s4K g6DuCwvTiufUHQcwBuN1CHp4orfFB/Qx/DEG13NNG68Ods+tqYqQTml06y8anB7a3dMI E9OIZcEtqHvUKgsINlaAkdYaAqPTjDzjJJO3WcNEIITOYB9LvewaPcMXJfxxWtxusFau t9Vg== X-Received: by 10.140.42.107 with SMTP id b98mr34888qga.11.1413588523313; Fri, 17 Oct 2014 16:28:43 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.140.87.71 with SMTP id q65ls1360926qgd.32.gmail; Fri, 17 Oct 2014 16:28:43 -0700 (PDT) X-Received: by 10.236.19.77 with SMTP id m53mr3851574yhm.1.1413588523021; Fri, 17 Oct 2014 16:28:43 -0700 (PDT) Received: from sdf.lonestar.org (mx.sdf.org. [192.94.73.24]) by gmr-mx.google.com with ESMTPS id bj5si298831pdb.1.2014.10.17.16.28.42 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Oct 2014 16:28:42 -0700 (PDT) Received-SPF: none (google.com: mbays@sdf.org does not designate permitted sender hosts) client-ip=192.94.73.24; Received: from thegonz.net (d24-141-9-29.home.cgocable.net [24.141.9.29]) (authenticated (0 bits)) by sdf.lonestar.org (8.14.8/8.14.5) with ESMTP id s9HNS7lZ022857 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Fri, 17 Oct 2014 23:28:09 GMT Received: from martin by thegonz.net with local (Exim 4.80.1) (envelope-from ) id 1XfGwS-00035o-Rd for lojban@googlegroups.com; Fri, 17 Oct 2014 19:28:16 -0400 Date: Fri, 17 Oct 2014 19:28:16 -0400 From: Martin Bays To: lojban@googlegroups.com Subject: Re: [lojban] Re: tersmu 0.2 Message-ID: <20141017232816.GB20049@gonzales> References: <20141011143749.GD23876@gonzales> <20141012012427.GF23876@gonzales> <20141012173533.GG23876@gonzales> <20141014010742.GF19061@gonzales> <20141015005542.GC3713@gonzales> <543E2F31.1050302@gmx.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7ZAtKRhVyVSsbBD2" Content-Disposition: inline In-Reply-To: <543E2F31.1050302@gmx.de> X-PGP-Key: http://mbays.freeshell.org/pubkey.asc X-PGP-KeyId: B5FB2CD6 X-cunselcu'a-valsi: xampo User-Agent: Mutt/1.5.22 (2013-10-16) X-Original-Sender: mbays@sdf.org X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: mbays@sdf.org does not designate permitted sender hosts) smtp.mail=mbays@sdf.org Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -2.6 (--) X-Spam_score: -2.6 X-Spam_score_int: -25 X-Spam_bar: -- --7ZAtKRhVyVSsbBD2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Wednesday, 2014-10-15 at 10:24 +0200 - selpa'i : > la'o me. Martin Bays .me cusku di'e > > So maybe {lo} isn't quite \iota, but it's something like "\iota applied > > to some ad-hoc but somehow natural subset of the extension"? If that > > isn't to reduce to just "lo broda is something(s) satisfying broda", > > this "natural" will have to be doing a lot of work... I don't have much > > of an idea what it could be. > > > > Possibly it can all be done by specifying the tense and aspect of > > {broda}? With the kind reading corresponding to gnomic aspect? >=20 > I definitely think tense can do a lot of this (maybe even all of it)=20 > while retaining maximality. It does make some sense that implicit tenses (etc) should be allowed in sub-bridi. To clarify: by a sub-bridi, I mean something like: a logical formula (possibly with free variables) evaluated as part of the parse of a sentence, including what I'll call the "implicit" sub-bridis which don't correspond to a sentence or subsentence production. So e.g. description sumti involve implicit sub-bridi, as do quantified selbri; elsewhere in this thread, under the guise of "opaqueness vs transparency", we're effectively discussing what other constructions should involve implicit sub-bridi. If implicit tenses are allowed in description sumti, I'd say they should be allowed in all sub-bridi. But then maybe we have a problem: if in your example > there are two cats in the room, one black and one white we consider {re mlatu cu zvati .i je lo mlatu cu xekri} as being plausibly elliptical for {lo vi mlatu cu xekri}, shouldn't we consider {re mlatu cu zvati .i je ro mlatu cu xekri} as being equally plausibly elliptical for {ro vi mlatu cu xekri}? That seems strange to me. I think it's pretty clear that we do want to allow implicit tenses in abstractions, though. But perhaps not in relative clauses, for the same reason as above? Maybe not very important, but I wonder whether "implicit tense" isn't just a Lojbanicism for something more general - that the situation a sentence is talking about (e.g. claiming a proposition to be true of) doesn't have to be at all specified explicitly, and in particular its spatial and temporal position (or lack thereof) doesn't have to be specified. So perhaps rather than asking whether sub-bridi have implicit tenses, we should rather ask whether they have to be evaluated in the same situation as the enclosing bridi, or whether they can introduce a situation shift (and so in particular a domain shift). > I have also used the gnomic aspect to describe the generic reading, but= =20 > we don't currently have a cmavo that indicates gnomic aspect. Aha, then probably I got that from you! I was trying to recall where I came across "gnomic aspect"; you on irc sounds likely. Martin --7ZAtKRhVyVSsbBD2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlRBphAACgkQULC7OLX7LNbIowCgkaOHw9U5+mSfh1leMWGYlMCW TCMAoKMkQ7i4RDMRBLxZZiqKG5PN+ygv =Ncxw -----END PGP SIGNATURE----- --7ZAtKRhVyVSsbBD2--