
www.Usenet.com
| <-- __Chronological__ --> | <-- __Thread__ --> |
Good Morning Jo! Your scope appears enormous, compassionate and humbling...... I do applaud your contribution to this academia. Would that there were more persons like you. Thank you for your kind consideration.... Carl E. Jo Schaper <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > [EMAIL PROTECTED] wrote: > > <snip> > > > > Yes, I am concerned about our environment and yes, I do read articles > > about my concerns and I will continue to ask questions. I truly don't > > mean to hurt anyones feelings or ruffle feathers and I certainly > > wouldn't and don't object to anyone earning a living. If my questions > > and ignorance bothered anyone, for that I am sorry. I would rather > > risk being viewed as ignorant than remain so...... Could you, any of > > you suggest better reading, more balanced... ? Is there anything I > > could do to help? <snip> > > > > Carl E. > > Dear Carl, > > I wish I could recommend some 'more balanced' approach, but the only one > I know of is to read all biased sides throw in the > government/regulatory assessment, and draw your own conclusions. For > example: Missouri has a long standing lead industry and resulting lead > pollution problems, from mining and smelting. The only sources for > firsthand information are the lead company, government mining and > regulatory documents, environmental group literature and some academic > papers by professors/students working in the lead belt. To understand > the scope of things you have to read the PR releases from the company, > talk to the workers, read the anti-lead diatribes from the enviros, dig > in the library and public documents for government assessments, talk to > the locals who may/may not be affected by the lead industry (positive > and negative) and dig through academic tomes. > The local press may or may not be fair--often 'investigatory' reporting > has a point of view to promote, even in the 'objective reporting'. What > helps, too, it to have a basic understanding of the substance, its uses, > its hazards, how it is mined, etc. A beginning chemistry or mineral text > can often furnish this. If you have an opportunity to visit a > phosphate mine I would take it. Often the workers are a good source of > information--they know the industry, (pluses and minuses) and generally > are more likely to tell a many-sided truth than a company news release. > > What can you do? 1) Become as well-informed on the issue as you can. > 2) You sent us to a fine government website. They have a few > opportunities for citizen participation listed. If nothing else, attend > their meetings if you can. You are more likely to change the mind of a > county commissioner or local permitter than to influence US policy on > phosphate to North Korea, but maybe you can present some facts to alter > the course of mining where you live. If you go into this with the idea > that you can be part of the solution, you can. Remember that old saw: > Think Globally Act Locally? It actually can be made to work! > 4) Find some aspect of the phosphate mining issue and become an expert > on it. How the mining affects groundwater. What are air quality issues? > Don't try to do it all, but by picking one point, you may be able to > become the spokesman for it. There were many arguments against an Army > Corps dam here 25 years ago--a friend of mine gave over 400 lectures on > how the dam would affect caves and vice versa--he was well informed, an > self educated, with only a high school degree, but he ended up debating > Army Corps colonels on this point of their plan. The dam was eventually > voted down by 64% in a non-binding referendum, which caused the > politicians to back off, and the dam was never built. > 5)Always be polite and respectful of people with opposing views. There > are none of us who have all the answers--many development decisions are > a result of a string of compromises a mile long. > > Hope this gives you some ideas how to proceed. > best wishes, > Jo
| <-- __Chronological__ --> | <-- __Thread__ --> |