Received: from mail-yh0-f63.google.com ([209.85.213.63]:33793) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1YtRYP-000275-Nv for lojban-beginners-archive@lojban.org; Fri, 15 May 2015 19:10:32 -0700 Received: by yhl29 with SMTP id 29sf33425017yhl.1 for ; Fri, 15 May 2015 19:10:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:message-id:subject:mime-version:content-type :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe; bh=tsheYSjTV+wiMWuqzoLSx6YuKfSxDhZM87P8XNOnCRQ=; b=q9J+cjAvrf53pGcaEjziojl85dq70lkhUXFv8Xcl1qlfUCowgkHXiWbEgLKpLP8C8u OodaoLjSV5G07/JHddhliRuUEbn5wpj7+/8hcIk34VFHWQWGE7Z/aTAI7vFKOiYo7ikj LP58W5lN2AZbsBYocSs7W+nf2Bkm0koaz6DCcRE2Ge7F7BQl7vRkLXGvkJq6vp7GZVfh c2LQoGARB6hlLVimytisIItbsReJirueJS3sTBOstkK1Y7yQVbycC6hJM7FLK0C/rnP0 hpXLKQMBOhu1ohuWHPdAZ0a+CfqyoLeBqhCG0kvAIHB1q44lBs9o/R6iXwCYljsoKJFK Ec7g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:subject:mime-version:content-type :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe; bh=tsheYSjTV+wiMWuqzoLSx6YuKfSxDhZM87P8XNOnCRQ=; b=bwfWkKog2Rjhi3BwpExeuXs+0RbDAfWd6ImWBXru+9QWfbTEA/AD8YJlHnJY8rbD+z rSS9Xo7xImvlMUjd3GGIfdD4OmcXekTqziIYlB2eaNWdUoI2E0cxhcbg7sm1PBAUEig9 RJ3QXU0qrhSYDjLPxwImIzphnkcABdrD+/kIKagBmjKBx6PfWuuxanNPbDnzsgTK8b7F lhgOOHWhEu3OIgSxuHttmUypZ9Ng2Rc2X4OerTdDwBX9/Wk+OmdlTrtFMWBi/nv/6vXd s3+tKfxy5n+kyQ6scNtx17uSuqDYL1xw8Z3AkYFZRKNbYXmcu395h5Cj6B22ViImD0bC /z6Q== X-Received: by 10.140.23.50 with SMTP id 47mr219838qgo.24.1431742211531; Fri, 15 May 2015 19:10:11 -0700 (PDT) X-BeenThere: lojban-beginners@googlegroups.com Received: by 10.140.21.165 with SMTP id 34ls1981166qgl.36.gmail; Fri, 15 May 2015 19:10:10 -0700 (PDT) X-Received: by 10.140.99.44 with SMTP id p41mr213960qge.3.1431742210928; Fri, 15 May 2015 19:10:10 -0700 (PDT) Date: Fri, 15 May 2015 19:10:10 -0700 (PDT) From: TR NS To: lojban-beginners@googlegroups.com Message-Id: <7246a2f2-8fe9-4db2-b104-c825409e634a@googlegroups.com> Subject: [lojban-beginners] Does the argument limit lead to half-ass words? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1139_498372610.1431742210383" X-Original-Sender: transfire@gmail.com Reply-To: lojban-beginners@googlegroups.com Precedence: list Mailing-list: list lojban-beginners@googlegroups.com; contact lojban-beginners+owners@googlegroups.com List-ID: X-Google-Group-Id: 300742228892 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -2.2 (--) X-Spam_score: -2.2 X-Spam_score_int: -21 X-Spam_bar: -- Content-Length: 7200 ------=_Part_1139_498372610.1431742210383 Content-Type: multipart/alternative; boundary="----=_Part_1140_962232970.1431742210383" ------=_Part_1140_962232970.1431742210383 Content-Type: text/plain; charset=UTF-8 In my recent studies of Lojban (and Loglan) I've started to question the efficacy of the argument system. One the things that struck me was the word for "run". barja x1 runs on x2 using limbs x3 with gait x4 That seems a strange definition. I can't really think of single time I ever needed to express that the running was done with anything other then legs. Perhaps it would be useful when talking about Oscar Pistorius Olympic races, but that's a rather rare case! When I think of running, it tends to be *to* some place or at least *via* some path. The word "barja" really doesn't seem like the idea of running. It seems more akin to "treading", as in "running on a tread mill", since the definition has no arguments whatsoever for origin or destination. But I suspect that is not what the definer really had in mind. I think rather, those arguments were left out (as if we could sensibly talk about running without them) because the definition needed to stay under five arguments and the definer already knew that a lujvo could be formed with "klama". And so we find the word "bajykla". bajykla k1 runs to destination k2 from origin k3 via route k4 using limbs b3 with gait b4 This word strikes me as what running is really all about. But notice we lost the surface (x2) argument. Moreover, I could easily imagine an additional speed argument. That lead me to wonder if the ordinal argument system is really sufficient. "Running" is a concept and everything that can be reasonably associated with the concept should be accounted for in the possible arguments. While it's kind of neat how "bajykla" can be composed form "barja" and "klama", being *neat* isn't high in my list of criteria for being well defined. On top of this, reading about Modal Tags, that really hammered home to me that the argument system has some holes. I don't see how a well defined predicate could ever make sense with dynamically added arguments. If they made sense they should already be part of the predicate's definition. (Of course, some modals are basically short-cuts for making relative clauses and not so much case tags at all. These stand out b/c they are universally applicable to just about any predicate.) In short, it seems like the limitation of keeping the number of arguments within a small range (generally five) is an arbitrary provision that causes some concepts to be chopped-up into equally arbitrary partial concepts. Of course, the converse issue would be how to handle predicates with potentially a dozen arguments when it is already difficult enough to recall the fourth or fifth? -- You received this message because you are subscribed to the Google Groups "Lojban Beginners" group. To unsubscribe from this group and stop receiving emails from it, send an email to lojban-beginners+unsubscribe@googlegroups.com. To post to this group, send email to lojban-beginners@googlegroups.com. Visit this group at http://groups.google.com/group/lojban-beginners. For more options, visit https://groups.google.com/d/optout. ------=_Part_1140_962232970.1431742210383 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
In my recent studies of Lojban (and Loglan) I've started t= o question the efficacy of the argument system. One the things that struck = me was the word for "run".

    barja x1 ru= ns on x2 using limbs x3 with gait x4 

That se= ems a strange definition. I can't really think of single time I ever needed= to express that the running was done with anything other then legs. Perhap= s it would be useful when talking about Oscar Pistorius Olympic r= aces, but that's a rather rare case! When I think of running, it tends to b= e *to* some place or at least *via* some path. The word "barja" really does= n't seem like the idea of running. It seems more akin to "treading", as in = "running on a tread mill", since the definition has no arguments whatsoever= for origin or destination.

But I suspect that is = not what the definer really had in mind. I think rather, those arguments we= re left out (as if we could sensibly talk about running without them) becau= se the definition needed to stay under five arguments and the definer alrea= dy knew that a lujvo could be formed with "klama". And so we find the word = "bajykla".

    bajykla k1 runs to destin= ation k2 from origin k3 via route k4 using limbs b3 with gait b4

This word strikes me as what running is really all about. But notic= e we lost the surface (x2) argument. Moreover, I could easily imagine an ad= ditional speed argument.

That lead me to wonder if= the ordinal argument system is really sufficient. "Running" is a concept a= nd everything that can be reasonably associated with the concept should be = accounted for in the possible arguments. While it's kind of neat how "bajyk= la" can be composed form "barja" and "klama", being *neat* isn't high in my= list of criteria for being well defined.

On top o= f this, reading about Modal Tags, that really hammered home to me that the = argument system has some holes. I don't see how a well defined predicate co= uld ever make sense with dynamically added arguments. If they made sense th= ey should already be part of the predicate's definition. (Of course, some m= odals are basically short-cuts for making relative clauses and not so much = case tags at all. These stand out b/c they are universally applicable to ju= st about any predicate.)

In short, it seems like t= he limitation of keeping the number of arguments within a small range (gene= rally five) is an arbitrary provision that causes some concepts to be chopp= ed-up into equally arbitrary partial concepts.  Of course, the convers= e issue would be how to handle predicates with potentially a dozen argument= s when it is already difficult enough to recall the fourth or fifth?
<= div>

--
You received this message because you are subscribed to the Google Groups &= quot;Lojban Beginners" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lo= jban-beginners+unsubscribe@googlegroups.com.
To post to this group, send email to lojban-beginners@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban-beginners.
For more options, visit http= s://groups.google.com/d/optout.
------=_Part_1140_962232970.1431742210383-- ------=_Part_1139_498372610.1431742210383--