Received: from mail-wi0-f189.google.com ([209.85.212.189]:40534) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1YV6zl-0006ms-V1 for lojban-list-archive@lojban.org; Mon, 09 Mar 2015 16:22:02 -0700 Received: by widex7 with SMTP id ex7sf3788353wid.7 for ; Mon, 09 Mar 2015 16:21:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe; bh=YEalu4V+rTxVysKnQ4esA8BCBVegWQmUlBHuU+qQHJ0=; b=DeyLfM9JDFtQb+AUeVSQEwKqS53kQPn/9kuo323p6yWfPA9OklNWU104eCXHvL+kg2 IbQPDBOtwPrcWFwSK7TyTG0HhCEU3ZlomlDytnOz0y/IMVDXeww/Zw1vySiFhidNtxHO 7sNv8wXA0R26vBlgxb44+nd2cDi3NkqDmGsOyV3B5SfJgd+z+2WBRRb7De8VcfPdKwMN uznA7+Pw59m9vPBeIBkWMu+0GLRnMDdvkBG9gZO1lQWfKADRMmUai4XM5z56vmMfQb9W 62Q04UbvVRUF5DllW2rn7I8fP+VSPxfKYrhyiXMnJ3ASOy3tTk+Iul43kljXc07FWhXs b+mw== X-Received: by 10.180.14.102 with SMTP id o6mr413963wic.19.1425943310902; Mon, 09 Mar 2015 16:21:50 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.180.77.75 with SMTP id q11ls50333wiw.10.gmail; Mon, 09 Mar 2015 16:21:50 -0700 (PDT) X-Received: by 10.180.80.132 with SMTP id r4mr934660wix.4.1425943310422; Mon, 09 Mar 2015 16:21:50 -0700 (PDT) Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com. [2a00:1450:400c:c00::22e]) by gmr-mx.google.com with ESMTPS id c8si406274wiw.1.2015.03.09.16.21.50 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Mar 2015 16:21:50 -0700 (PDT) Received-SPF: pass (google.com: domain of ilmen.pokebip@gmail.com designates 2a00:1450:400c:c00::22e as permitted sender) client-ip=2a00:1450:400c:c00::22e; Received: by wghl2 with SMTP id l2so32012811wgh.8 for ; Mon, 09 Mar 2015 16:21:50 -0700 (PDT) X-Received: by 10.180.77.199 with SMTP id u7mr4076826wiw.42.1425943310337; Mon, 09 Mar 2015 16:21:50 -0700 (PDT) Received: from [192.168.0.102] (95-210-212-178.ip.skylogicnet.com. [95.210.212.178]) by mx.google.com with ESMTPSA id gz3sm1275439wib.1.2015.03.09.16.21.46 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Mar 2015 16:21:49 -0700 (PDT) Message-ID: <54FE2B04.8070302@gmail.com> Date: Tue, 10 Mar 2015 00:21:40 +0100 From: Ilmen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: lojban@googlegroups.com Subject: Re: [lojban] {detri} References: <54FD915D.4060607@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------020805020104010408070505" X-Original-Sender: ilmen.pokebip@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ilmen.pokebip@gmail.com designates 2a00:1450:400c:c00::22e as permitted sender) smtp.mail=ilmen.pokebip@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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: , List-Unsubscribe: , X-Spam-Score: -1.7 (-) X-Spam_score: -1.7 X-Spam_score_int: -16 X-Spam_bar: - This is a multi-part message in MIME format. --------------020805020104010408070505 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable On 09/03/2015 22:48, Jorge Llamb=C3=ADas wrote: > > On Mon, Mar 9, 2015 at 9:26 AM, Ilmen > wrote: > > > =E2=80=A2 { .i detri fa li re no no bi pi'e mu pi'e re mu } > =E2=80=A2 { li pa no pi'e vo no cu tcika fo mi } > > However, does the {detri} sentence actually have the intended > meaning? Isn't {me'o} more appropriate than {li} for expressing dates= ? > > > I think dates (and times) are coordinates in a one-dimensional time=20 > axis, so I think {li} is right. Coordinates are numbers, not=20 > expressions. So for example the expressions "2008-05-25" and "May 25,=20 > 2008" both refer to the same date, even though they are different=20 > expressions (different me'o, same li). So, according to you, {detri} is a relation between a timestamp / time=20 address, and an event? This would be an useful predicate indeed, but=20 that seems to be very different from the relation described in the Gimste. If {detri} has the meaning you're suggesting, then another predicate is=20 necessary for relating a date structure to an event using a specific=20 calendar system, or to convert a date structure into a timestamp / pure=20 number address. > In sentences such as { detri fa li re no no bi pi'e mu pi'e re mu > }, it seems that the date expression "2008:5:25" is first > evaluated into a pure number (using some unspecified base), > > and then given to detri-x1, in which case detri-x4 seems to become > completely useless, as it cannot be applied to any numeric > expression (as all is given to it as input is a pure number). { > detri fa li re no no bi pi'e mu pi'e re mu fo ko'a } would then be > about as meaningful as { li ze no no no no no cu detri fo ko'a }. > > > I take detri4 (or detri3 rather, since I take detri to have only three=20 > places) as the reference frame, not a place to indicate how to read=20 > the expression used to refer to the detri1. Basically it should tell=20 > you what the origin and the units are. How to read the li-expression=20 > is something that one must already know. Just as one knows that in "li=20 > pa no" the first digit is for tens and the second for units, one=20 > should know that in "li re no no bi pi'e mu pi'e re mu" the digits=20 > show year-month-day. If you are using some non-standard or not=20 > well-known notation to refer to a date, you would have to explain it,=20 > but basically in the same way you would have to explain any=20 > non-standard expression you use to refer to anything else. I think we=20 > need to keep the date separate from the words used to refer to it.=20 > detri1 is the date, not the words used to refer to it. You could use a=20 > different expression like "la'o gy May 25, 2008 gy" to refer to the=20 > same date that "li re no no bi pi'e mu pi'e re no" refers to. You seem to invest {li} with a great power, greater than what I'd have=20 expected. It seems that all we know is that {li} is provided with a=20 numeric expression, that it must returns a pure number, but that the=20 function/algorithm for interpreting the numeric expression is entirely=20 left to the context (and there's no way to explicitly provide one using=20 {li}). So much more than merely the numeric base is left to the context,=20 it seems. If so, it becomes difficult to explicitly express which calendar system=20 to use for evaluating the li-expression; it seems to me that the speaker=20 would need to use an appropriate predicate for precisely stating how to=20 interpret the expression, and avoid using {li}. mi'e la .ilmen. mu'o --=20 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 e= mail to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/d/optout. --------------020805020104010408070505 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On 09/03/2015 22:48, Jorge Llamb=C3=ADas wrote:

On Mon, Mar 9, 2015 at 9:26 AM, Ilmen <i= lmen.pokebip@gmail.com> wrote:

=E2=80=A2 { .i detri fa li re no no bi pi'e mu pi'e re mu }=
=E2=80=A2 { li pa no pi'e vo no cu tcika fo mi }

However, does the {detri} sentence actually have the intended meaning? Isn't {me'o} more appropriate than {li} for expressing dates?

I think dates (and times) are coordinates in a one-dimensional time axis, so I think {li} is right. Coordinates are numbers, not expressions. So for example the expressions "2008-05-25" and "May 25, 2008" both refer to the same date, even though they are different expressions (different me'o, same li).

So, according to you, {detri} is a relation between a timestamp / time address, and an event? This would be an useful predicate indeed, but that seems to be very different from the relation described in the Gimste.
If {detri} has the meaning you're suggesting, then another predicate is necessary for relating a date structure to an event using a specific calendar system, or to convert a date structure into a timestamp / pure number address.

In sentences such as { detri fa li re no no bi pi'e mu pi'e re mu }, it seems that the date expression "2008:5:25" is first evaluated into a pure number (using some unspecified base),=C2=A0
and then given to detri-x1, in which case detri-x4 seems to become completely useless, as it cannot be applied to any numeric expression (as all is given to it as input is a pure number). { detri fa li re no no bi pi'e mu pi'e re mu fo ko'a } would then be about as meaningful as { li ze no no no no no cu detri fo ko'a }.

I take detri4 (or detri3 rather, since I take detri to have only three places) as the reference frame, not a place to indicate how to read the expression used to refer to the detri1. Basically it should tell you what the origin and the units are. How to read the li-expression is something that one must already know. Just as one knows that in "li pa no" the first digit is for tens and the second for units, one should know that in "li re no no bi pi'e mu pi'e re mu" the digits show year-month-day. If you are using some non-standard or not well-known notation to refer to a date, you would have to explain it, but basically in the same way you would have to explain any non-standard expression you use to refer to anything else. I think we need to keep the date separate from the words used to refer to it. detri1 is the date, not the words used to refer to it. You could use a different expression like "la'o gy May 25, 2008 gy" to refer to the same date that "li re no no bi pi'e mu pi'e re no" refers to.
You seem to invest {li} with a great power, greater than what I'd have expected. It seems that all we know is that {li} is provided with a numeric expression, that it must returns a pure number, but that the function/algorithm for interpreting the numeric expression is entirely left to the context (and there's no way to explicitly provide one using {li}). So much more than merely the numeric base is left to the context, it seems.

If so, it becomes difficult to explicitly express which calendar system to use for evaluating the li-expression; it seems to me that the speaker would need to use an appropriate predicate for precisely stating how to interpret the expression, and avoid using {li}.

mi'e la .ilmen. mu'o


--
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 post to this group, send email to lojban@googlegroups.com.
Visit this group at http:= //groups.google.com/group/lojban.
For more options, visit http= s://groups.google.com/d/optout.
--------------020805020104010408070505--