On Wed, 29 Aug 2007 07:11:23 -0400, Diana Riggs <rigger@hotmail.com> wrote: > The plan is to sell the info to marketing companies. Cite please?
On 29 Aug 2007 23:34:50 GMT, Dave Hinz <DaveHinz@gmail.com> wrote in soc.genealogy.misc: >On Wed, 29 Aug 2007 07:11:23 -0400, Diana Riggs <rigger@hotmail.com> wrote: >> The plan is to sell the info to marketing companies. > >Cite please? junk Anyway, it is known for years that marketing companies are purchasing information from census, but the census data can be used for so many more useful usage, for example to see where you will need a new school or a new hospital. The basic purpose of census is not to help marketing companies but they can use the census data and this is not a plot. Denis -- 0 Denis Beauregard - /\/ Les Français d'Amérique du Nord - www.francogene.com/genealogie--quebec/ |\ French in North America before 1721 - www.francogene.com/quebec--genealogy/ / | Maintenant sur cédérom, début à 1765 oo oo Now on CD-ROM, beginnings to 1765
The plan is to sell the info to marketing companies. , 06 Jul 2006 11:41:51 -0500, "Steve W. Jackson" <stevewjackson@knology.net> wrote: >In article <Pine.LNX.4.64.0607052013350.751@kd6lvw.ampr.org>, > "D. Stussy" <spam@bde-arc.ampr.org> wrote: > >> On Mon, 3 Jul 2006, akak01000101 wrote: >> > Since I saw other census questions here, I thought I'd post this >> > here.... >> > >> > Remember the days of about 10 questions that just dealt with your name, >> > sex, and race, etc...? Basic questions. Now they want to know things >> > like, where you work, when you leave for work, how much you pay for >> > various things, cars you drive, fuel you use, etc.... >> > >> > This reads like an application you fill out when you want someone to >> > rob your home or steal your identity. Only thing that is missing, thank >> > god, is your SS#. >> > >> > Now if you have a problem filling out all this information, the >> > government says they will fine you up to $5,000. Does anyone else have >> > a problem with this? >> >> I have a problem with it. Any question that exceeds the constitutional >> mandate of the census (to make certain every person is counted - and counted >> only once - meaning identity information only) should be optional. To >> penalize for it is wrong. To penalize for not answering about one's name, >> age, etc. (i.e. personal identity) should be done, with exceptions for cause >> (e.g. hospitalization, outside the U.S., etc.). > >Aside from the fact that there is *no* 2006 US census and therefore a >question about the entire purpose of this thread... > >That so-called Constitutional mandate says nothing about counting every >person once and only once -- though it should have done so. The census >is called for in Article 1 Section 2. It originally called for counting >of all free persons, not counting Indians, and for counting three-fifths >of all "other persons" -- meaning slaves. But it also specified when >the count would be done by the Congress and then said "in such Manner as >they shall by Law direct". That seems reasonably broad. > >Given the diversity of the American population, it's reasonable to go >beyond a simple head count. There are numerous benefits and advantages >that the country derives from having some meaningful demographic data. >As someone interested in genealogy, I'm certainly aware of how much more >I wish were in older censuses, and I don't have any issues with having >that much accessible to my descendants someday, provided there's nothing >there which puts me at risk in the present. > >Before forming an opinion concerning penalties for not answering, >however, I'd like to see something more concrete on such a plan.
Chinese antique, wonderful treasure big collection ,invitation visit Antique 1912-1949 Porcelain teapot 528 chinaware 400 ,Website extreme security,invitation visit, Thanks ! Jianxiong Xu Address: Shengzhou Zhejiang China Tel:(86-575)83103731 Website:http://www.xjx588.com E-mail:xjx_588@tom.com
Try http://www.teafor2.com/ It's a great site and they take voluntary donations. I even found markers for my great grandparents there. Keith In article <JM43qr.H6w@news.boeing.com>, lintardspamtrap@scotts-home.net says... > I used to belong to one, where people would request a picture of a grave > sight. I've long > lost the links and cant seem to find them anymore. > > Id like to volunteer again if there is such a service. > > >
On 01 Aug 2007 in soc.genealogy.misc, R. Scott wrote: > I used to belong to one, where people would request a picture of a > grave sight. I've long lost the links and cant seem to find them > anymore. > > Id like to volunteer again if there is such a service. FindAGrave has such a function: http://findagrave.com/ I don't find a specific description of the program, but if you click around and visit a cemetery's main page, if is has photo requests, they'll show up. This is the listing for Holy Cross cemetery in Brooklyn, New York, USA: http://www.findagrave.com/cgi-bin/fg.cgi?page=cr&CRid=64166 Cemeteries by location: http://www.findagrave.com/tocs/geographic.html -- Joe Makowiec http://makowiec.org/ Email: http://makowiec.org/contact/?Joe
I used to belong to one, where people would request a picture of a grave sight. I've long lost the links and cant seem to find them anymore. Id like to volunteer again if there is such a service.
"R. Scott" <lintardspamtrap@scotts-home.net> wrote in message news:JM43qr.H6w@news.boeing.com... > I used to belong to one, where people would request a picture of a grave > sight. I've long > lost the links and cant seem to find them anymore. > > Id like to volunteer again if there is such a service. > > You might check some of these sites. http://www.usgenweb.org/volunteers/ http://www.familyworkings.com/links/volunteer.htm http://genealogy.allinfoabout.com/features/cemeteries.html http://www.myresearchers.com/ Joe in Texas
Sorry, Stockport.Cheshire, England "Joe Makowiec" <makowiec@invalid.invalid> wrote in message news:Xns997F4E5FF8A3CmakowiecatnycapdotrE@66.250.146.128... > On 01 Aug 2007 in soc.genealogy.misc, Brian Hopwood wrote: > > > Is anyone researching the Gordon surname in Stockport ? > > Particularly, an Alfred Gordon born about 1871, married to Mary > > Edwards in 1890. > > Which Stockport? > > http://www.geonames.org/search.html?q=stockport > http://www.catb.org/~esr/faqs/smart-questions.html > http://www.rootsweb.com/~surnames/goodbad > > -- > Joe Makowiec > http://makowiec.org/ > Email: http://makowiec.org/contact/?Joe
On 01 Aug 2007 in soc.genealogy.misc, Brian Hopwood wrote: > Is anyone researching the Gordon surname in Stockport ? > Particularly, an Alfred Gordon born about 1871, married to Mary > Edwards in 1890. Which Stockport? http://www.geonames.org/search.html?q=stockport http://www.catb.org/~esr/faqs/smart-questions.html http://www.rootsweb.com/~surnames/goodbad -- Joe Makowiec http://makowiec.org/ Email: http://makowiec.org/contact/?Joe
Is anyone researching the Gordon surname in Stockport ? Particularly, an Alfred Gordon born about 1871, married to Mary Edwards in 1890. Many Thanks ! Brian Hopwood
Dear friends, We posted the Table of Ranks of the Russian Empire on our site in English. This law with some changes worked in Russia from 1722 till 1917. If you are interested, you can see it here: http://rusgenealogy.webng.com/table.htm We hope these pages will be of use for you.
On Jul 23, 4:16 am, elie <elie387@gmail.com> wrote: > Title: Printing, Publishing > > Onlineyearbooks is a trading style of OS Print And Publishing Limited. > We have: > · an international pedigree, > · strong internal controls and > · carefully managed costs > > For more enquiries visit us aswww.onlineyearbooks.co.uk > or > Email us:marketing@onlineyearbooks.co.uk > > Kind Regards > Michael Bamford (Business Development Manager) > Keywords: Books Printing , Brochure printing, Online yearbook printing Spam message seen in many newsgroups. Details for reporting this: Domain name: onlineyearbooks.co.uk Registrant: os international llc Registrant type: Non-UK Corporation Registrant's address: po box 484 huntingdon cambs PE29 1WP GB Registrar: Pipex Communications UK Ltd t/a 123-Reg.co.uk [Tag = 123-REG] URL: http://www.123-reg.co.uk Relevant dates: Registered on: 15-Feb-2006 Renewal date: 15-Feb-2008 Last updated: 15-Feb-2006 Registration status: Registered until renewal date. Name servers: ns1.greatvaluewebhost.com ns2.greatvaluewebhost.com -Trace: posting.google.com 1185185770 24531 127.0.0.1 (23 Jul 2007 10:16:10 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Mon, 23 Jul 2007 10:16:10 +0000 (UTC) User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; DigExt; FunWebProducts; .NET CLR 1.0.3705; InfoPath. 1),gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: x35g2000prf.googlegroups.com; posting- host=122.160.0.7; posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0 Spam will be noted in antispam newsgroup shortly so keywords will direct the spammer to that group too.
Title: Printing, Publishing Onlineyearbooks is a trading style of OS Print And Publishing Limited. We have: · an international pedigree, · strong internal controls and · carefully managed costs For more enquiries visit us as www.onlineyearbooks.co.uk or Email us:marketing@onlineyearbooks.co.uk Kind Regards Michael Bamford (Business Development Manager) Keywords: Books Printing , Brochure printing, Online yearbook printing
Lars Eighner wrote: > In our last episode, <f7n62n$puv$1$8302bc10@news.demon.co.uk>, the lovely > and talented Peter J Seymour broadcast on soc.genealogy.misc: > > >>What I meant to add is that this is the sort of justification put >>forward by the LDS for their XML Gedcom. It didn't help them much. In my >>opinion, XML is a side issue. It may or may not have a role to play, >>depending on how people want to proceed. Appropriate data design is what >>counts and should come before implementation issues such as XML. > > > The main advantage of XML is that namespaces will make it possible (and in > well-behaved applications, necessary) for each product to define what it > means by its tags. At present, that will make it possible for human > developers to translate one format to another. The ultimate goal would seem > to be to automate the business of translating from one namespace to another, > so a very smart application that used a "spouse" tag could figure out how to > handle input that used "HUSB" and "WIFE" without a human developer having to > tell it. Of course, it never will be possible to get all the information > from a more flexible format into a more restrictive one without losing some > information. > And of course then you'll run into situations where the data-entry human dithers and shivers and agonizes over what to call his sibling's house-mate: there's no legal marriage, so "Spouse" is wrong; the two are opposite sexes so "Partner" seems wrong (or they're not opposite sexes so "Partner" seems a bit too precise); "Companion" sounds like a pet dawg and isn't strong enough; "mate" sounds cold; "boy-toy" and "old fool's plaything" won't hack it with the great-aunts ... This is much like a discussion about the use of the word "died" in the sentence, "George died on the 3rd of September 1805". In one newspaper, on one single day, I found 27 different phrases used to replace "died". The next day I found 6 different instances, and on the day after than 9 more. The programmer simply cannot foresee all the conceivable variations on any given word such as Birth, Death, marriage, spouse, because if he even tries, the program will very rapidly become (as said in one of the Star Trek movies) the one that swallowed Jupiter. IMO Cheryl
Everett M. Greene wrote: > melsonr@aragorn.rgmhome.net (Robert Melson) writes: > >>Wes Groleau <groleau+news@freeshell.org> writes: >> >>>Robert Melson wrote: >>> >>>>think applications like phpGedView, The Next Generation and, to >>> >>>Much as I like both of those, I have to >>>agree with Dr. Leverich--they really don't >>>offer any major innovation. They're just >>>improvements on the user interface of the >>>same basic thing. >> >>I don't disagree. I very much like pGV, myself, but >>am certainly aware that overall it's not really a >>ground breaking application. Still, it does illustrate >>the point I was attempting to make - all the capability >>resides in/on the server, making it unnecessary for the >>local machine to install anything more forbidding than >>a browser. This, I think, is where things are probably >>heading <waves hands> in genealogy as well as in other >>areas. > > > This is akin to saying that terrorists are well-financed and > fanatical so we might as well just let them win. Sun is going this way with some of their office systems in effective returning to the data terminal as a "thin client" ... server-based, server-centric and network computing. eg HP Compaq t5720 Thin Client with Genuine Windows XP Embedded. The t5720 delivers desktop-like features and support for local applications. This unit is the ideal choice for businesses featuring the AMD Geode NX 1500 processor with 512 MB of Flash memory and either 256 MB or 512 MB of DDR RAM standard. Sun Ray 270 Virtual Display Client - Overview Anywhere you can install a Sun Ray thin client device instead of a PC, you can potentially save money, reduce energy usage, and improve security. a Sun V20 Server running Solaris 10 for Sparc, and two Sun Ray 2FS clients, each with a single 20-inch LCD monitor. The network between the server and the Sun Ray clients was a dedicated 100Mbps segment, with another NIC on the server linked to the overall lab network. With the server running, powering on a Sun Ray client would bring up a Solaris Desktop log-in quite quickly, and from there, the experience was more or less like working on a local system, including stereo sound and USB device support. http://www.infoworld.com/article/06/08/10/33TCsunray_1.html my internet is 2 to 6 mb/sec with 20/20 available if I wish to pay no point because the route across USA from east to west is much slower than that about midnight in New York and all the tracerts to aol.com cnn.com give time outs ancestry.com is very quick I don't know if they now have a european server farm images seem subjectively much quicker this summer than laat their networked trees are proving very popular with newbies who are also discovering tribalpages so instead of gedcom a high tech xml server and social networking Hugh W -- a wonderful artist in Denmark http://www.ingerlisekristoffersen.dk/ Beta blogger http://snaps4.blogspot.com/ photographs and walks old blogger GENEALOGE http://hughw36.blogspot.com/ MAIN BLOG
In article <20070720.7998798.A351@mojaveg.lsan.mdsg-pacwest.com>, mojaveg@mojaveg.lsan.mdsg-pacwest.com (Everett M. Greene) writes: > melsonr@aragorn.rgmhome.net (Robert Melson) writes: <snip> >> I don't disagree. I very much like pGV, myself, but >> am certainly aware that overall it's not really a >> ground breaking application. Still, it does illustrate >> the point I was attempting to make - all the capability >> resides in/on the server, making it unnecessary for the >> local machine to install anything more forbidding than >> a browser. This, I think, is where things are probably >> heading <waves hands> in genealogy as well as in other >> areas. > > This is akin to saying that terrorists are well-financed and > fanatical so we might as well just let them win. Eh? How do you arrive at that conclusion? As the old ads for "The National Enquirer" had it, "inquiring minds want to know." Bob Melson -- Robert G. Melson | Rio Grande MicroSolutions | El Paso, Texas ----- "People unfit for freedom---who cannot do much with it---are hungry for power." ---Eric Hoffer
Everett M. Greene wrote: > Wes Groleau <groleau+news@freeshell.org> writes: >> Everett M. Greene wrote: >> > Not having looked at the XML-based proposals, I'm not familiar >> > with what's being proposed, but if the preceding is a valid >> > example, I don't see any significant benefit. As you say, >> > there's not semantic difference and clutter is being added for >> > no obvious reason. >> >> That's why I said, it's like going from English to pig-Latin. >> Semantically there is no difference. Any flaws in the GEDCOM >> data model are in both versions. And there are flaws, though >> GEDCOM obviously is not completely useless. (And that's why >> no one seems to be in a big hurry to fix it.) >> >> I can think of two advantges of XML: >> >> 1. Open source and commercial XML parsers are everywhere. >> >> 2. If you know how to use XSL, you can write a presentation >> stylesheet. Your GEDCOM (XML) file plus the XSL is all >> that's necessary for a sufficiently modern browser to >> make a fairly nice web page. In other words, instead >> of writing code to transform GEDCOM into HTML, you write >> a high-level spec for that code, and the user's browser >> does all the rest of the work! > > Those are valid points for those who are interested in generating > Web-oriented presentations. But what portion of people dealing > with genealogy are interested in doing that? Are you saying that we should be bound by the limited requirements of the least ambitious? Let's look at some of the possibilities if we move genealogy software into the 21st century: First there's what's known in the trade as re-purposing of data (no, I don't particularly like the word): Use of a stylesheet to convert an XML export to HTML is referred to above. Use of a stylesheet to convert an XML export to SVG ("SVG is a language for describing two-dimensional graphics and graphical applications in XML." - W3C). Your data converted to a rescalable graphics format which can then be massaged by SVG-aware graphics packages, converted to PDF, JPEG or whatever. Use of a stylesheet to convert an XML export to Formatting Objects (FO). FO is an XML schema to describe page formatting. FO can then be converted to PDF, postscript, RTF, Word, OpenOffice etc. Secondly there's data re-use. There would be the necessity of exchanging data with legacy applications using Gedcom 5.5 or earlier. Conversion of an XML export to non-XML is easy; just use a stylesheet. Conversion the other way is less less easy as we would need parsers for the non-XML format. Then, if anyone were to develop packages for related fields, such as local history, there quite a number of people would find value in moving data both ways. Anyone starting from scratch with such an application would be thinking of XML as an export/import mechanism. With our hypothetical genealogical XML problem it would be quite easy - just write a stylesheet. Finally if big archives were to make data available in machine-readable form this would be XML (for instance A2A seems to be XML internally converted to HTML for output; converting this back to XML is somewhat like extracting an egg from an omelet so I've written to them to ask if raw XML could be provided). Again, import of such data into any other XML-enabled package would be easy - you've guessed it, just write a stylesheet. -- Ian Goddard Hotmail is for the benefit of spammers. The email address that I actually read is igoddard and that's at nildram dot co dot uk
New Jewish and other United States ethnic - family history resources online, are genealogy oriented and cross-referenced to country regions of origin, at: UNITED STATES. http://www.academic-genealogy.com/regionalgenealogy.htm#usa
melsonr@aragorn.rgmhome.net (Robert Melson) writes: > Wes Groleau <groleau+news@freeshell.org> writes: > > Robert Melson wrote: > >> think applications like phpGedView, The Next Generation and, to > > > > Much as I like both of those, I have to > > agree with Dr. Leverich--they really don't > > offer any major innovation. They're just > > improvements on the user interface of the > > same basic thing. > > I don't disagree. I very much like pGV, myself, but > am certainly aware that overall it's not really a > ground breaking application. Still, it does illustrate > the point I was attempting to make - all the capability > resides in/on the server, making it unnecessary for the > local machine to install anything more forbidding than > a browser. This, I think, is where things are probably > heading <waves hands> in genealogy as well as in other > areas. This is akin to saying that terrorists are well-financed and fanatical so we might as well just let them win.