Received: from localhost ([::1]:43021 helo=stodi.digitalkingdom.org) by stodi.digitalkingdom.org with esmtp (Exim 4.76) (envelope-from ) id 1S6H8l-0000fa-KC; Fri, 09 Mar 2012 23:54:59 -0800 Received: from 173-13-139-235-sfba.hfc.comcastbusiness.net ([173.13.139.235]:51627 helo=jukni.digitalkingdom.org) by stodi.digitalkingdom.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1S6H8g-0000fN-87 for wikineurotic@lojban.org; Fri, 09 Mar 2012 23:54:57 -0800 Received: from jukni.digitalkingdom.org (localhost [127.0.0.1]) by jukni.digitalkingdom.org (8.14.5/8.14.5) with ESMTP id q2A7srLK024541 for ; Fri, 9 Mar 2012 23:54:53 -0800 Received: (from apache@localhost) by jukni.digitalkingdom.org (8.14.5/8.14.5/Submit) id q2A7srpj024540; Fri, 9 Mar 2012 23:54:53 -0800 Date: Fri, 9 Mar 2012 23:54:53 -0800 X-Authentication-Warning: jukni.digitalkingdom.org: apache set sender to webmaster@lojban.org using -f To: wikineurotic@lojban.org X-PHP-Originating-Script: 48:htmlMimeMail.php MIME-Version: 1.0 From: webmaster@lojban.org Message-ID: X-Spam-Score: 2.6 (++) X-Spam_score: 2.6 X-Spam_score_int: 26 X-Spam_bar: ++ X-Spam-Report: Spam detection software, running on the system "stodi.digitalkingdom.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: The page Tsani's Interpretations: Abstractors was changed by Jacob at 07:54 UTC You can view the page by following this link: http://www.lojban.org/tiki/Tsani%27s%20Interpretations%3A%20Abstractors [...] Content analysis details: (2.6 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 1.6 RCVD_IN_BRBL_LASTEXT RBL: RCVD_IN_BRBL_LASTEXT [173.13.139.235 listed in bb.barracudacentral.org] 0.4 RDNS_DYNAMIC Delivered to internal network by host with dynamic-looking rDNS 0.6 TO_NO_BRKTS_DYNIP To: misformatted and dynamic rDNS Subject: [Wikineurotic] Wiki page Tsani's Interpretations: Abstractors changed by Jacob X-BeenThere: wikineurotic@lojban.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: webmaster@lojban.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: wikineurotic-bounces@lojban.org The page Tsani's Interpretations: Abstractors was changed by Jacob at 07:54 UTC You can view the page by following this link: http://www.lojban.org/tiki/Tsani%27s%20Interpretations%3A%20Abstractors You can view a diff back to the previous version by following this link: http://www.lojban.org/tiki/tiki-pagehistory.php?page=Tsani%27s%20Interpretations%3A%20Abstractors&compare=1&oldver=3&newver=4 *********************************************************** The changes in this version follow below, followed after by the current full page text. *********************************************************** +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ @@ -Lines: 5-9 changed to +Lines: 5-9 @@ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ As for the presence of {ce'u} within these embedded bridi, I adhere to ((ka, du'u, si'o, ce'u, zo'e|these rules)). - As for subscripting {ce'u} with {xi} in the event of a {ce'u}-type abstraction being contained within an abstraction, I adhere to the rules of relative clauses as outlined in The Book. That is to say that {ce'uxire} refers to a {ce'u} of the parent abstraction ''even if that abstraction is not {ce'u}-capable'', i.e. a member of {nu} and friends. This is done for the sake of simplicity. + As for subscripting {ce'u} with {xi} in the event of a {ce'u}-type abstraction being contained within an abstraction, I adhere to the rules of relative clauses as outlined in The Book. That is to say that {ce'uxire} refers to a {ce'u} of the parent abstraction ''even if that abstraction is not {ce'u}-capable'', i.e. a member of {nu} and friends. This is done for the sake of simplicity. Using {ce'u} without a subscript, in a {ce'u}-incapable clause ({nu} et al.) is __incorrect__, ''even if that clause is embedded within a {ce'u}-capable one. !{nu} and {du'u} +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ @@ -Lines: 75-76 changed to +Lines: 75-128 @@ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Example of pre-application: {mi djuno lo ka ce'u nelci citka lo plise kei do}, {mi djuno lo do nelci citka ce'u kei lo plise} -> {mi djuno lo du'u do nelci citka lo plise} + + !Using {ka} everywhere! + + !!A list of gismu that I propose should use {ka} + + *kakne = x1 is capable of being/doing x2 (ka) under conditions x3 (nu) + *zukte = x1 employs means x2 (ka) to bring about/cause x3 (nu) + *troci = x1 attempts x2 (ka) by actions/method (ka) + *snada = x1 accomplishes/succeeds at x2 (ka) as a result of attempt x3 (ka) + *fliba = x1 fails at being/doing x2 (ka) + *sisti = x1 ceases to be/do x2 (ka) + *zifre = x1 is free to be/do x2 (ka) under conditions (nu) + *bilga = x1 is obliged to be/do x2 (ka) by standard/agreement + *fuzme = x1 is responsible/accountable for action x2 (ka) to judge/authority x3 + *gunka = x1 works/labours at x2 (ka) for purpose/goal/objective x3 (nu) + *lazni = x1 is lazy at/avoiding work/effort concerning action x2 (ka) + *tatpi = x1 is tired/fatigued by effort/work/situation x2 (ka) + *surla = x1 is relaxed/relaxing/resting/is at ease at being/doing x2 (ka) + *srera = x1 errs in doing/being x2 (ka), erroneous under conditions x3 (nu) by standard x4 + *darsi = x1 shows audacity in doing/being x2 (ka) + *virnu = x1 is brave/courageous in doing/being x2 (ka) by standard x3 + *bebna = x1 is a fool/idiot/boob at doing/being x2 (ka) + *stati = x1 has a talent/aptitude/innate skill for doing/being x2 (ka) + *tarti = x1 behaves/conducts oneself as/in manner x2 (ka) under conditions x3 (nu) + *certu = x1 has skill/shows prowess at doing/being x2 (ka) by standard x3 + *sutra = x1 is fast/swift at doing/being x2 (ka) + *masno = x1 is slow/sugglish at doing/being x2 (ka) + *frati = x1 reacts/responds with action x2 (ka) to stimulus x3 (nu) under conditions x4 (nu) + *bredi = x1 is ready/prepared for x2 (ka) + *rivbi = x1 avoids/shuns/escapes/skirts [fate] x2 (ka) by action/state x3 (ka) + *((Tsani's Interpretations: Bad gismu|zajba)) = x1 is a gymnast at/performs gymnastics feat x2 (ka) + *((Tsani's Interpretations: The case against cinse|cinse)) = x1, in activity/state x2 (ka), exhibits sexuality/gender/sexual orientation x3 (ka) by standard x4 + *kamni = x1 (mass) is a committee with task/purpose x2 (ka) of body x3 + + !!Problems with using {ka}; "How do I say X?" + + Some of you might complain that using these properties instead of events for some gismu, such as {bredi}, makes them less useful, but I argue that a form of sumti raising answers that problem. How to say, under my interpretation, "I'm ready for the end of the world" ? Under official Lojban, let's say that {mi bredi lo nu fanmo pe'a lo munje} glosses the English sentence. Then, ask yourself, "What is that that I'm ready for?" You can't be prepared ''for an event''; you can however be prepared to ''experience'' that even. Thus, I consider {mi bredi lo ka ce'u lifri lo nu fanmo pe'a lo munje}, which is long, but which can be reduced into {mi bredi tu'a lo nu fanmo pe'a lo munje} (yes, it's one of those "I'm raising an event O_o" situations) or into {mi seli'i fanmo pe'a lo munje kei bredi} or into the more afterthought form involving {co}, {mi bredi co seli'i fanmo pe'a lo munje}, as being a better solution. + + Another notable ka-ification is that of {sisti}, which I differentiate from {cirko} with volition. That is to say that {lo si'o sisti cu si'o zukte lo ka ce'u cirko ce'uxire}. In order to get at the "old" version of sisti, I'd use {zukte lo ka ce'u tolcfa}. + + {co} becomes a real jewel as it lets us avoid a lot of description and abstraction boilerplate. Consider the previous example, {zukte lo ka ce'u tolcfa}. We can readily reduce this into {zukte co tolcfa}. Similarly, {kakne lo ka broda} can be transformed into {kakne co broda}. This was possible before this ka-revolution, and is thus not an antecedent of my proposal, but I do advocate furthering the use of {co} in order to reduce the number of uses of {lo} and various abstraction markers. + + Yes, this system involves more words for ''a lot'' of constructs, but now we have a more consistent type system that lets us pass around properties like so: {mi bredi lo na se kakne be do}, {mi zifre lo se djuno be do [bei mi]}. + + + + !Some notable formulae + + Under this interpretation of abstractors, the following is true: + *{ko'a ckaji lo ka ce'u broda} -> {ko'a broda} + *{ko'a dunli ko'e lo ka ce'u broda} -> {ko'a .o ko'e broda} + *********************************************************** The new page content follows below. *********************************************************** This page is part of a series called ((Tsani's Interpretations of Controversial Lojban Grammar|Tsani's Interpretations of Controversial Lojban Grammar)). Any abstractors in Lojban are extremely useful with their current definitions, but with ((The Complete Lojban Language|the book))'s definitions not quite matching the way many abstractors are used in current conversations on IRC, I feel the need to explain the way I use these cmavo, in perhaps what is an attempt to make them, overall, more useful. As for the presence of {ce'u} within these embedded bridi, I adhere to ((ka, du'u, si'o, ce'u, zo'e|these rules)). As for subscripting {ce'u} with {xi} in the event of a {ce'u}-type abstraction being contained within an abstraction, I adhere to the rules of relative clauses as outlined in The Book. That is to say that {ce'uxire} refers to a {ce'u} of the parent abstraction ''even if that abstraction is not {ce'u}-capable'', i.e. a member of {nu} and friends. This is done for the sake of simplicity. Using {ce'u} without a subscript, in a {ce'u}-incapable clause ({nu} et al.) is __incorrect__, ''even if that clause is embedded within a {ce'u}-capable one. !{nu} and {du'u} These two abstractors constitute the core of this document. Disregarding {su'u}, it is my belief that all abstractions can be expressed using only {nu} and {du'u} (to some degree) and thus that all other abstractors exist only for convenience, or for achieving certain slightly more specific interpretations (as is the case for {jei} and {ni}, described near the end of this document). !!{nu} {nu}, like its gloss suggests, creates an event, which is bounded in spacetime and has various properties such as its duration and its location(s). It is mainly used after sumtcita, such as and most commonly {ca}. ''.i ca lo nu zdani nerkla kei mi co'u cutci dasni -- When I enter my house, I take off my shoes.'' (For additional explanations on {ca} and other tenses and sumtcita, see ((Tsani's Interpretations: Sumti Tags|this)).) There are no circumstances for which a nu-clause should contain {ce'u}; the same goes for {nu}'s friends, {li'i}, {mu'e}, {pu'u}, {za'i}, and {zu'o}. Additionally, a nu-clause should never contain an indirect question. That is to say that a {nu} abstraction must always be "fully applied". See the section on {ka} for an explanation of "application". The "return value" of a nu-clause is inherently a fasnu1. !!{du'u} {du'u} is the predication abstractor, where it differs from {nu} in that {du'u} has an x2, namely the text claiming du'u1. Predications are not are not bound in spacetime and have properties such as sumti being related, type of relationship, and modals and connectives involved. A du'u1 is a sort of class of nu1, such that events are instances of predications. There are few brivla that actually use true du'u. In fact, it seems like most of the "facts xN (du'u) about subject xN+1" are actually properties, rather than real predications. For instance, for all uses of {djuno} where the x3 must find its way into the x2 in order to be semantically correct, djuno2 is a property of djuno3, rather than a du'u. More on that in the section about {ka}. {du'u}'s default "return value" is a bridi1, which entails that under my interpretation, bridi1 is a du'u1. A return value that differs from the default is marked using an indirect question: compare {lo du'u do klama}, {lo du'u do klama makau}, {lo du'u do mokau}, and {lo du'u mi jikau do klama}. There are some questions for which the interpretation is strange: consider {lo du'u peikau mi cinba do}[1], {lo du'u fi'akau do cinba fi'akau mi}, {lo du'u mi sexixokau darxi do}, and {lodu'u xokaure'u nu mi cinba do}. There are two particular indirect questions, namely {la'umakau} and {xukau}, that are discussed in the section regarding {jei} and {ni}. Of course, as could be seen in the {fi'akau} example, there's nothing wrong with using multiple indirect questions. As for {peikau}, it glosses "what ''you'' feel about broda" and not "what ''I'' feel about broda". (Okay, it ''could'' mean "what I feel about broda", but only under a {doi mi} context, which is silly.) Some problems arising from ((Tsani's Interpretations: The Superman/Lois Lane Paradox|the Superman/Lois Lane paradox)) prompted the creation of two experimental cmavo, which are useful only under very specific circumstances: {((Tsani's Interpretations: du'au|du'au))} and {(Tsani's Interpretations: lu'au|lu'au))}. Both are members of LAhE and they respectively cast a text into a bridi1 and bridi1 into a text. For example, consider {.i ko'a goi lo du'u mi citka ci lo plise}. {.i mi cusku lu'au ko'a} is equivalent in meaning to {.i mi cusku lo se du'u mi citka ci lo plise}. !{ka} and {si'o} These two abstractors are children of {du'u}, in the sense that it is possible, using only {du'u} to express meanings identical to those of {ka} and {si'o}. I work under the assumption that a du'u-clause containing at least one {ce'u} is equivalent to a ka-clause and that a du'u-clause where all sumti places and explicit modal places are {ce'u} is equivalent to a si'o-clause. !!{ka} Under my interpretation, {ka} is hugely useful, in that it supplants many prior uses of {nu}. In order to properly understand the way that I grasp the property abstraction, it is necessary to understand that Lojban uses a second order logic for this. Consider {bebna = x1 is foolish in property x2} and the example {mi bebna lo ka [ce'u] cinba du'ezo'e}. Readily, we can see that there is a sort of second-degree predication, namely {lo du'u mi cinba du'ezo'e}. This is a process that I call ''application''. Applying a property to a sumti or to sumti means to reduce the property abstraction using {ka} into a predication abstraction using {du'u}. To do so, one must determine the referents of the {ce'u}. For instance, {mi mutce lo ka ce'u tavla do makau} -> {lo du'u mi tavla do makau}. Application is a process handled by the selbri relating the property; the speaker never has to worry about application. In other words, the "property brivla", such as but not limited to {kakne}, {mutce}, {simxu}, {zukte}, {mulno}, {simsa}, and {dunli}, function in a two-step process of applying the property, and then making a claim about the predication that results from the application. Note that as a {du'u} abstraction is called a bridi or proposition, a {ka} abstraction is called a ''function'', where the {ce'u} is/are the parameter(s). !!{si'o} Certainly less useful than {ka}, {si'o} has a specific function that is difficult or irritating to implement with a {du'u} abstraction. Under my interpretation, a sidbo1 __is not__ a {si'o}. I believe that a sidbo1 is simply a property of sibdo2, as understood/created/interpreted by sidbo3. I understand {lo si'o broda} as meaning "what is means to ''broda'', for si'o2" or "the meaning of ''broda'', for si'o2" or "'s interpretation of ''broda''". !{du'u}'s friends: {ni} and {jei} {ni} and {jei} fall into "{du'u}'s friends" category, rather than the "{du'u}'s children category" which encompasses {ka} and {si'o}, due to that there are no required {ce'u} in a ni/jei-abstraction. However, they remain {du'u}'s ''friends'' and __not__ {du'u}'s ''siblings'' due to that a simple {du'u} abstraction can be used to obtain an __almost__ equal meaning. It ''must'' be noted that {ni} and {jei} do have interpretations slightly different from their du'u-equivalents. Like a {du'u} abstraction however, {ni} and {jei} abstractions may contain {ce'u}. !!{ni} A {ni} abstraction is vague. It may extract from the bridi either a pure number, a number ''with units'', or a vague sort of comparable-ish thing. In terms of {du'u}, this is done by means of a sumti indirect question attached to a modal, namely {sela'u} or {la'u}, for the first two possible return values, respectively. These modals stem from {klani} from which {ni} itself stems. Considering that properties are not comparable, but that quantities are, a {ni} abstraction is under my interpretation the correct sumti for the comparison property place of {zmadu}, {mleca}, and (on some occasions) {dunli}. e.g. ''mi zmadu do lo ni ce'u certu lo ka ce'u tavla fo lo lojbo'' "My ability to speak Lojban exceeds yours" !!{jei} The ''truth-value abstraction'' as it's called is in a sense a specialisation of {ni}, rather than of {du'u} itself, considering that the return value of {jei} under my interpretation is a real number in the interval [0, 1]. As numbers are comparable, {jei} abstractions may be used as zmadu/mleca/dunli3, but this is unuseful outside of fuzzy logic contexts. All in all, however, {jei} has extremely few uses. In terms of a {du'u}-approximation, {jei} is similar to {lo du'u xukau broda} !The Pre-application of properties Some places that use {du'u} in Official Lojban, but {ka} under my interpretation may be ''pre-applied'', i.e. applied by the speaker and not the selbri. The most notable instance of pre-application is {djuno}. Under my interpretation, it would be necessary for all {djuno} bridi to be of the type {ko'a djuno lo ka ce'u brode kei ko'e}, which is extremely inconvenient. Thus, for the sake of simplicity, preserving backwards-compatibility as much as possible, and not having to use {kei}, using a plain, fully-applied {du'u} is acceptable as a djuno2. If djuno3 is left implicit, it is understood that it is some sumti from the proposition expressed in djuno2. If djuno2 is fully-applied but djuno3 is specified and is not redundant to any explicit or implicit sumti that are present in the djuno2 proposition, it is defined as being the referent of an implicit {ce'u} inside the prenex of the djuno2 proposition. Example of pre-application: {mi djuno lo ka ce'u nelci citka lo plise kei do}, {mi djuno lo do nelci citka ce'u kei lo plise} -> {mi djuno lo du'u do nelci citka lo plise} !Using {ka} everywhere! !!A list of gismu that I propose should use {ka} *kakne = x1 is capable of being/doing x2 (ka) under conditions x3 (nu) *zukte = x1 employs means x2 (ka) to bring about/cause x3 (nu) *troci = x1 attempts x2 (ka) by actions/method (ka) *snada = x1 accomplishes/succeeds at x2 (ka) as a result of attempt x3 (ka) *fliba = x1 fails at being/doing x2 (ka) *sisti = x1 ceases to be/do x2 (ka) *zifre = x1 is free to be/do x2 (ka) under conditions (nu) *bilga = x1 is obliged to be/do x2 (ka) by standard/agreement *fuzme = x1 is responsible/accountable for action x2 (ka) to judge/authority x3 *gunka = x1 works/labours at x2 (ka) for purpose/goal/objective x3 (nu) *lazni = x1 is lazy at/avoiding work/effort concerning action x2 (ka) *tatpi = x1 is tired/fatigued by effort/work/situation x2 (ka) *surla = x1 is relaxed/relaxing/resting/is at ease at being/doing x2 (ka) *srera = x1 errs in doing/being x2 (ka), erroneous under conditions x3 (nu) by standard x4 *darsi = x1 shows audacity in doing/being x2 (ka) *virnu = x1 is brave/courageous in doing/being x2 (ka) by standard x3 *bebna = x1 is a fool/idiot/boob at doing/being x2 (ka) *stati = x1 has a talent/aptitude/innate skill for doing/being x2 (ka) *tarti = x1 behaves/conducts oneself as/in manner x2 (ka) under conditions x3 (nu) *certu = x1 has skill/shows prowess at doing/being x2 (ka) by standard x3 *sutra = x1 is fast/swift at doing/being x2 (ka) *masno = x1 is slow/sugglish at doing/being x2 (ka) *frati = x1 reacts/responds with action x2 (ka) to stimulus x3 (nu) under conditions x4 (nu) *bredi = x1 is ready/prepared for x2 (ka) *rivbi = x1 avoids/shuns/escapes/skirts [fate] x2 (ka) by action/state x3 (ka) *((Tsani's Interpretations: Bad gismu|zajba)) = x1 is a gymnast at/performs gymnastics feat x2 (ka) *((Tsani's Interpretations: The case against cinse|cinse)) = x1, in activity/state x2 (ka), exhibits sexuality/gender/sexual orientation x3 (ka) by standard x4 *kamni = x1 (mass) is a committee with task/purpose x2 (ka) of body x3 !!Problems with using {ka}; "How do I say X?" Some of you might complain that using these properties instead of events for some gismu, such as {bredi}, makes them less useful, but I argue that a form of sumti raising answers that problem. How to say, under my interpretation, "I'm ready for the end of the world" ? Under official Lojban, let's say that {mi bredi lo nu fanmo pe'a lo munje} glosses the English sentence. Then, ask yourself, "What is that that I'm ready for?" You can't be prepared ''for an event''; you can however be prepared to ''experience'' that even. Thus, I consider {mi bredi lo ka ce'u lifri lo nu fanmo pe'a lo munje}, which is long, but which can be reduced into {mi bredi tu'a lo nu fanmo pe'a lo munje} (yes, it's one of those "I'm raising an event O_o" situations) or into {mi seli'i fanmo pe'a lo munje kei bredi} or into the more afterthought form involving {co}, {mi bredi co seli'i fanmo pe'a lo munje}, as being a better solution. Another notable ka-ification is that of {sisti}, which I differentiate from {cirko} with volition. That is to say that {lo si'o sisti cu si'o zukte lo ka ce'u cirko ce'uxire}. In order to get at the "old" version of sisti, I'd use {zukte lo ka ce'u tolcfa}. {co} becomes a real jewel as it lets us avoid a lot of description and abstraction boilerplate. Consider the previous example, {zukte lo ka ce'u tolcfa}. We can readily reduce this into {zukte co tolcfa}. Similarly, {kakne lo ka broda} can be transformed into {kakne co broda}. This was possible before this ka-revolution, and is thus not an antecedent of my proposal, but I do advocate furthering the use of {co} in order to reduce the number of uses of {lo} and various abstraction markers. Yes, this system involves more words for ''a lot'' of constructs, but now we have a more consistent type system that lets us pass around properties like so: {mi bredi lo na se kakne be do}, {mi zifre lo se djuno be do [bei mi]}. !Some notable formulae Under this interpretation of abstractors, the following is true: *{ko'a ckaji lo ka ce'u broda} -> {ko'a broda} *{ko'a dunli ko'e lo ka ce'u broda} -> {ko'a .o ko'e broda} _______________________________________________ Wikineurotic mailing list Wikineurotic@lojban.org http://mail.lojban.org/mailman/listinfo/wikineurotic