Return-Path: X-Sender: lojban-out@lojban.org X-Apparently-To: lojban@yahoogroups.com Received: (qmail 9152 invoked from network); 15 Aug 2005 19:29:12 -0000 Received: from unknown (66.218.66.218) by m22.grp.scd.yahoo.com with QMQP; 15 Aug 2005 19:29:12 -0000 Received: from unknown (HELO chain.digitalkingdom.org) (64.81.49.134) by mta3.grp.scd.yahoo.com with SMTP; 15 Aug 2005 19:29:11 -0000 Received: from lojban-out by chain.digitalkingdom.org with local (Exim 4.52) id 1E4kdu-0002pg-Rg for lojban@yahoogroups.com; Mon, 15 Aug 2005 12:29:07 -0700 Received: from chain.digitalkingdom.org ([64.81.49.134]) by chain.digitalkingdom.org with esmtp (Exim 4.52) id 1E4kcp-0002nF-Et; Mon, 15 Aug 2005 12:28:02 -0700 Received: with ECARTIS (v1.0.0; list lojban-list); Mon, 15 Aug 2005 12:27:51 -0700 (PDT) Received: from nobody by chain.digitalkingdom.org with local (Exim 4.52) id 1E4kcX-0002n3-Q0 for lojban-list-real@lojban.org; Mon, 15 Aug 2005 12:27:41 -0700 Received: from [208.234.8.229] (helo=intelligenesiscorp.com) by chain.digitalkingdom.org with esmtp (Exim 4.52) id 1E4kcQ-0002mm-HI for lojban-list@lojban.org; Mon, 15 Aug 2005 12:27:41 -0700 Received: from zombiethustra (pcp06586041pcs.nrockv01.md.comcast.net [69.140.24.121]) by intelligenesiscorp.com (8.12.10/8.12.10) with SMTP id j7FJRKTN006005; Mon, 15 Aug 2005 15:27:24 -0400 Cc: "Ari Heljakka" , "Izabela Lyon Freire Goertzel" Date: Mon, 15 Aug 2005 15:27:16 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20050815190210.88870.qmail@web81305.mail.yahoo.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-Spam-Score: -2.6 (--) X-archive-position: 10374 X-ecartis-version: Ecartis v1.0.0 Errors-to: lojban-list-bounce@lojban.org X-original-sender: ben@goertzel.org X-list: lojban-list X-Spam-Score: -2.6 (--) To: lojban@yahoogroups.com X-Originating-IP: 64.81.49.134 X-eGroups-Msg-Info: 1:12:0:0 X-eGroups-From: "Ben Goertzel" From: "Ben Goertzel" Reply-To: ben@goertzel.org Subject: [lojban] Re: Loglish: A Modest Proposal X-Yahoo-Group-Post: member; u=116389790; y=YbGXaG-kBLXQOzuS26Agj5h413FxH6Vo95gOR29CLDspIaqAFw X-Yahoo-Profile: lojban_out X-Yahoo-Message-Num: 24752 Content-Length: 4726 Lines: 129 > I assume that -- as is usual with > AI prospectuses -- as these problems are pointed > out, devices will be found (or at least claimed) > to deal with them. Yes -- I explicitly stated that my posting on Loglish was just a preliminary idea-sketch and not a fully-fleshed-out, rigorous proposal. I posted my preliminary ideas in order to get feedback from others, which I am getting, and I much appreciate it... If Loglish actually takes off (e.g., if I implement or convince someone else to implement a parser for it) then I will take discussion of it off this mailing list and onto another list, since I realize this is a list for discussing Lojban not Loglan, Loglish or other Lojban-related languages. However, this list seemed the best place for tossing around ideas about Loglish. At least, the people on this list seem to know what the hell I'm talking about, whereas when I floated the idea on an AI-related list I got no reply but general dumbfoundedness... ;-) > Fow now (as usual, agqin) we > are left with a good display and unremarked > amounts of pre-editing, post-editing and just > plain cheating in the middle. Of the latter, I > note that neither "murder" nor "kill," its > supposed surrogate, is three-placed in English "Kill" is not three-placed in English *syntax*, but it has more than one argument in English *semantics*. For instance, FrameNet http://framenet.icsi.berkeley.edu/index.php gives the following case-roles associated with the English verb "kill": use Core --------------------------- Degree Peripheral Depictive Extra-Thematic Instrument Peripheral Killer Core Manner Peripheral Means Peripheral Place Peripheral Purpose Extra-Thematic Reason Extra-Thematic Result Extra-Thematic Time Peripheral Victim Core Just as I'd suggest WordNet as the standard reference for Loglish word-senses, I'd suggest FrameNet as the standard reference for Loglish argument-structures. In this case "instrument" maps into the FrameNet argument slot called "Instrument" > ("He killed her a knife" is not English -- or, > rather, means that he bagged a wild knife for > her) and neither is connected with conflict or > violence to make a connection with "weapon," so > the analysis does not go off as it appears to in > the text. That does not mean it does not go off, > of course, but it must be more complex (and > possibly more ad hoc) than suggested. Lacking a > quick connection between "murder" and "plier quu > weapon" one wonders how to keep this from being > "Ben murdered the chicken who had a plier." Because the parser (be it a computer parser or the parser in the mind of the human Loglish-listener) sees "plier quu weapon" and then has the job of matching "weapon" with one of the argument-slots of kill according to FrameNet. Out of all these argument-slots, it has to figure out that "weapon" matches "instrument" better than any of the others. Of course, the parser's job is even easier if the speaker uses "pliers quu instrument" i.e. if the speaker is a bit familiar with FrameNet lingo, but I gave "pliers quu weapon" as an example just to show that there's some room for improvisation/sloppiness on the speaker's part. > Presumably Loglish must have some way of marking > off modification of arguments from modification > of the main predicate. Given the paucity of > reference to Lojban, it is not clear what it > might be (it probably can't be the Lojban device > with {be}, given the conflict with English "be." The English word "be" wouldn't exist in Loglish, nor would any other English "helping" or "being" verbs. This was not explicitly stated in my brief initial Loglish document, but it should have been. As I did say in my document, I assume that *all Lojban cmavo* (including "be") are supposed to be carried over into Loglish. I screwed up by mistakenly leaving out "la", "cu" and "lo" in the Loglish example I emailed out last night, but Jorge fortunately corrected this silly error on my part. > I think the practical issues motivating this > suggestion have real merit; I just don't think it > concerns Lojban (nor -- yet -- predicate logic). No insights into predicate logic are likely to come from Lojban or Loglish; both languages are intended to serve as front ends to predicate logic... As to the irrelevance to Lojban -- well, if this discussion is generally annoying people, I can take it off this list. But for the moment, I at least am enjoying and benefiting from the responses ;-) -- Ben G 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.