Received: from mail-gg0-f189.google.com ([209.85.161.189]:36420) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1SvrF3-0005fa-Ux; Mon, 30 Jul 2012 07:46:55 -0700 Received: by ggke5 with SMTP id e5sf6538503ggk.16 for ; Mon, 30 Jul 2012 07:46:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:x-yahoo-newman-property:x-yahoo-newman-id :x-ymail-osg:x-mailer:references:message-id:date:from:reply-to :subject:to:in-reply-to:mime-version:x-original-sender :x-original-authentication-results:precedence:mailing-list:list-id :x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type; bh=McB6+pgSd0E35xrF0S2mmJg4H9IglkyhRte9bDpDPLE=; b=vjGlN1LoWXXE9Gf2BzQRLxxkmX7Z+0efFsl3fjTbD8/Fp42pEe7KNPE4Qfwrmbwusc eSCRkBHv9qx4K/ayhXf31CgOd7uU+MXNCLfhT3p0O0N5tB9Qa2O0FVJYfsoh40HKwgii je9vOEpF5KN73B4PrZps1YnN3SbFVMiS+o1D0= Received: by 10.50.187.136 with SMTP id fs8mr1546149igc.2.1343659595146; Mon, 30 Jul 2012 07:46:35 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.231.62.136 with SMTP id x8ls4102580ibh.7.gmail; Mon, 30 Jul 2012 07:46:33 -0700 (PDT) Received: by 10.42.132.5 with SMTP id b5mr4528370ict.7.1343659593389; Mon, 30 Jul 2012 07:46:33 -0700 (PDT) Received: by 10.42.132.5 with SMTP id b5mr4528369ict.7.1343659593370; Mon, 30 Jul 2012 07:46:33 -0700 (PDT) Received: from nm9.bullet.mail.ne1.yahoo.com (nm9.bullet.mail.ne1.yahoo.com. [98.138.90.72]) by gmr-mx.google.com with SMTP id ev10si2317992igc.2.2012.07.30.07.46.33; Mon, 30 Jul 2012 07:46:33 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 98.138.90.72 as permitted sender) client-ip=98.138.90.72; Received: from [98.138.226.177] by nm9.bullet.mail.ne1.yahoo.com with NNFMP; 30 Jul 2012 14:46:33 -0000 Received: from [209.191.108.96] by tm12.bullet.mail.ne1.yahoo.com with NNFMP; 30 Jul 2012 14:46:32 -0000 Received: from [66.94.237.100] by t3.bullet.mud.yahoo.com with NNFMP; 30 Jul 2012 14:46:32 -0000 Received: from [127.0.0.1] by omp1005.access.mail.mud.yahoo.com with NNFMP; 30 Jul 2012 14:46:32 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 706195.32839.bm@omp1005.access.mail.mud.yahoo.com Received: (qmail 80866 invoked by uid 60001); 30 Jul 2012 14:46:31 -0000 X-YMail-OSG: 39cS2wkVM1kCMDXBr.5Z8yJYfKSKUYMYQPxdYwhhMp5aOhL FHEKcLKZ8DMc8zdngHp9p6uxiR9QwAP9n5WMfGk0OLP8dqrTYdFNOHgEzhnB yAE3bzxOx9dlUWLL6Q3LDeHWCvc5MS8VnAkFqOn9ZvIfX0CwMa0CFnH.Al.3 pffBh3G9c3iAvuDQGKbhqritZ4YFEJxyc5DIeRny.wMlIXSp3SockXpVr.tm 9S2HzilLD7MPtYuUoVWWVobOXgYxr_75EcBt0bPp8prqiN0ZgQzeKbbESd2S SWxbeXCTgV9.1Ybk.yzuY8ZEUWIm7UatTysm3R9oj6QgwEpMYn5Tt1bAKWLG tm_SIcbBBjQzSy12NUmXo.aQWKMqvP44fy3z3dOoamzknAm5TYS8ok0YnMg3 l1WOMrPNpl9J6SgA_1cfaLN05gbiAv77CTFrqptQfo4Pq40al2MjfyLuZz0G ZaeWngSpsAT8Y1.xyQwSIoaauw_CqB7V649odugy9EYWs26EDrUOs7FH2owR _rGuxamimjQIrQlujrjHJitz0K22IP_8v2dwhwzLZ_WjuGQTg4Ilf3P_j4ok dEvp7z9pIk7.vucpAhbC1pYC8KdzT.uyzqsY0qWr2xQdg Received: from [99.92.108.194] by web184406.mail.bf1.yahoo.com via HTTP; Mon, 30 Jul 2012 07:46:31 PDT X-Mailer: YahooMailWebService/0.8.120.356233 References: Message-ID: <1343659591.78422.YahooMailNeo@web184406.mail.bf1.yahoo.com> Date: Mon, 30 Jul 2012 07:46:31 -0700 (PDT) From: John E Clifford Reply-To: lojban@googlegroups.com Subject: Re: [lojban] Afterthought TAG Termset Connectives To: "lojban@googlegroups.com" In-Reply-To: MIME-Version: 1.0 X-Original-Sender: kali9putra@yahoo.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 98.138.90.72 as permitted sender) smtp.mail=kali9putra@yahoo.com; dkim=pass (test mode) header.i=@yahoo.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: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary="1789658926-216652670-1343659591=:78422" X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / --1789658926-216652670-1343659591=:78422 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Relevant to another thread, I notice that in posing and attempting to solve= these sorts of problems, y'all regularly have implicit appeal to transform= ational grammars of one sort or another. ________________________________ From: Jacob Errington To: lojban@googlegroups.com=20 Sent: Monday, July 30, 2012 7:26 AM Subject: [lojban] Afterthought TAG Termset Connectives =20 Do these exist? The forethought version is grammatical: {.i nu'i ca gi zo .u'i ny nu'u gi zo .i'i cy selsku} Considering that afterthought TAG connectives take the form of <[connective= ] TAG bo> where [connective] is the connective of the appropriate connectiv= e selma'o, e.g. {mi .e ca bo do}, I would presume that the afterthought ter= mset connective form would be <[sumti] pe'e je TAG bo [sumti]> where [sumti= ] is >=3D1 sumti. Unfortunately, of course, this does not parse in jbofi'e. Additionally, it would appear as though TAG connectives such as {.e ca bo} = are not valid utterances by themselves, whereas bare connectives such as {.= e} are. I'm not sure that this is desirable, but it does make it impossible= to answer {ji}-questions and such with tag connectives. I can think of an = example usage inspired by the CLL example of {ji}:=A0 {.i do djica tu'a lo tcati ji lo ckafi} "Would you like tea or coffee?" {.e ba bo} (English sucks for the answer:) "The former, then the latter." (This example is incidentally unaffected by the connective problem that usu= ally arises when using connectives in non-top-level contexts like {tu'a ko'= a .e ko'a}. The problem itself is that it's arguable as to whether {tu'a ko= 'a .e ko'e broda} is equivalent to {tu'a ko'a broda .ije tu'a ko'e broda} -= > {lo su'u ko'a co'e cu broda .ije lo su'u ko'e co'e cu broda} or rather {l= o su'u ko'a .e ko'e co'e cu broda}.=A0 A similar, more drastic case occurs in {lo pendo be mi .e do}, which we'd n= aturally assume is "the friend of both me and you" but it's arguable as to = whether {lo pendo be mi .e do cu broda} is equivalent to {lo pendo be mi cu= broda .ije lo pendo be do cu broda} or {zo'e noi pendo mi .e do cu broda}.= My rationale behind supporting the latter interpretation is that using one= descriptor should only create one description, whereas the former interpre= tation creates two descriptions behind the scenes, namely {lo pendo be mi} = and {lo pendo be do} which could be referring to entirely different things.= =A0Additionally although less importantly, the latter interpretation seems = far more natural, not to mention that to achieve the meaning of the former = interpretation using the latter, one must necessarily employ the {zo'e noi}= construction, which is unnecessarily cumbersome, whereas with the latter i= nterpretation, one must simply repeat {lo pendo} such that {lo pendo be mi ku .e lo pendo be do}. The only apparent downside to the latter inte= rpretation is that when using afterthought, in order to repeat the main des= cription, a lot of terminators might be required, not to mention that if th= e description is fairly complex (a four-part tanru) it can become very anno= ying to repeat it.) Returning to the main point of this post, considering that termsets is a pa= rt of the language that everybody loves to hate, it's unlikely that afterth= ought tag termset connectives will ever see the light of day, but I don't t= hink that the cmavo required for termsets are going to disappear any time s= oon (at least not before mekso, for which there remains proponents.) Theref= ore, I see no reason why this discrepancy between forethought and afterthou= ght should exist. (Not to mention the impossible non-logical bridi-tail aft= erthought connective, which I wanted to use just today...) Could it be that= afterthought tag termset connection was impossible due to a parser limitat= ion? What with the PEG being capable of all sorts of things that the older = grammars weren't, could this be implemented in the current grammar? As far = as I can tell, making {pe'e JA TAG bo} grammatical breaks no usage at all. mu'o mi'e la tsani --=20 You received this message because you are subscribed to the Google Groups "= lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com. For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den. --=20 You received this message because you are subscribed to the Google Groups "= lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com. For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den. --1789658926-216652670-1343659591=:78422 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Relevant t= o another thread, I notice that in posing and attempting to solve these sor= ts of problems, y'all regularly have implicit appeal to transformational gr= ammars of one sort or another.


= From: Jacob Errington <= ;nictytan@gmail.com>
To: lojban@googlegroups.com
Se= nt: Monday, July 30, 2012 7:26 AM
Subject: [lojban] Afterthought TAG Termset Connectiv= es

Do these exist?
The forethought version is gra= mmatical:

{.i nu'i ca gi zo .u'i ny nu'u gi zo .i'= i cy selsku}

Considering that afterthought TAG con= nectives take the form of <[connective] TAG bo> where [connective] is= the connective of the appropriate connective selma'o, e.g. {mi .e ca bo do= }, I would presume that the afterthought termset connective form would be &= lt;[sumti] pe'e je TAG bo [sumti]> where [sumti] is >=3D1 sumti. Unfo= rtunately, of course, this does not parse in jbofi'e.

Additionally, it would appear as though TAG connectives= such as {.e ca bo} are not valid utterances by themselves, whereas bare co= nnectives such as {.e} are. I'm not sure that this is desirable, but it doe= s make it impossible to answer {ji}-questions and such with tag connectives= . I can think of an example usage inspired by the CLL example of {ji}: = ;
{.i do djica tu'a lo tcati ji lo ckafi} "Would you like tea or coffee?= "
{.e ba bo} (English sucks for the answer:) "The former, then th= e latter."

(This example is incidentally unaffecte= d by the connective problem that usually arises when using connectives in n= on-top-level contexts like {tu'a ko'a .e ko'a}. The problem itself is that = it's arguable as to whether {tu'a ko'a .e ko'e broda} is equivalent to {tu'= a ko'a broda .ije tu'a ko'e broda} -> {lo su'u ko'a co'e cu broda .ije l= o su'u ko'e co'e cu broda} or rather {lo su'u ko'a .e ko'e co'e cu broda}.&= nbsp;

A similar, more drastic case occurs in {lo pendo be mi = .e do}, which we'd naturally assume is "the friend of both me and you" but = it's arguable as to whether {lo pendo be mi .e do cu broda} is equivalent t= o {lo pendo be mi cu broda .ije lo pendo be do cu broda} or {zo'e noi pendo= mi .e do cu broda}. My rationale behind supporting the latter interpretati= on is that using one descriptor should only create one description, whereas= the former interpretation creates two descriptions behind the scenes, name= ly {lo pendo be mi} and {lo pendo be do} which could be referring to entire= ly different things. Additionally although less importantly, the latte= r interpretation seems far more natural, not to mention that to achieve the= meaning of the former interpretation using the latter, one must necessaril= y employ the {zo'e noi} construction, which is unnecessarily cumbersome, wh= ereas with the latter interpretation, one must simply repeat {lo pendo} such that {lo pendo be mi ku .e lo pendo be do}. The only apparent = downside to the latter interpretation is that when using afterthought, in o= rder to repeat the main description, a lot of terminators might be required= , not to mention that if the description is fairly complex (a four-part tan= ru) it can become very annoying to repeat it.)

Returning to the main point of this post, considering t= hat termsets is a part of the language that everybody loves to hate, it's u= nlikely that afterthought tag termset connectives will ever see the light o= f day, but I don't think that the cmavo required for termsets are going to = disappear any time soon (at least not before mekso, for which there remains= proponents.) Therefore, I see no reason why this discrepancy between foret= hought and afterthought should exist. (Not to mention the impossible non-lo= gical bridi-tail afterthought connective, which I wanted to use just today.= ..) Could it be that afterthought tag termset connection was impossible due= to a parser limitation? What with the PEG being capable of all sorts of th= ings that the older grammars weren't, could this be implemented in the curr= ent grammar? As far as I can tell, making {pe'e JA TAG bo} grammatical brea= ks no usage at all.

mu'o mi'e la tsani
--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.


--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
--1789658926-216652670-1343659591=:78422--