From a.rosta@lycos.co.uk Wed Apr 30 16:32:12 2003 Received: with ECARTIS (v1.0.0; list lojban-list); Wed, 30 Apr 2003 16:32:13 -0700 (PDT) Received: from lmsmtp02.st1.spray.net ([212.78.202.112]) by digitalkingdom.org with esmtp (Exim 4.12) id 19B13W-00066w-00 for lojban-list@lojban.org; Wed, 30 Apr 2003 16:32:06 -0700 Received: from oemcomputer (host81-7-56-109.surfport24.v21.co.uk [81.7.56.109]) by lmsmtp02.st1.spray.net (Postfix) with ESMTP id 402835B68D; Thu, 1 May 2003 01:31:32 +0200 (MEST) From: "And Rosta" To: , Subject: [lojban] Re: nai in UI (was: BPFK phpbb) Date: Thu, 1 May 2003 00:30:20 +0100 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.2910.0) In-Reply-To: X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal X-archive-position: 5072 X-ecartis-version: Ecartis v1.0.0 Sender: lojban-list-bounce@lojban.org Errors-to: lojban-list-bounce@lojban.org X-original-sender: a.rosta@lycos.co.uk Precedence: bulk Reply-to: lojban-list@lojban.org X-list: lojban-list jimc: > On Wed, 30 Apr 2003, And Rosta wrote: > > I have no problem with the Formal Grammar or Official Parser passing > > nonsense. But any truly well-formed sentence of Lojban must be meaningful, > > however silly or surreal that meaning is. A true parser will recognize > > which strings are and aren't meaningful. A parser that ignores meaning > > is nonsense, in the sense that it produces nothing useful > > Hey, wait a minute! Think modularity. There are morpheme streams that can > or can't be split into valid Lojban words. There are word streams that can > or can't be parsed into valid syntax trees. But I opine that a syntax tree is valid only if it is the syntax tree of some sentence, and since a sentence is a pairing of a sound and a meaning, a syntax tree is valid only if it yields a meaning. > And there are semantic > constructs that are or aren't Carroll-esque. The phrase "meaningful > concept" is too vague to be a meaningful concept. I contend (a) that if we are dealing with language then we have to engage with this notion of meaningfulness, since language is intrinsically meaningful -- if you don't have meaning then you don't have language -- and (b) that a logical language like Lojban ought to spend a lot of energy on firming up the definition of meaningfulness (e.g. a well-formed logical formula, augmented by extralogical stuff like attitudinality etc.). > I would like to amend > your pronouncement to say, a valid parser passes all valid word streams > (putting out a correct syntax tree) and rejects all invalid word streams, > where validity is judged from the grammar. In other words, the parser does > or doesn't truly realize that grammar. (I.e. makes it real.) (And as a > separate module, the semantic analyser may have an opinion about > jabberwockishness.) > > I'm sure we can come up with natlang examples where the parsing depends in > an essential way on the meaning of the words (not just their syntactic > category), but I can't think of one so early in the morning. Perhaps such examples or their lack is in the eye of the beholder. At any rate, my view is that in every sentence the meaning results from the parse -- the very function of the parse is to build the meaning. > But that kind > of a pain in the butt doesn't belong in Lojban. Think modularity! But what is the purpose of this particular module? A language needs a module that builds well-formed logical formula from lexical primitives. I see no useful role for this putative module that is blind to meaning. --And.