From south-bay-birds-bounces+south-bay-birds-archive=[[email protected]] Wed Apr 21 13:04:28 2004
Received: from www.plaidworks.com (localhost [127.0.0.1])
	by plaidworks.com (8.12.9/8.12.9) with ESMTP id i3LK0uH3004180
	for <[[email protected]]>; Wed, 21 Apr 2004 13:00:57 -0700 (PDT)
Received: from grouse.mail.pas.earthlink.net (grouse.mail.pas.earthlink.net
	[207.217.120.116])
	by plaidworks.com (8.12.9/8.12.9) with ESMTP id i3LJxwAg004127
	for <[[email protected]]>;
	Wed, 21 Apr 2004 12:59:58 -0700 (PDT)
Received: from user-38lc1bd.dialup.mindspring.com ([209.86.5.109])
	by grouse.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
	id 1BGNsz-0004iJ-00
	for [[email protected]]; Wed, 21 Apr 2004 12:59:57 -0700
Mime-Version: 1.0 (Apple Message framework v609)
In-Reply-To: <[[email protected]]>
References: <[[email protected]]>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <[[email protected]]>
Content-Transfer-Encoding: 7bit
From: Les Chibana <[[email protected]]>
Subject: Re: [SBB] Abbreviations of birds sighted
Date: Wed, 21 Apr 2004 13:00:47 -0700
To: South Bay Birders <[[email protected]]>
X-Mailer: Apple Mail (2.609)
X-BeenThere: [[email protected]]
X-Mailman-Version: 2.1.5b1
Precedence: list
List-Id: South Bay Birding <south-bay-birds.plaidworks.com>
List-Unsubscribe: <http://www.plaidworks.com/mailman/listinfo/south-bay-birds>, 
	<mailto:[[email protected]]?subject=unsubscribe>
List-Post: <mailto:[[email protected]]>
List-Help: <mailto:[[email protected]]?subject=help>
List-Subscribe: <http://www.plaidworks.com/mailman/listinfo/south-bay-birds>, 
	<mailto:[[email protected]]?subject=subscribe>
Sender: south-bay-birds-bounces+south-bay-birds-archive=[[email protected]]
Errors-To: south-bay-birds-bounces+south-bay-birds-archive=[[email protected]]

And it's probably a good time to remind SBBers that it's good etiquette
to spell out the common name for which you use a code at least once
in your message, preferably at the beginning or in your subject line.

You should be aware that there are also six letter codes in use and
a four-letter code that's different than the Banding Lab's. So, don't
assume that everyone knows what species you're talking about. And
when using codes, be aware that there are some possible double
references, referred to as collisions, and ways to avoid them in these
systems. E.g., some people will use SASP for Savannah Sparrow.
Others might interpret that as Sage Sparrow. A way to avoid this is to
use SAVS for the former and SAGS for the latter. In this example, you
have an option to wait for the Sage Sparrow to be split (if it happens)
and use BESP for the local form of Sage (Bell's) Sparrow. Whichever
you do, just remember, it doesn't take that long to type out the full
name at least once.

Les Chibana, Palo Alto


On Apr 21, 2004, at 8:45 AM, [[email protected]] wrote:

> Hi all:
>
> I have been lurking for several months on this list and am curious 
> about the four letter abbreviations people often use when posting 
> their bird-sightings.  Sometimes there is no spelled out version of 
> the bird's name in the post, and I have to rack my brain to come up 
> with the likely bird's name.
>
> Since apparently this is a widespread & accepted practice (although I 
> have only seen it on this birding list), I am wondering if there is a 
> translation list available somewhere that might make it easier when I 
> am stumped??
>
> Thanks,
>
> Carole
> Sunnyvale

_______________________________________________
Do not post admin requests to the list. They will be ignored.
south-bay-birds mailing list      ([[email protected]])
Help/Unsubscribe/Update your Subscription:
http://www.plaidworks.com/mailman/options/south-bay-birds/south-bay-birds-archive%40plaidworks.com

This email sent to [[email protected]]