From pycyn@aol.com Fri Aug 31 18:06:56 2001
Return-Path: <Pycyn@aol.com>
X-Sender: Pycyn@aol.com
X-Apparently-To: lojban@yahoogroups.com
Received: (EGP: mail-7_3_2); 1 Sep 2001 01:06:56 -0000
Received: (qmail 21157 invoked from network); 1 Sep 2001 01:06:55 -0000
Received: from unknown (10.1.10.26)
  by m8.onelist.org with QMQP; 1 Sep 2001 01:06:55 -0000
Received: from unknown (HELO imo-r03.mx.aol.com) (152.163.225.99)
  by mta1 with SMTP; 1 Sep 2001 01:06:55 -0000
Received: from Pycyn@aol.com
  by imo-r03.mx.aol.com (mail_out_v31_r1.4.) id r.21.108b2401 (4013)
  for <lojban@yahoogroups.com>; Fri, 31 Aug 2001 21:06:40 -0400 (EDT)
Message-ID: <21.108b2401.28c18ea4@aol.com>
Date: Fri, 31 Aug 2001 21:06:44 EDT
Subject: Re: [lojban] Re: Induction
To: lojban@yahoogroups.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_21.108b2401.28c18ea4_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10535
From: pycyn@aol.com

--part1_21.108b2401.28c18ea4_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 8/31/2001 6:37:09 PM Central Daylight Time, 
jjllambias@hotmail.com writes:


> la nitcion cusku di'e
> 
> >You can "jinvi" based on all sorts of things. Isn't 'conclude' a sort of
> >{jalge jinvi}? And 'deduce' and 'abduce' a {javni jinvi}?
> 
> I don't know, could you expand the tanru? Give a couple of
> examples?
> 
> mi jivbi'o le du'u do se xajmi kei fo le nu do cmila
> I conclude from your laughter that you were amused.
> 
> How does {jalge} enter into it?
> 

As I said, "induction" is about worst word to mess with ("abduction" and 
"conduction" are actually worse but almost no one uses them). There are, of 
course, rules fro all kinds of reasoning and all reasoning leads from 
premises to conclusion (antecedent information to resulting new information). 
Some rules guarantee that the conclusion is at least as certain as the 
premises, others don't, a few pretty much guarantee the opposite. Some are 
mathematically precise, some are fairly precise, some are sloppy below the 
"rule of thumb" level. My advice is to have a good word for deductively 
valid arguments and after that just go with reasoning. If it really matter, 
talk about the paradigm that you are working off of; that probably counts for 
more than the actual rules most of the time.

--part1_21.108b2401.28c18ea4_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><BODY BGCOLOR="#ffffff"><FONT SIZE=2>In a message dated 8/31/2001 6:37:09 PM Central Daylight Time, 
<BR>jjllambias@hotmail.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">la nitcion cusku di'e
<BR>
<BR>&gt;You can "jinvi" based on all sorts of things. Isn't 'conclude' a sort of
<BR>&gt;{jalge jinvi}? And 'deduce' and 'abduce' a {javni jinvi}?
<BR>
<BR>I don't know, could you expand the tanru? Give a couple of
<BR>examples?
<BR>
<BR> &nbsp;mi jivbi'o le du'u do se xajmi kei fo le nu do cmila
<BR> &nbsp;I conclude from your laughter that you were amused.
<BR>
<BR>How does {jalge} enter into it?
<BR></BLOCKQUOTE>
<BR>
<BR>As I said, "induction" is about worst word to mess with ("abduction" and 
<BR>"conduction" are actually worse but almost no one uses them). &nbsp;There are, of 
<BR>course, rules fro all kinds of reasoning and all reasoning leads from 
<BR>premises to conclusion (antecedent information to resulting new information). 
<BR>&nbsp;Some rules guarantee that the conclusion is at least as certain as the 
<BR>premises, others don't, a few pretty much guarantee the opposite. &nbsp;Some are 
<BR>mathematically precise, some are fairly precise, some are sloppy below the 
<BR>"rule of thumb" level. &nbsp;My advice is to have a good word for deductively 
<BR>valid arguments and after that just go with reasoning. &nbsp;If it really matter, 
<BR>talk about the paradigm that you are working off of; that probably counts for 
<BR>more than the actual rules most of the time.</FONT></HTML>

--part1_21.108b2401.28c18ea4_boundary--

