From lojban+bncCJ2UzZHuDRDTt53wBBoEsN5e_w@googlegroups.com Sun Jun 26 09:18:40 2011 Received: from mail-vw0-f61.google.com ([209.85.212.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1Qas2f-0005J2-PF; Sun, 26 Jun 2011 09:18:40 -0700 Received: by vws2 with SMTP id 2sf2661354vws.16 for ; Sun, 26 Jun 2011 09:18:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:x-beenthere:received-spf:mime-version :in-reply-to:references:date:message-id:subject:from:to :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:x-google-group-id:list-post :list-help:list-archive:sender:list-subscribe:list-unsubscribe :content-type:content-transfer-encoding; bh=rJeJsnzUtacCqimJh0+wViRfG2TCHLXoanaqr1ohJX4=; b=HFN30G81aezV918nL1gMu4MC1/4kiWa6up/zx37DF/y4GO6wgn8POktUrJEEi0M/Vi Xvbvvu14GQsNTzW1hTEmHaeoKhJzbphKsXgUkS5jWMYUn6eziJe3VtwSN4qb+PtVGxwb kjtzJkH3Ag7KCC3Pg2EOHjyk2kOQxAZU+FDaI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:in-reply-to:references:date :message-id:subject:from:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type :content-transfer-encoding; b=yFC6MuGyOkZH1luGjfohMfSacw+3vXegYA6RytWF88GN6qVsyCQXQFUFAOwkbfD+NU sd+IV6pNK310rUcNqsscw3UQ7/irSZ/S1XuDXyGXL1qTUF3tgdRIy/kZLtvc6bE4JGU+ BwXP8NUrJmefD+9zX8sLsghhOsj0nm1cFGjqo= Received: by 10.220.49.159 with SMTP id v31mr775772vcf.57.1309105107778; Sun, 26 Jun 2011 09:18:27 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.52.179.138 with SMTP id dg10ls2049633vdc.2.gmail; Sun, 26 Jun 2011 09:18:26 -0700 (PDT) Received: by 10.52.70.242 with SMTP id p18mr1547781vdu.15.1309105106230; Sun, 26 Jun 2011 09:18:26 -0700 (PDT) Received: by 10.52.70.242 with SMTP id p18mr1547780vdu.15.1309105106219; Sun, 26 Jun 2011 09:18:26 -0700 (PDT) Received: from mail-vx0-f170.google.com ([209.85.220.170]) by gmr-mx.google.com with ESMTPS id ch6si3871318vdb.2.2011.06.26.09.18.26 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 26 Jun 2011 09:18:26 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 209.85.220.170 as permitted sender) client-ip=209.85.220.170; Received: by vxi39 with SMTP id 39so3432603vxi.29 for ; Sun, 26 Jun 2011 09:18:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.99.10 with SMTP id em10mr7028100vdb.257.1309105105801; Sun, 26 Jun 2011 09:18:25 -0700 (PDT) Received: by 10.52.107.6 with HTTP; Sun, 26 Jun 2011 09:18:25 -0700 (PDT) In-Reply-To: References: Date: Sun, 26 Jun 2011 13:18:25 -0300 Message-ID: Subject: Re: [lojban] non-ka properties From: =?ISO-8859-1?Q?Jorge_Llamb=EDas?= To: lojban@googlegroups.com X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 209.85.220.170 as permitted sender) smtp.mail=jjllambias@gmail.com; dkim=pass (test mode) header.i=@gmail.com Reply-To: lojban@googlegroups.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: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 2011/6/25 Felipe Gon=E7alves Assis : > > First, a thought experiment. Imagine you were assigned to define the > place structure of a gismu based on the idea of "more", or comparatives. > How would you define it? (Really, think a bit about that before proceedin= g) I don't know, but I can tell you how I think the place structure of "zmadu" came about: Imagine you want a suffix like the English suffix -er, to make comparatives like "smaller", "prettier", "heavier", "greener", and so on. Then you end up with the place structure of "zmadu" (the first three places anyway): x1 is more than x2 in smallness, x1 is more than x2 in prettiness, etc. The extension of this to properties that are not derived from a simple adjective came later, but it's a natural one. "x1 is more than x2 in how many kids they have". Wait, there is the adjective "prolific", so that would be "x1 is more than x2 in prolificness", but you would say "more prolific" rather than "prolificker" in English anyway. Or "x1 is more than x2 in how many times they travelled to Paris", I don't think there is an adjective for being a frequent traveller to Paris, but there is the property "lo ka ce'u xo kau roi klama la paris". > Now, what I believe my approach would be. > I would start with "x1 is more than x2..." and think, "we need more place= s > to specify in which sense x1 is more than x2". And in which senses may > something be more than other? > > This is no mystery in logic or math. The general idea of "being more" is > the concept of an order relation. My first proposal would possibly be > =A0"x1 is greater than x2 under order relation x3", > with {zmadu} and {mleca} being the words used to talk generally about > order relations. I think "lidne" might be a better candidate for the general word for order relations. But you can probably convert any "lidne" relation into a "zmadu" or "mleca" with a suitable choice of property: abu lidne by lo selyle'u =3D abu mleca by lo ka ce'u xo kau moi lo selyle'u > How can we express an order relation? Straightforwardly: > =A0{ko'a zmadu ko'e loka ce'u cnita ce'u}. > Assuming the place structure of the order relation paralleled that of > {mleca}, the above sentence would mean precisely > =A0{ko'a se cnita ko'e}. I'm confused. Did you really mean "mleca" and "se" there? I would have said "ko'a zmadu ko'e loka ce'u cnita ce'u" would have to be "ko'a cnita ko'e". But the problem with that is that "cnita" is already, on its own, an order relation. You gain nothing with "zmadu". "ko'a cnita ko'e" already says what you wanted to say in the first place. The power of "zmadu" is that it creates an order relation out of something that is not, on its own, an order relation. Something like "crino". From the property "lo ka ce'u crino" you create the order relation "lo ka ce'u ri'ozma ce'u". But it would be pointless to say "ko'a zmadu ko'e lo ka ce'u ri'ozma ce'u". > It turns out, though, that there is another relatively simple way, probab= ly > much more common, to specify an order relation. Given a general set X, > an already ordered set Z, and a map f: X -> Z, there is a unique order > relation in X which makes f monotone. This is the order induced in X by > Z via f. > > This is what we mean when we say "Alice is heavier than Bob". We are > comparing the folks with the relation induced by the usual real numbers > ordering via the weight function. > > In these cases, it would be much simpler to just make x3 the function. > It could be argued that this is a sumti raising over the original definit= ion. > This implicit sumti raising could be made standard with no risk of > ambiguity. And that's basically what zmadu does, except you don't put f in the x3, you put there the properties that the members of X have by virtue of being mapped by f into Z. This is convenient because we already have a straightforward way to refer to these properties using selbri ("lo ka ce'u "), whereas we have no straightforward way of referring to f. The simpleat I can think of is "lo fancu be fo lo ka ce'u " but that just adds words to what we already had. > Let us look first at the definition. > "x1 exceeds/is more than x2 in property/quantity x3 (ka/ni) by amount/exc= ess x4" > > Granted, the line of thought of the gismu finti was not the same as mine. > > However, you certainly agree that the x3 is meant to specify the kind of > more-ness being expressed. If you also think that a {zmadu} necessarily > entails some order relation, you should agree that it is the x3 that allo= ws > the speaker to specify it. > (The x4 is a separate issue, addressed at the end) > > Now, let us examine current use. In the sentence > =A0{ko'a zmadu ko'e loni ce'u clani}, > would you describe the x3 as rather > =A0(a) a property abstraction in the same sense that {loka ce'u clani} is= ? > =A0(b) a quantity in the same sense as {loni ko'a clani} is? > =A0(c) the length function? > =A0(d) something else? > > Option (c) is clearly the answer for me. "ni" (much like "jei") has been used with two different senses. More or les= s: (1) ni =3D ka se la'u ma kau (2) ni =3D se klani lo nu I assume your sense (a) responds to (1), and your sense (b) to (2). I don't think it has ever been used to describe the length function, unless you assume that the x3 of zmadu must take a function, and therefore when "lo ni clani" is used in the x3 of zmadu then it must be referring to the length function instead of to the properties that things have by being assigned a length by the length function. If you assume, like I do, that the x3 of zmadu takes a property, then when "lo ni" is used in the x3 of zmadu it must be referring to the property "lo ka se la'u ma kau ce'u clani". > {fancu} would be more useful were it defined as, e.g., > =A0"[...] defined by expression x4 with free variable x5 (letteral)". > > What do you think of my using the undefined x5 like that? > =A0{fancu fo lu lo cmene be me'o xy. li'u me'o xy.} Personally I'm happy with the kau-method, but I would understand what you m= ean. >> but there is no cmavo (say "lo'au") that condenses that into >> something like "lo'au cmene be ce'u". > >> I would suggest using a function cmavo, like "lo'au", for that. > > Alternatively, the new cmavo could play the role of {ce'u}, and > bind to the usual descriptors, instead of abstractions: > =A0{lo cmene be ce'au} > =A0{loni ce'au clani} As I said, I prefer that any expression that starts with "lo cmene ..." refers to names and not to a function into names, but that's just my preference. > As a general note, whatever the means to representing a > function may be, it should be relatively easy to specify its > defining expression and range. The precise domain is > usually unimportant. The defining expression also usually pretty much determines the range: you know what kind of thing "cmene" can take as its x1, so it's not really necessary to specify that the range of the cmene-function is linguistic expressions of a certain kind (cmevla or selbri in the case of Lojban names). But you can also figure out what the function in question is from the property "lo ka ma kau cmene ce'u", "the property of having whatever name it has". > All in all, I am still convinced that functions are not only important, > but also the right thing to fill some places. Nevertheless, I am not > sure about how to best express them concisely while still keeping > in line with current lojban grammar and usage... Especially difficult are the cases of xokau, such as what I would express with "lo fancu be fo lo ka ce'u xo kau moi" (the function that takes something into its position in a sequnce) or "lo fancu be fo lo ka xo kau da broda ce'u" (the function that takes something into the number of things that broda it, for example "lo fancu be fo lo ka xo kau da tunba ce'u", "the function that takes something into the number of siblings they have"). mu'o mi'e xorxes --=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.