tigers
[Top] [All Lists]

Fwd: Tiger identification manual

To: tigers@Autox.Team.Net
Subject: Fwd: Tiger identification manual
From: MWood24020 <MWood24020@aol.com>
Date: Sun, 18 Jan 1998 17:55:03 EST
This is a multi-part message in MIME format.

--part0_885164103_boundary
Content-ID: <0_885164103@inet_out.mail.aol.com.1>
Content-type: text/plain; charset=US-ASCII

In a message dated 98-01-18 17:43:32 EST, MWood24020 writes:

<< Continuing the flow of information regarding the Tiger makes sense. Helping
individuals feel comfortable with the potential purchase of an auto which may
or may not be a Tiger makes sense. However, compiling a "how to" book
facilitating and inspiring fraud is a major problem. While this may not in any
way be the intent of this proposed work, it is bound to be a potential issue. 
 As far as TAC goes, STOA has traveled the country making the service
available: SUNI, TE/AE East, Tigers United etc. Also, some individuals
responding to this issue seem to question the expert status of TAC officials.
All I can tell you is that the majority of those involved with TAC have been
involved with Tigers since the beginning and also have extensive experience in
all facets of "Tigering", whether that be restoration, building personalized
cars, compiling Tiger history or other "hands on" work that has led to dozens
of Sunbeams passing through their workshops. They, in the majority of cases,
have just about seen it all and clearly have the expertise to judge a Tiger's
authenticity.
 This leads to another potential problem arising from a "how to tell if you
are looking at a real Tiger" book. How many who read the book and look at
pictures are going to believe that they have become "experts" on the Tiger?
Could this lead to establishing "authenticity" of bogus cars? (I don't mean
this in an arrogant sense, but a little information sometimes can be dangerous
when misapplied!)
 It might make sense to expand the TAC program, within reason, where the
service could be more readily available nationwide. Printing a book which
could serve as a blueprint for fraud makes no sense. >>


--part0_885164103_boundary
Content-ID: <0_885164103@inet_out.mail.aol.com.2>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline

From: MWood24020 <MWood24020@aol.com>
Return-path: <MWood24020@aol.com>
To: jimparent@compuserve.com
Subject: Re: Tiger identification manual
Date: Sun, 18 Jan 1998 17:43:32 EST
Organization: AOL (http://www.aol.com)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit

Continuing the flow of information regarding the Tiger makes sense. Helping
individuals feel comfortable with the potential purchase of an auto which may
or may not be a Tiger makes sense. However, compiling a "how to" book
facilitating and inspiring fraud is a major problem. While this may not in any
way be the intent of this proposed work, it is bound to be a potential issue. 
As far as TAC goes, STOA has traveled the country making the service
available: SUNI, TE/AE East, Tigers United etc. Also, some individuals
responding to this issue seem to question the expert status of TAC officials.
All I can tell you is that the majority of those involved with TAC have been
involved with Tigers since the beginning and also have extensive experience in
all facets of "Tigering", whether that be restoration, building personalized
cars, compiling Tiger history or other "hands on" work that has led to dozens
of Sunbeams passing through their workshops. They, in the majority of cases,
have just about seen it all and clearly have the expertise to judge a Tiger's
authenticity.
This leads to another potential problem arising from a "how to tell if you are
looking at a real Tiger" book. How many who read the book and look at pictures
are going to believe that they have become "experts" on the Tiger? Could this
lead to establishing "authenticity" of bogus cars? 
It might make sense to expand the TAC program, within reason, where the
service could be more readily available nationwide. Printing a book which
could serve as a blueprint for fraud makes no sense.

--part0_885164103_boundary--

<Prev in Thread] Current Thread [Next in Thread>