From nellardo@concentric.net Thu May 18 11:35:59 2000 Return-Path: Received: (qmail 30572 invoked from network); 18 May 2000 18:35:58 -0000 Received: from unknown (10.1.10.142) by m2.onelist.org with QMQP; 18 May 2000 18:35:58 -0000 Received: from unknown (HELO uhura.concentric.net) (206.173.118.93) by mta3 with SMTP; 18 May 2000 18:35:57 -0000 Received: from cliff.concentric.net (cliff.concentric.net [206.173.118.90]) by uhura.concentric.net (8.9.1a/(98/12/15 5.12)) id OAA12132; Thu, 18 May 2000 14:35:49 -0400 (EDT) [1-800-745-2747 The Concentric Network] Errors-To: Received: from concentric.net ([216.112.226.144]) by cliff.concentric.net (8.9.1a) id OAA05192; Thu, 18 May 2000 14:35:41 -0400 (EDT) Message-ID: <392434F3.1BC5C9A4@concentric.net> Date: Thu, 18 May 2000 14:39:56 -0400 Reply-To: nellardo@concentric.net Organization: Herds of Wild Buffalo Girls X-Mailer: Mozilla 4.7 (Macintosh; I; PPC) X-Accept-Language: en MIME-Version: 1.0 To: lojban@egroups.com Subject: Re: [lojban] More on lojban programatic semantics: Strong typing and inferencing of types References: <20000516214537.44864.qmail@hotmail.com> <4.2.2.20000517232539.00b1aac0@127.0.0.1> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Brook Conner X-Yahoo-Message-Num: 2751 lojbab cusku di'e > Not really. The use of "la" means that I have some particular named > "stokuot" in mind. It doesn't imply anything about anyone I am not > discussing. The fact that I use "noi" means that I am presuming that the > listener already has enough information to know who/what "la stokuot" > refers to. Hmm. Okay, I think I see. "noi" is providing additional information, but you know what it is. "poi" is helping you identify it. > > However, most PLs have > >scoping rules that allow multiple things of the same name - the scoping > >makes sure the referent of the name is always unambiguous. > > The use of le or la by a Lojbanist means that he assumes that the referent > is unambiguous to the listener, given context and previous knowledge. If > it is not, then he needs to provide restrictive information to make it > unambiguous Got it. Part of the trick in devising a programmatic semantics is determining *when* the programmer needs to provide more information - what prior context and knowledge does the computer have to remove ambiguities? > >On the other hand, "poi" implies that the characteristic named is an > >*essential* aspect of the thing named - this is much closer to the > >meaning of a type in a PL. > > No. poi information need not be essential to the thing named. > > John, who is the one sitting next to Jane, is my friend. > > would use a poi clause in Lojban. It is not an essential aspect of John > that he sits next to Jane, it merely is a useful way to point him > out. Hmmm, okay. I'm projecting too much of my own prior knowledge of programming languages onto lojban. Types in a PL *are* intrinsic, and often absolutely essential. > Having pointed him out, but noting that the light is dim, I could > add. "John, who has red hair, is tall." and the clause here would be > translated into Lojban with "noi" because you already know who John is, and > this is just incidental information. I think what was tripping me up was the word "incidental" - it implied to me that it could be left out without changing the meaning of the sentence. While this is true for a single sentence, it is not true for a discourse - an incidental description of hair color must be consistent with later descriptions of hair color. Whether the incidental is there or not affects the truth values of later statements in the discourse. Brook