Received: from mail-wi0-f191.google.com ([209.85.212.191]:34722) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XiVRR-0005Ur-Rv for lojban-list-archive@lojban.org; Sun, 26 Oct 2014 14:33:42 -0700 Received: by mail-wi0-f191.google.com with SMTP id q5sf345243wiv.18 for ; Sun, 26 Oct 2014 14:33:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to: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:content-type; bh=iOmYdzpsUjUQXAqdgDSs+w538z+CW5Jz/YNjZGppbjg=; b=Rfiu4nWieN+TIj/mrIs7g49xcLVndnEDFN1VHS+fgcEZr+Ga0AEfSVFFib4mqbAwXr Nc3MJUrZ4AyMwpsLXE8iZxPNHNWo88F8FiQ5Gzj8bncBj8Xm7x+r3xO+3LeEKspCgl5u 61IDQuZ458P3Ho0efoWN9wcDmsYkYlHnZKEj0Y0bqoQLxKR658nd2BQRo+M96cnj/Z98 vnrXHbItNv+Y/gb8BZstsEpY7lHbx1fRY60ZDNLMHwraasU1jsP+A7C36FLFHvr+74f8 ITL7VcQ8q9UVN6t05+ARz7gNhTONT2QQIOT7ouOOaRtAmNPVE/5m52mJr/b2Eqmsb9wE UkBQ== X-Received: by 10.180.77.227 with SMTP id v3mr53475wiw.11.1414359210448; Sun, 26 Oct 2014 14:33:30 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.180.106.6 with SMTP id gq6ls390936wib.3.canary; Sun, 26 Oct 2014 14:33:29 -0700 (PDT) X-Received: by 10.180.83.134 with SMTP id q6mr3168118wiy.7.1414359209836; Sun, 26 Oct 2014 14:33:29 -0700 (PDT) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com. [2a00:1450:400c:c00::234]) by gmr-mx.google.com with ESMTPS id cy3si395423wib.2.2014.10.26.14.33.29 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 Oct 2014 14:33:29 -0700 (PDT) Received-SPF: pass (google.com: domain of ilmen.pokebip@gmail.com designates 2a00:1450:400c:c00::234 as permitted sender) client-ip=2a00:1450:400c:c00::234; Received: by mail-wg0-f52.google.com with SMTP id y10so1809622wgg.11 for ; Sun, 26 Oct 2014 14:33:29 -0700 (PDT) X-Received: by 10.180.103.33 with SMTP id ft1mr16659468wib.71.1414359209748; Sun, 26 Oct 2014 14:33:29 -0700 (PDT) Received: from [192.168.0.102] ([37.252.206.11]) by mx.google.com with ESMTPSA id l5sm9661038wif.3.2014.10.26.14.33.25 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Oct 2014 14:33:28 -0700 (PDT) Message-ID: <544D68A0.8000402@gmail.com> Date: Sun, 26 Oct 2014 22:33:20 +0100 From: Ilmen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: lojban@googlegroups.com Subject: Re: [lojban] Re: tersmu 0.2 References: <20141015005542.GC3713@gonzales> <20141018004531.GE20049@gonzales> <20141018180946.GF20049@gonzales> <20141018233648.GA29040@gonzales> <20141021010639.GB11705@gonzales> <20141022002214.GD25753@gonzales> In-Reply-To: <20141022002214.GD25753@gonzales> X-Original-Sender: ilmen.pokebip@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ilmen.pokebip@gmail.com designates 2a00:1450:400c:c00::234 as permitted sender) smtp.mail=ilmen.pokebip@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com 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: , Content-Type: text/plain; charset=UTF-8; format=flowed X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - On 22/10/2014 02:22, Martin Bays wrote: > } {fi'o} is maybe a little too vague for your purpose; I'd suggest {broda > } xoi ke'a ca'e du fo'a} which > } would be semantically equivalent to {lo du'u broda ku ca'e du fo'a}, if > } I'm not mistaken. > > Is {broda xoi xo'i [tag] ke'a} not equivalent to {[tag] broda}? Not really. {fi'o broda xy} has a rather vague semantic, it's not clear how the bridi is related to the fact/event of "xy broda". Often the bridi goes in some abstraction place of the fi'o-predicate (like with {ca}, {ki'u}...), but that's not always the case: {ka'a} is based on {fi'o klama}, and {klama} has no abstraction sumti place where the main bridi could go. Arguably the bridi could go into klama2 or klama3, but that doesn't seem to be the intended meaning when using {ka'a}. I'd interpret {broda se ka'a xy} as {broda xoi fasnu fa ke'a jo'u lo nu xy se klama} ~= {fasnu fa lo nu broda jo'u lo nu xy se klama}, or something like this. Therefore I wouldn't say that {broda se ka'a do} = {broda xoi ke'a klama do}, which means "it's brodaing, which is coming to you" (that's probably not the intended meaning). However I think {fi'o xo'i TAG} = {TAG}, by definition. {xo'i}'s purpose is to allow using directly the predicates that are underlying sumtcita whose associated predicate hasn't any Lojban predicate word (e.g. {pu'i}, {nu'o}, {za'o} and the like). However I'm not fond of {xo'i}, I'd rather prefer the missing sumtcita predicates to be given a real predicate word and be done with it. :) mu'o mi'e la .ilmen. -- You received this message because you are subscribed to the Google Groups "lojban" group. To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/d/optout.