On Tue, 2004-01-20 at 18:27, Hans Fugal wrote: > Who: > Jacob Fugal, Hans Fugal, Von Fugal, Stuart Jansen, Andrew McNabb, Adam > Ravitch, Evan McNabb, Mike Ong > (If your name isn't listed and you'd like to be involved, reply) > > What: (The itches) > We brainstormed the following possibilities. Some pros and cons listed > here, although I'm sure others were mentioned. Everyone think about them > and discuss them (here until we get the list set up). Remember, the > criteria are small enough to do in a semester and interesting enough to > at least a couple of people so that it gets done. > > Evan suggested working on a scripture reader; con: not genealogy > > CVS for GEDCOM; I'm not sure we all completely agreed on exactly what > this is. It could be almost as simple as using CVS and doing a bit of > pre/post processing, or it could be an entirely ground-up GEDCOM > revision management system. This would almost certainly include figuring > out how to merge two gedcom files that are mostly the same (or perhaps > even gedcom files that are mostly different), a difficult task that many > people have been/are working on. Mike Ong says Dr. Sederberg is making > some good headway in this problem. > > A date authority, or a place authority; The date authority might be > small enough. The place authority would almost certainly be too big. > > A genealogy UI, modular and pluggable to different back ends, etc. cons: > way too big and cross-platform gui issues. > > A conceptual model similar to the GENTECH GDM but better, easier to > understand, and more conceptual (less influenced by databases). Possible > con: little or no programming involved. > > Research log software > > Collaborative research log. The ideas here started spilling into > collaborative genealogy and distributed databases as well. > > When: > 6:30 before UUG meetings > > Infrastructure: > Stuart and his crony Andrew will be setting up the infrastructure. > They'll set up CVS, a mailing list, a basic web site, and possibly a wiki.
> ___________________________________________________________________ > List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list Let me throw another log on the fire. Assumptions: 1. As time goes on, more and more people will have family history servers of some kind on the net. 2.Some of the information on the site will be very sensitive (e.g. could be used for identity theft) 3. There are probably different levels of sensitivity. Problems: 1. How do we make sure the right people are accessing the right information? 2. While password authentication is much better than nothing, can we do better? 3. Without personal one-on-one verification, how do you grant different access priviledges to those who want to sign up? 4. How do you protect against bots or spiders trying to crack a password? 5. How do we do continual (instead or one time) authentication? 6. With all of the authentication, how do we make it easy to access the site? If this is an interesting problem, how do we package it so that it is easy to add to anyone's web site? We'll talk tomorrow. Hopefully the "Genoss" web site will be up soon. By the way, I am using "Genoss" as the name right now. We can certainly change it. There is no website with the name "genoss.com", and, "Genoss" in German can mean "enjoy". -- Scott N. Woodfield 2232 TMCB Computer Science Dept. Brigham Young University Provo, UT 84602 801 378 2915 ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
