[From nobody Mon Jan 4 16:11:07 2010 Authentication-Results: isp.att.net; domainkey=hardfailed (invalid domain coverage) header.From=apgpubliclist-bounces@apgen.org Authentication-Results: isp.att.net; dkim=hardfailed (bad signature) header.i=@gmail.com Received: from sccwmxc02.att.net ([204.127.208.82]) by isp.att.net (frfwmxc05) with ESMTP id <20100104224604M05003lo8re>; Mon, 4 Jan 2010 22:46:04 +0000 Received: from mailapp0.msomt.modwest.com ([204.11.245.152]) by att.net (sccwmxc02) with ESMTP id <20100104224604s020053k6ae>; Mon, 4 Jan 2010 22:46:04 +0000 X-Originating-IP: [204.11.245.152] Received: from mailapp0.msomt.modwest.com (localhost [127.0.0.1]) by mailapp0.msomt.modwest.com (Postfix) with ESMTP id 1E57328AEE8; Mon, 4 Jan 2010 15:46:03 -0700 (MST) Received: from mfe5.msomt.modwest.com (mfe5.msomt.modwest.com [204.11.245.169]) by mailapp0.msomt.modwest.com (Postfix) with ESMTP id 6DFFB28AEC5 for <apgpubliclist@mailapp.modwest.com>; Mon, 4 Jan 2010 15:46:01 -0700 (MST) Received: from mail-bw0-f226.google.com (mail-bw0-f226.google.com [209.85.218.226]) by mfe5.msomt.modwest.com (Postfix) with ESMTP id 74D2A268072 for <APGpubliclist@apgen.org>; Mon, 4 Jan 2010 15:45:59 -0700 (MST) Received: by bwz26 with SMTP id 26so10392832bwz.27 for <APGpubliclist@apgen.org>; Mon, 04 Jan 2010 14:45:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=mjGmfCij+OnM3P5GeONyJGYI9WXowa5QMqpExuZUQhk=; b=POtqe92BX69A8OLHRVLveJTztofR/H6ZrgdfoAaUBr08BpLEkcXDnRYrr1y3QROCRU 2hkt2ZflohP+rQplsqAeXm6omleJBnhVBmtw+B4aIQXyTtNtAsbzjrNOiUwcANHlkafj /YrTaiUVSxfmU1u+FNzZAZQiRRXrfvfzGgP7c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=LR8s/j6K2ZpdpSkObrqt6mGpWMZGOXOpR0S3q5u2Cvs3aMIky+ZOox0QFcxrF/IYLl V/KqvagIwln0ubvarYpAAcsNV0TnyyBp1lzSsKZYeQ1BUg83s/ktgbs3Ajk5k7UD8pl4 paCer1bt8VDMEyI8pi/Uq45tmzrOKW7dDF99U= MIME-Version: 1.0 Received: by 10.204.0.70 with SMTP id 6mr10610192bka.85.1262645158233; Mon, 04 Jan 2010 14:45:58 -0800 (PST) Date: Mon, 4 Jan 2010 16:45:58 -0600 Message-ID: <3bf060001001041445s57164375h932fee890ba9eaf0@mail.gmail.com> From: Michael John Neill <mjnrootdig@gmail.com> To: APGpubliclist@apgen.org Content-Type: multipart/alternative; boundary=00151750de3c2248f2047c5e7c0f X-Modwest-MailScanner: Found to be clean X-Modwest-MailScanner-From: mjnrootdig@gmail.com Subject: [APG Public List] pre-writing obituaries-was predeceased children in obituaries X-BeenThere: apgpubliclist@apgen.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "APG Public List is an unmoderated mailing list sponsored and archived by the Association of Professional Genealogists." <apgpubliclist.apgen.org> List-Unsubscribe: <http://mailapp.modwest.com/mailman/listinfo/apgpubliclist>, <mailto:apgpubliclist-request@apgen.org?subject=unsubscribe> List-Archive: <http://mailapp.modwest.com/pipermail/apgpubliclist> List-Post: <mailto:apgpubliclist@apgen.org> List-Help: <mailto:apgpubliclist-request@apgen.org?subject=help> List-Subscribe: <http://mailapp.modwest.com/mailman/listinfo/apgpubliclist>, <mailto:apgpubliclist-request@apgen.org?subject=subscribe> Sender: apgpubliclist-bounces@apgen.org Errors-To: apgpubliclist-bounces@apgen.org --00151750de3c2248f2047c5e7c0f Content-Type: text/plain; charset=ISO-8859-1 Pre-writing the obituary is an excellent idea, but remember when you are dead, you are dead and do have limited control. A relative of mine died a few years ago and left a lengthy obituary with the funeral director to be published upon their demise. The family said they wanted nothing published whatsoever. There was no death notice and no obituary, nothing. Unusual, but not unheard of. Genealogical societies might want to consider publishing occasional biographies of members in their newsletters as a way of preserving them for future generations. Space would be less of an issue and they would get preserved, particularly if the publications were submitted to FHL, LOC, ACPL, etc. Sometimes we are a little too focused on the past and neglect to preserve some of the present. Just my 2cents. Michael > ------------------------------------ > Michael John Neill > Weekly "Casefile Clues" Column > http://www.casefileclues.com > > > --00151750de3c2248f2047c5e7c0f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div class=3D"gmail_quote"> <div>Pre-writing the obituary is an excellent idea, but remember when you a= re dead, you are dead and do have limited control. A relative of mine died = a few years ago=A0and left a lengthy obituary with the funeral director to = be published upon their demise. The family said they wanted nothing publish= ed whatsoever.=A0=A0There was no death notice and no obituary, nothing. Unu= sual, but not unheard of. </div> <div>=A0</div> <div>Genealogical societies might want to consider publishing occasional bi= ographies of members in their newsletters as a way of preserving them for f= uture generations. Space would be less of an issue and they would get prese= rved, particularly if the publications were submitted to FHL, LOC, ACPL, et= c. Sometimes we are a little too focused on the past and neglect to preserv= e some of the present. </div> <div>Just my 2cents. </div> <div>Michael</div> <div>=A0</div> <div>=A0</div> <div>=A0</div> <blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0= px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> <div> <div style=3D"FONT-SIZE: 12pt; COLOR: #000000; FONT-FAMILY: Times New Roman= ">------------------------------------<br>Michael John Neill<br>Weekly &quo= t;Casefile Clues&quot; Column<br><a href=3D"http://www.casefileclues.com">h= ttp://www.casefileclues.com</a><br> <br><br></div></div></blockquote></div> --00151750de3c2248f2047c5e7c0f-- ]