Received: from mail-yb1-f188.google.com ([209.85.219.188]:50062) by stodi.digitalkingdom.org with esmtps (TLSv1.3:TLS_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1joxHE-0001e4-IG for lojban-list-archive@lojban.org; Fri, 26 Jun 2020 15:56:58 -0700 Received: by mail-yb1-f188.google.com with SMTP id o140sf11324991yba.16 for ; Fri, 26 Jun 2020 15:56:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20161025; h=sender:date:from:to:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:list-subscribe :list-unsubscribe; bh=I+rsu0qYA/syljtiZl6aJ8MC3D7yI29cCXEbgp759kM=; b=KrbrglUCueTHVFlolCwDNRC0lxl/tIgL90Yu8LfjwPhEo6zcMfmT+0kAO1xlU8sY3k v+fr43xtDWqChGWxmJeQ2FT9RqfdX+HV7SNX4GZi256l0vCuon6QSwVyRYD3q16CXMUC ZnL1Xvm9TyJAWFlsy5MOVFzcJBBxa6DC0j5XBGZZN7O/Qu9SP4FFX4gOne9XWqItkdi3 r2LFHRadVv/Fn6sduG35v6v5WNbn9wa+oNvL3PoJr+UcGtHN1OfCCech0MWX+hJ04oXa yW2dcnw5blFh+/oOaS4qxiZC9xyp52HV+Rd4GByNZjl3M2wzXlyV7/s93e4c81B/IseT J1eQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mail.gvsu.edu; s=google; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=I+rsu0qYA/syljtiZl6aJ8MC3D7yI29cCXEbgp759kM=; b=HYHYN8oIHwvw3dGE/OFB1BdscFL2rW/efzFPAIAsH9r5PrXLuSSsuR+kkIlnzDh6QA 1YdU2PyHYk6ydqOP3DLEwkBF32etOjXOV6iN1fuQt71lNk59DFTGYSuDxeAb4I999w06 IYkU7I/pr62mbprE3apOjNnqhYZHbc2rgcsCQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=sender:x-gm-message-state:date:from:to:message-id:in-reply-to :references:subject:mime-version:x-original-sender:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=I+rsu0qYA/syljtiZl6aJ8MC3D7yI29cCXEbgp759kM=; b=HFZPggpQuTIjQ5fVmM00GAWQQCkQ1qLZNa7C2B2AvOwR1WiZ6FwPO+0UHyIba+9x0x IMYhBZbqlUS2T37v5MDfi6wcVhy1THvT1wZTw+Vp2474LeFVngTSV3jYLbH5W3E6qjSq 4WQfw3151bmHRiQ/K7HgvGK9rU9PFdTQso2NCatrHnmXsxeHsjO4BRFkhsRu0oE0nSQ7 VEu1McHSiR2a/8/ywhyyLvawTbrZVsO+h8yJ0B5bqX7aooZxm2XF8yqXtLlQcIDl3kxj PgLZVTu3mw8TMxV3FgYlFzpSABsEnPFk/i2u4IXh7Jjtqe+TNZuf02NBuR+tppcPpWf7 u8Sg== Sender: lojban@googlegroups.com X-Gm-Message-State: AOAM533XF6l6XLWSpSMVdgHzyhno7Vyr5l3T8sIgyX5z6FOyGs2EXDM2 7LBHeINy9wFFm/ZHMtFsmZI= X-Google-Smtp-Source: ABdhPJyDMuFuHJFg/jlI/M+y9z9MaU9fAy5rDC/ARH46m17HAbNX11lf5gHqkmJBpNy0iuTHZayuFg== X-Received: by 2002:a25:9843:: with SMTP id k3mr8711161ybo.444.1593212210084; Fri, 26 Jun 2020 15:56:50 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 2002:a5b:44:: with SMTP id e4ls3838082ybp.10.gmail; Fri, 26 Jun 2020 15:56:49 -0700 (PDT) X-Received: by 2002:a25:c5cf:: with SMTP id v198mr8700655ybe.6.1593212209409; Fri, 26 Jun 2020 15:56:49 -0700 (PDT) Date: Fri, 26 Jun 2020 15:56:48 -0700 (PDT) From: Jmive To: lojban Message-Id: <6f660247-6db6-4854-88be-08a0a8674eb8n@googlegroups.com> In-Reply-To: References: <8947d7eb-5621-4b69-b047-ed3da665fcafo@googlegroups.com> <5ed45849-4b31-492b-9dd9-e7425ce33b5bo@googlegroups.com> <4f9e3d5a-702f-4201-9309-5eec71516747o@googlegroups.com> <09ceaddd-3561-422a-a4b4-958d6562260co@googlegroups.com> Subject: Re: [lojban] Re: Gismu in need of place structure extensions MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_226_384807639.1593212208466" X-Original-Sender: mcdonohe@mail.gvsu.edu Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Spam-Checked-In-Group: lojban@googlegroups.com X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -2.9 (--) X-Spam_score: -2.9 X-Spam_score_int: -28 X-Spam_bar: -- ------=_Part_226_384807639.1593212208466 Content-Type: multipart/alternative; boundary="----=_Part_227_764121705.1593212208466" ------=_Part_227_764121705.1593212208466 Content-Type: text/plain; charset="UTF-8" On Friday, June 26, 2020 at 9:50:45 AM UTC-4 Adam Lopresto wrote: > On Thu, Jun 25, 2020 at 5:12 PM wrote: > >> >> On Thursday, June 25, 2020 at 12:33:14 PM UTC-4, Gleki Arxokuna wrote: >>> >>> No. Precisely zi'o since the place structure would be different changing >>> semantics >>> >> This doesn't follow. The presence of a {zo'e} in a bridi does not imply >> the existence of an entity for which the bridi holds if the {zo'e} is >> substituted for that entity. That's {da}. As an elliptical, {zo'e} assumes >> the value of whatever sumti is contextually implied... and if context >> implies that nothing fits in that place, that sumti is {zi'o}. {zi'o} is a >> way of explicitly expressing that that particular place is inapplicable in >> the current context, but {zo'e} is *not* an explicit way of expressing >> that it is; it's a way of skipping a place and leaving its value implied. >> > > That's wrong about {zo'e} and about {zi'o}. {zo'e} absolutely does imply > the existence of an entity that satisfies the bridi. The way in which it's > different from {da} is that it also makes a claim about what that entity is > (specifically, that its value can be inferred from context, or that its > particular value isn't important in this context). {mi patfu zo'e} implies > {mi patfu da} every bit as much as {mi patfu do} does. > > {zi'o}, on the other hand, doesn't say anything at all about what can or > can't fill that place. All it does is create a new predicate that doesn't > include that place. Now, as a practical matter, it's relatively rare to > assert a predicate that explicitly removes a place unless you want to imply > that the predicate with that place wouldn't also hold, but that's by no > means necessary. The empty set satisfies {zilcmi} ({se cmima be zi'o}, but > so do all other sets. The members place is removed, but there's no > implication that it's necessarily unfillable. > By the book, I suppose you're right: the book gives {loi jmive cu se zbasu fi loi selci} as incorrect because "We do not generally suppose ... that someone 'makes' living things from cells." But I would contest that this a problem with {zo'e}: if we don't generally suppose that, then context would imply that {lo zbasu} here is equal to {zi'o} if not for the fact that {zi'o} is a special case among sumti in that it cannot be elliptically implied. Requiring an explicit {zi'o} in such a context violates the principle of least effort. It also means, as Gleki points out, that *any change at all* to the place structure of any bridi is liable to break older texts. Yet as the book points out, that very sort of change is inevitable. Allowing the elliptical implication of {zi'o} would fix this problem: the fact that those texts are older is the context that implies the existence of a {zi'o}. On Friday, June 26, 2020 at 8:59:00 AM UTC-4 gleki.is...@gmail.com wrote: > You are changing the definition of gismu. This means old texts will break. > You told it yourself, I'm just commenting on that. The current official > definition of kelci has the concept of game inapplicable. That's why you > have to use zi'o to fix old texts. If Alice uses non-standard meaning of > kelci then the text has to be fixed. > E.g. pleci = x1 plays game x2 (property of x1) > Take that up with xorxes if you want: he does translate the English words "the game began" as {lo nu kelci cu cfari} and "the players" as {lo kelci}. Both of those English phrases indicate that a game is being played. I take this as evidence that the word *as used* has semantic content related to games or gaming, regardless of how it is officially defined. {samselkei} and {dracyselkei} (which, again, by official definitions, literally mean "computer toy" and "roleplaying toy") also indicate that this is how people are trying to use the word. Taking this into account, an additional {kelci} place to accommodate the game being played would be a strict improvement of the word itself, and I think, would alter the semantics of most existing texts far less than you seem to fear: no text where {kelci} is used in a sense expressing the playing of games would be at all harmed. Alternatively, we could define {lo te kelci} as "a game or playful activity". A bridi to express that a kid is playing with a basketball by dribbling it might then be {lo verba cu kelci lo lankyboi lo nu mirjalgau}, even though in English we would not usually call dribbling a game. This way, even if the value of a {zo'e} can never, ever, ever be {zi'o}, no existing usage of {kelci} would be semantically altered in any meaningful way, because {ko'a kelci} already implies that some playful activity is taking place. -- You received this message because you are subscribed to the Google Groups "lojban" group. To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/lojban/6f660247-6db6-4854-88be-08a0a8674eb8n%40googlegroups.com. ------=_Part_227_764121705.1593212208466 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Friday, June 26, 2020 at 9:50:45 AM UTC-4 Adam Lopresto wrote:
On Thu, Jun 25, 2020 at 5:12 PM <deusexma...@gmail.com> wrote:
<= /div>

On Thursday, June 25, 20= 20 at 12:33:14 PM UTC-4, Gleki Arxokuna wrote:
No. Precisely zi'o since the place structure would be = different changing semantics
This doesn't follow. The = presence of a {zo'e} in a bridi does not imply the existence of an e= ntity for which the bridi holds if the {zo'e} is substituted for that entit= y. That's {da}. As an elliptical, {zo'e} assumes the value of whatever sumt= i is contextually implied... and if context implies that nothing fits in th= at place, that sumti is {zi'o}. {zi'o} is a way of explicitly expressing th= at that particular place is inapplicable in the current context, but {zo'e}= is not an explicit way of expressing that it is; it's a way of skip= ping a place and leaving its value implied.

Th= at's wrong about {zo'e} and about {zi'o}. {zo'e} absolutely does imply the = existence of an entity that satisfies the bridi. The way in which it's= different from {da} is that it also makes a claim about what that entity i= s (specifically, that its value can be inferred from context, or that its p= articular value isn't important in this context). {mi patfu zo'e} implies {= mi patfu da} every bit as much as {mi patfu do} does.

{zi'o}, on the other hand, doesn't say anything at all about what can or can't=20 fill that place. All it does is create a new predicate that doesn't=20 include that place. Now, as a practical matter, it's relatively rare to=20 assert a predicate that explicitly removes a place unless you want to=20 imply that the predicate with that place wouldn't also hold, but that's=20 by no means necessary. The empty set satisfies {zilcmi} ({se cmima be=20 zi'o}, but so do all other sets. The members place is removed, but=20 there's no implication that it's necessarily unfillable.
<= /span>
By the book, I suppose you're right: the book gives {loi jmive cu se zbasu fi loi selci} as incorrect because "We do not generally suppose ...=20 that someone 'makes' living things from cells."

But I would contest that this a=20 problem with {zo'e}: if we don't generally suppose that, then context=20 would imply that {lo zbasu} here is equal to {zi'o} if not for the fact=20 that {zi'o} is a special case among sumti in that it cannot be elliptically implied. Requiring an explicit {zi'o} in such a context=20 violates the principle of least effort. It also means, as Gleki points=20 out, that any change at all to the place structure of any bridi=20 is liable to break older texts. Yet as the book points out, that very=20 sort of change is inevitable. Allowing the elliptical implication of=20 {zi'o} would fix this problem: the fact that those texts are older is=20 the context that implies the existence of a {zi'o}.

On Friday, June 26, 2020 at 8:59:00 AM UTC-4 gleki.is...@gmail.com w= rote:
=
= You are changing the definition of gismu. This means old texts will break.=20 You told it yourself, I'm just commenting on that. The current official=20 definition of kelci has the concept of game inapplicable. That's why you have to use zi'o to fix old texts. If Alice uses non-standard meaning=20 of kelci then the text has to be fixed.
E.g. pleci =3D x1 plays game x2 = (property of x1)
Take that up wit= h xorxes if you want: he does translate the English words "the game began" = as {lo nu kelci cu cfari} and "the players" as {lo kelci}. Both of those En= glish phrases indicate that a game is being played. I take this as evidence= that the word as used has semantic content related to games or gami= ng, regardless of how it is officially defined. {samselkei} and {dracyselke= i} (which, again, by official definitions, literally mean "computer toy" an= d "roleplaying toy") also indicate that this is how people are trying to us= e the word. Taking this into account, an additional {kelci} place to accomm= odate the game being played would be a strict improvement of the word itsel= f, and I think, would alter the semantics of most existing texts far less t= han you seem to fear: no text where {kelci} is used in a sense expressing t= he playing of games would be at all harmed.

Alternatively, we could = define {lo te kelci} as "a game or playful activity". A bridi to express th= at a kid is playing with a basketball by dribbling it might then be {lo ver= ba cu kelci lo lankyboi lo nu mirjalgau}, even though in English we would n= ot usually call dribbling a game. This way, even if the value of a {zo'e} c= an never, ever, ever be {zi'o}, no existing usage of {kelci} would be seman= tically altered in any meaningful way, because {ko'a kelci} already implies= that some playful activity is taking place.

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsub= scribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/l= ojban/6f660247-6db6-4854-88be-08a0a8674eb8n%40googlegroups.com.
------=_Part_227_764121705.1593212208466-- ------=_Part_226_384807639.1593212208466--