From roots-in@roots-l.rootsweb.com Thu Apr 20 11:43:06 2006
Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34])
	by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k3KHh6jb031703;
	Thu, 20 Apr 2006 11:43:06 -0600
Received: from roots-l.rootsweb.com (roots-l.rootsweb.com [66.43.16.22])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k3KHh4Cw011128
	for <roots-approved@rootsweb.com>; Thu, 20 Apr 2006 11:43:04 -0600
Received: from roots-l.rootsweb.com (roots-l [127.0.0.1])
	by roots-l.rootsweb.com (8.12.10/8.12.10) with ESMTP id k3KFAMFI007463
	for <roots-approved@rootsweb.com>; Thu, 20 Apr 2006 11:10:22 -0400
Received: (from roots-in@localhost)
	by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k3KFAMoT007462
	for roots-approved@rootsweb.com; Thu, 20 Apr 2006 11:10:22 -0400
Received: from lists5.rootsweb.com (lists5.rootsweb.com [66.43.27.41])
	by roots-l.rootsweb.com (8.12.10/8.12.10) with SMTP id k3K97bFI005927
	for <roots-in@roots-l.rootsweb.com>; Thu, 20 Apr 2006 05:07:37 -0400
Received: (from slist@localhost)
	by lists5.rootsweb.com (8.12.8/8.12.8) id k3KBe8xq001130
	for roots-in@roots-l.rootsweb.com; Thu, 20 Apr 2006 05:40:08 -0600
X-Envelope-From: logan@familytreeregistry.org Thu Apr 20 05:40:08 2006
Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34])
	by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k3KBe8jb001121
	for <ROOTS-L@lists5.rootsweb.com>; Thu, 20 Apr 2006 05:40:08 -0600
Received: from blazecast9.rdns9.net (62.d0.5546.static.theplanet.com [70.85.208.98])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k3KBe6X9005394
	for <ROOTS-L@rootsweb.com>; Thu, 20 Apr 2006 05:40:07 -0600
Received: from c-68-50-47-207.hsd1.va.comcast.net ([68.50.47.207] helo=ljk)
	by blazecast9.rdns9.net with esmtpa (Exim 4.52)
	id 1FWXW2-00054q-M0
	for ROOTS-L@rootsweb.com; Thu, 20 Apr 2006 06:40:07 -0500
From: "logan@FamilyTreeRegistry.org" <logan@familytreeregistry.org>
To: <ROOTS-L@rootsweb.com>
Date: Thu, 20 Apr 2006 07:39:46 -0400
Message-ID: <BLEGJHDGFKHNDBFLPJFIKECFEKAA.logan@familytreeregistry.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Importance: Normal
In-Reply-To: <200604200334.k3K3Y2h5012355@lists5.rootsweb.com>
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - blazecast9.rdns9.net
X-AntiAbuse: Original Domain - rootsweb.com
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - familytreeregistry.org
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 1.31 (*) BAYES_00,FORGED_RCVD_HELO
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
Sender: roots-in@roots-l.rootsweb.com
Subject: [ROOTS-L] Re: Legality in making a family history book

Deanna Cassidy asked whether it was necessary to receive permission from
people in order to list them in a published family history, and mentioned
that some of her family members had requested that their names be left out.
Aside from legal and ethical questions, there is a very practical
consideration here: if your relatives are upset at the way you are
publicizing information, they are less likely to provide information to you
in the future.

To enable genealogical information to be shared sufficiently to find
researchers with common interests, while respecting individuals' privacy, I
created the free website www.FamilyTreeRegistry.org.  You are welcome to
provide details about your family tree(s) there, without having to provide
individuals' given names, explain relationships between individuals (beyond
being on the same tree), or even provide your own email address (you can be
contacted through the website).  By optionally associating ethnicities,
places, religions, nobility status, and other details to surnames or family
trees, researchers with common interests will still be able to identify your
family trees as being of interest to them.

I hope this will be a useful solution to genealogists concerned about
privacy.  Since GEDCOM is not required (not accepted, even, for privacy
reasons) to register a family tree, you can even register trees that have
not been computerized, such as trees published in old/rare books or
manuscript trees stored in repositories.

Best regards,

Logan


