Received: from mail-la0-f55.google.com ([209.85.215.55]:34399) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.85) (envelope-from ) id 1ZMk3z-0002Vd-Ns for lojban-list-archive@lojban.org; Tue, 04 Aug 2015 14:48:00 -0700 Received: by labqg3 with SMTP id qg3sf6030804lab.1 for ; Tue, 04 Aug 2015 14:47:52 -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:content-type:content-transfer-encoding :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:sender:list-subscribe:list-unsubscribe; bh=OJ0hOwCu8rEf6WsURH60ST5Ty9hN9N+aWUmxDXWoC74=; b=wViG4EirdEt5XnIS5fquCEjkDWAhnG50SpI5HSE1NHw/abE/iMXmfFGTQXcbvIK5N+ WqP2bIhkhuY/xZdWSeW3VMAFEN7VCeFCRVP1bl/nf62yyKLnIgrxquKUnjRu6bQA4yHv VGwEc0UKpAbRN5Xldbg4J4e1/rBTiO+P2d6brxHzR9Wy6ev3WCZL/CG1uGFIdFvyWvSo Im8yuLDVjQgnfbkp4WeF10+yd15CL8LTjzHrL7uGDPm5FJ93IjGti7GG3E+s4YcGcfjw QgjH04IZI+Wb7J+3R4We5Ne1ykMmAZX+DWCCkKgegtbLWfC+mEf/xnr8C3yaJiV0A6PN SkrQ== X-Received: by 10.152.26.167 with SMTP id m7mr48864lag.12.1438724872734; Tue, 04 Aug 2015 14:47:52 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.152.18.137 with SMTP id w9ls103108lad.102.gmail; Tue, 04 Aug 2015 14:47:51 -0700 (PDT) X-Received: by 10.152.1.105 with SMTP id 9mr1724777lal.3.1438724871843; Tue, 04 Aug 2015 14:47:51 -0700 (PDT) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com. [2a00:1450:400c:c05::234]) by gmr-mx.google.com with ESMTPS id bk2si158503wib.1.2015.08.04.14.47.51 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Aug 2015 14:47:51 -0700 (PDT) Received-SPF: pass (google.com: domain of ilmen.pokebip@gmail.com designates 2a00:1450:400c:c05::234 as permitted sender) client-ip=2a00:1450:400c:c05::234; Received: by mail-wi0-x234.google.com with SMTP id ud3so40917402wib.0 for ; Tue, 04 Aug 2015 14:47:51 -0700 (PDT) X-Received: by 10.194.187.40 with SMTP id fp8mr12141674wjc.34.1438724871758; Tue, 04 Aug 2015 14:47:51 -0700 (PDT) Received: from [192.168.0.102] (95-210-222-65.ip.skylogicnet.com. [95.210.222.65]) by smtp.googlemail.com with ESMTPSA id bu12sm842306wjb.44.2015.08.04.14.47.47 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Aug 2015 14:47:50 -0700 (PDT) Message-ID: <55C132F0.20008@gmail.com> Date: Tue, 04 Aug 2015 23:47:28 +0200 From: Ilmen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: lojban@googlegroups.com Subject: Re: [lojban] xoi and new soi as bridi relative clause References: <1c2a3b64-07b1-4023-a740-362deb17da34@googlegroups.com> <55AD070D.5020903@gmx.de> <55AE1142.5090807@gmx.de> <8bab9435-5f94-4742-b74a-8cceac2c8a60@googlegroups.com> <55AE616F.9040509@gmx.de> In-Reply-To: <55AE616F.9040509@gmx.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable 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:c05::234 as permitted sender) smtp.mail=ilmen.pokebip@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-Spam-Checked-In-Group: lojban@googlegroups.com X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -1.7 (-) X-Spam_score: -1.7 X-Spam_score_int: -16 X-Spam_bar: - Actually I'm not sure anymore which of those {xoi} should be. Initially=20 I made this particle as a better and more precise alternative to {fi'o},=20 that would parallel NOI in syntax and enable rewording any sumtcita tag=20 as a xoi-phrase. However it's turning out that maybe there are two=20 distinct and mutually exclusive categories of sumtcita cmavo, namely=20 subordinating sumtcita (ka'e, ka'enai=E2=80=A6), whose host bridi's truth v= alue=20 depends on the sumtcita's meaning, versus realis/non-subortinating=20 sumtcita (ri'a, ri'anai=E2=80=A6), whose host bridi's truth value is indepe= ndent=20 from the sumtcita's, so that there couldn't exist an all-encompassing=20 cmavo for turning any predicate into the semantic equivalent of any=20 sumtcita clause. Here is the basis for supposing that sumtcita can be split into two=20 categories, depending on whether they affect the truth value of the=20 outer bridi that hosts them so they couldn't be removed without changing=20 the sentence's meaning: NON-SUBORDINATING/INDEPENDENT TAGS: =E2=80=A2 {mi sipna ri'a lo nu tatpi} entails {mi sipna}. =E2=80=A2 {mi sipna ri'a nai lo nu tatpi} entails {mi sipna}. =E2=80=A2 {mi citka se pi'o lo forca} entails {mi citka}. =E2=80=A2 {snime carvi ca nai lo nu critu} entails {snime carvi}. SUBORDINATING TAGS: =E2=80=A2 {mi sipna ka'e} doesn't entail {mi sipna}. =E2=80=A2 {mi sipna ka'e nai} doesn't entail {mi sipna}. =E2=80=A2 {mi sipna na ku} doesn't entail {mi sipna}. =E2=80=A2 {mi sipna va'o lo nu tatpi} doesn't seem to entail {mi sipna} in= =20 modern mainstream usage. So it seems two versions of {xoi} would be needed for covering all these=20 cases. This also raises the question of whether {fi'o} is subordinating, i.e.=20 whether {mi sipna fi'o se cumki} entails {mi sipna} or not. mi'e la .ilmen. mu'o On 21/07/2015 17:12, selpa'i wrote: > la .guskant. cu cusku di'e >> (D) ma'a ca ro xavdei lo ka vokta'a cu simxu, soi ku'i na ku=20 >> ro da >> poi jbopre zo'u lo nu da pagzu'e ke'a cu dikni >> "On every Saturday we have vocal chats, which however is=20 >> such >> that not every Lojbanist is such that their taking part in them=20 >> occurs >> regularly." >> >> No problem here. My main problem was this: >> what if some xoi-clauses and soi-clauses in a sentence have each prenex? >> which prenex will be regarded as outmost? >> >> However, considering (D), I understood the logical property of >> xoi/soi-clause. >> They are statements independent of the main bridi. Logically, {soi}, >> {xoi} and {se'u} plays the same role as {to} {toi}. > > This may be true for {soi}, but I'm not at all sure it's true for=20 > {xoi}. There are two options for {xoi}: it's either restrictive or=20 > non-restrictive. If it is one of the two, then we don't have a word=20 > for the other and vice versa. There should really be two {xoi}. Let's=20 > call them {Pxoi} and {Nxoi}. There is an important difference between=20 > (E) and (F): > > (E) so'i verba cu krixa Pxoi fanza > "Many children are yelling annoyingly." > (There may be children there whose yelling isn't annoying) > > (F) so'i verba cu krixa Nxoi fanza > "Many children are yelling, which is annoying." > (Every yelling child is annoying) > > Which one is {xoi} supposed to be? > > mi'e la selpa'i mu'o > --=20 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 e= mail 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.