Re: Storing data and code in a Db with LISP-like interface

From: Frank Hamersley <terabitemightbe_at_bigpond.com>
Date: Fri, 28 Apr 2006 01:05:45 GMT
Message-ID: <JTd4g.17761$vy1.2626_at_news-server.bigpond.net.au>


JOG wrote:
> Frank Hamersley wrote:

>> Bob Badour wrote:
>>> Marshall Spight wrote:
>>>> Neo wrote:
>>>>
>>>>>>>> The tomato is *not* a vegetable!
>>>>>>> :) why isn't it?
>>>>>> It has seeds. The seeds make it a fruit. Actually I think it also
>>>>>> qualifies as a berry, which is especially weird.
>>>>> So could one classify the following as fruits since they all have
>>>>> seeds: zuchinni, yellow squash, butternut squash, pumpkins, chilis,
>>>>> peppers, bell peppers, egg plant, bitter melon, okra, chayote, green
>>>>> beans ... and how do I convince the average person, especially for
>>>>> bittermelon. Who is right, the average person or you :)
>>>>
>>>> Neither; I advocate asking an expert for questions like these.
>>>> The botanist is right.
>>> In the end, taxonomy is rather arbitrary. Hierarchy just doesn't work
>>> for things as complex as biological systems.
>> Why do we use them in that case?
>>
>> Cheers, Frank.  [B.Sc (UWA) Zool]

>
> Often because they work well on paper, and we are still traditionally
> tied to these constraints.

Bull - paper has nothing to do with it and its not tradition either.

It is in fact the state of the art after hundreds of years of (western) scientific endeavour. That does not presume it is perfect and certainly does preclude it from advancing in the future but these traits do not enable you to consign it to the rubbish bin.

> Family trees for instance. Hardly hierarchical but construed as such
> due to the conventions of paper. For instance the Queen and Prince
> Phillip have common ancestors, although this is (conveniently)
> unobtainable information from the official royal 'hierarchy'.

This is not a phylogenic structure...it is/was a political statement first.

Cheers, Frank. Received on Fri Apr 28 2006 - 03:05:45 CEST

Original text of this message