Rick: I view the idea of having the web page as the single repository for the currently accepted version of the Behymer genealogy, rather than distributing multiple versions over the mailing list. Of course, the initial posting will have many errors and/or omissions (I'm far from perfect). My idea is to solicit comments re what needs to be changed or annotated and then to post a new version after sufficient inputs have been received. Little by little we would arrive at something that all would agree upon (I hope). I like your suggestion of posting only the first 3 generations from Elder John and soliciting comments, however. That way I can continue to enter new data into TMG, which is mostly for the later generations, anyway, without affecting what is under evaluation and validation by the Behymer list. By limiting the initial posting to the first 3 generations, we would also limit the amout of "misinformation" that is posted to the net. Under the scrutiny (microscope?) of the researchers on this list, I doubt that any misinformation would be allowed to last for very long anyway <grin>. Once the first 3 generations have been validated, I could then post the genealogy though the fourth generation, and we could start the validation process all over again for the additional generation. I hope to post the initial release this weekend. Stay tuned. John Charles Tippet JohnDoeTippet@csi.com ---------- > From: Rick Phillips <Edwin-P@worldnet.att.net> > To: BEHYMER-L@rootsweb.com > Subject: Re: New Behymer Web Page > Date: Tuesday, September 15, 1998 10:11 PM > > John, I think it would be a good idea to post the basic data [that you > might publish on a new web-page] here on the mailing list so we all can > examine it for errors and contribute source materials, if needed. This > would hasten getting an accurate webpage out there, and prevent further > evolution of erroneous assumptions, etc. The first 3 generations or so > would probably be managable at first. > > Thats my two cents worth. I think the concept is a great one! > > Rick Phillips > edwin-p@worldnet.att.net > > > > > > John Tippet wrote: > > > > John: > > > > I was thinking along similar lines as you. In my version, I was also going > > to give priority to correcting mistakes, clarifying assumptions, educated > > guesses, etc, as opposed to adding new material (I am not sure that a > > 1-month verification period is sufficient to reach a concensus on the > > initial release of data). However, in addition, I have a stack of new > > material about 5 inches thick that I have yet to enter into the database > > (along with references). While the list is evaluating the initial release, > > I thought, perhaps naively, that I would have time to input some of this > > material that is in the queue. If I wait to enter all of the new material, > > then it would delay posting of the initial release to the web, however, it > > would be more complete. As I post updates, it will also be difficult to > > keep track of what has changed if I am simultaneously responding to the > > verification process, as well as adding new material. > > > > At this point, I have a working knowledge of html programming (just enough > > to be dangerous) and could probably post the initial release (warts and > > all) as early as this week (or on the weekend). It will also include a > > list of references, which I have found a way to have automatically > > generated with The Master Genealogist, the program I use to keep track of > > everything. > > > > I would be interested in hearing from others on the Behymer list as to how > > they would like me to proceed. Should I publish now, warts and all, or > > wait? Should I delay adding new material to the database until all of the > > verification comments on the initial release have been addressed? (in this > > case I would put my 5" stack of new material on hold). Or would you rather > > I continue to incrementally add the new data that I have, and withhold the > > verification process until some appropriate point in time? > > > > John Charles Tippet > > JohnDoeTippet@csi.com >