From nobody@digitalkingdom.org Fri Dec 19 10:05:49 2008 Received: with ECARTIS (v1.0.0; list lojban-list); Fri, 19 Dec 2008 10:05:52 -0800 (PST) Received: from nobody by chain.digitalkingdom.org with local (Exim 4.69) (envelope-from ) id 1LDjjR-00082g-Hi for lojban-list-real@lojban.org; Fri, 19 Dec 2008 10:05:49 -0800 Received: from rv-out-0708.google.com ([209.85.198.247]) by chain.digitalkingdom.org with esmtp (Exim 4.69) (envelope-from ) id 1LDjjO-00082C-UM for lojban-list@lojban.org; Fri, 19 Dec 2008 10:05:49 -0800 Received: by rv-out-0708.google.com with SMTP id b17so1132060rvf.46 for ; Fri, 19 Dec 2008 10:05:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=cDhUS8t1z86T4Lu6xc8sm2qPbGHgu5ZvCtZjkE+w++Y=; b=NecYBR188rpYu22SptcBpu2o0QpQB7tCf2XA4Lvm+GYBFVlqcBG9TQBJu64x+8o+zf DhRBD4nO9R20auWdmCcDrUYW/ihwNkWKLwrc/mN8pnakMIoPDSHzfP3KinLjpTvzSxTE vTAbkg8+S3xo/LjaNL9zdqsg9CLKwqfePvUTk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=p5sb1bJxvpgiWzHv87Z90f7hDIYBDa29sTyXkizHMDrsO+R+4obsPBHUpdoLX7t2f3 jti2AX2zLknf96uh1ZtkKsPl2l7GFbu8euYIDWwnTVvCBhRdXjPfA/griO5kTx/WIdRa bUaoELcvoiKrdCJrFyGgFDMVhSPf40wfKdi2A= Received: by 10.141.136.4 with SMTP id o4mr1717820rvn.13.1229709945817; Fri, 19 Dec 2008 10:05:45 -0800 (PST) Received: by 10.141.194.15 with HTTP; Fri, 19 Dec 2008 10:05:45 -0800 (PST) Message-ID: <925d17560812191005nd881082tddfabf6d283f6494@mail.gmail.com> Date: Fri, 19 Dec 2008 15:05:45 -0300 From: "=?ISO-8859-1?Q?Jorge_Llamb=EDas?=" To: lojban-list@lojban.org Subject: [lojban] Re: [lojban-beginners] Re: About the negators In-Reply-To: <96f789a60812190833k22700061i143be7bf997749ce@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <101615.13333.qm@web81304.mail.mud.yahoo.com> <925d17560812171429j1e9f7202r4381bbd7e063b19e@mail.gmail.com> <96f789a60812181220tfb3d6c3k56b01d844f9e4075@mail.gmail.com> <925d17560812181329y69bf5672of028ac125047536d@mail.gmail.com> <96f789a60812190833k22700061i143be7bf997749ce@mail.gmail.com> X-Spam-Score: 0.0 X-Spam-Score-Int: 0 X-Spam-Bar: / X-archive-position: 15121 X-ecartis-version: Ecartis v1.0.0 Sender: lojban-list-bounce@lojban.org Errors-to: lojban-list-bounce@lojban.org X-original-sender: jjllambias@gmail.com Precedence: bulk Reply-to: lojban-list@lojban.org X-list: lojban-list On Fri, Dec 19, 2008 at 1:33 PM, Michael Turniansky wrote: > > This is a very interesting argument. I've never considered trying to > glean meaning from how something parses, and I doubt that anyone can. You can tell many things from the parse tree. For example, the grammar is explicitly constructed so that {ko'a .e ko'e .a ko'i} will parse as {(ko'a .e ko'e) .a ko'i} and {ko'a .e ko'e .a bo ko'i} will parse as {ko'a .e (ko'e .a bo ko'i)}. There was no need to do it that way. In fact, the grammar would be simpler, fewer rules, if it didn't care about getting such groupings right. > Can > you tell me how "smaji" differs from "ganra" by how they parse? No, the formal grammar will only tell you that they are both of "selma'o" BRIVLA. (In fact it will also recognize they are both gismu, but that's morphology.) The syntax won't tell you anything about the meaning, which comes from the dictionary. The syntax won't distinguish between the meanings of {na} and {ja'a} either, they are just members of NA. But it can inform you about their scope. > The best > you can do is tell me that they are both three-argument gismu. Not even that. The number of arguments is the same for all BRIVLA as far as the grammar is concerned: every brivla accepts an infinite (or indefinite) number of arguments. > "Na" is > forced by the grammar to be right before a selbri (or connective. Any other > legal places, disregarding UI and the like? I'm not sure). Strictly, it is part of the selbri, and it can alternate with tags, so for example you can have {ba na bai ja'a ro roi ja'a na ja'a ja'a na na vi broda} as one selbri. > But how you can > jump from syntax to meaning is beyond me. The parse tree can be helpful to determine groupings and scopes. Of course you can always define things so the meaning goes against what the syntax suggests, but why do that? > I wish it could be free when > attached to ku, as PU is, without affecting its meaning, but it's not. Why > they made the choice they did to not let it, is beyond me. Because if {naku} always had scope over every other operator, there would be no way of saying such simple things as "some x are not broda". >> (1) su'o da na broda >> >> (3) su'o da ge na broda gi na broda >> >> This can only mean "some x is not broda and is not broda", which >> reduces to "some x is not broda". > > Cute, but that doesn't mean that you can then translate it back as "su'o > da na broda". Right. That's the problem. > There is no hard and fast transforms for > arbitrary logical constructs, Sure there are. Except for the crazy {na} rule, everything else (I mean everything that has a direct correlate in predicate logic) behaves according to relatively simple rules. > any more than, while it is true that "ko'a ge > du su'ore broda gi du su'oci broda" can be transformed into the true > sentence "ko'a du su'oci broda". {su'ore} and {su'oci} are not basic predicate logic operators, although they are easy to define in terms of {su'o} only. (And yes, that transformation happens to be valid.) > Dang!! I said I didn't wish to be sucked back into this discussion that > we already agreed to disagree on, and there we are again, with a wider > audience than last time :-( There are things that are a matter of opinion or aesthetics, and it is perfectly reasonable to disagree about that. For example, I can think that {su'o da na broda gi'e na broda} and {su'o da na broda} having different meanings sucks, and you can think it's perfectly fine. Or, you can think that yes, it sucks, but we're stuck with it and there's nothing to do about it because CLL is written as it is written and we better not change it. We can agree to disagree about all that. But sometimes you seem to challenge not my sense of aesthetics, or my attitude towards some official rule, but some basic rules of logic. You can't really maintain that "There is no hard and fast transforms for arbitrary logical constructs". The whole point of logic is to have hard and fast transforms for arbitrary logical constructs, so that we can determine whether some line of logical reasoning is valid independently of the semantic content of the predicates involved. mu'o mi'e xorxes To unsubscribe from this list, send mail to lojban-list-request@lojban.org with the subject unsubscribe, or go to http://www.lojban.org/lsg2/, or if you're really stuck, send mail to secretary@lojban.org for help.