<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: Potentially hazardous asteroid conferences</title>
	<atom:link href="http://www.spacepolitics.com/2007/03/13/potentially-hazardous-asteroid-conferences/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.spacepolitics.com/2007/03/13/potentially-hazardous-asteroid-conferences/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=potentially-hazardous-asteroid-conferences</link>
	<description>Because sometimes the most important orbit is the Beltway...</description>
	<lastBuildDate>Wed, 17 Sep 2014 13:35:41 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.0.38</generator>
	<item>
		<title>By: Space Politics &#187; NEO hearing next week</title>
		<link>http://www.spacepolitics.com/2007/03/13/potentially-hazardous-asteroid-conferences/#comment-23381</link>
		<dc:creator><![CDATA[Space Politics &#187; NEO hearing next week]]></dc:creator>
		<pubDate>Wed, 03 Oct 2007 10:31:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/03/13/potentially-hazardous-asteroid-conferences/#comment-23381</guid>
		<description><![CDATA[[...] comes more than six months after NASA completed the report mentioned in the hearing&#8217;s title, which concluded that significantly more money would be needed to meet the goals mandated by Congress.... That report, which also discussed potential deflection strategies, was criticized sharply by [...]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] comes more than six months after NASA completed the report mentioned in the hearing&#8217;s title, which concluded that significantly more money would be needed to meet the goals mandated by Congress&#8230;. That report, which also discussed potential deflection strategies, was criticized sharply by [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D</title>
		<link>http://www.spacepolitics.com/2007/03/13/potentially-hazardous-asteroid-conferences/#comment-10738</link>
		<dc:creator><![CDATA[D]]></dc:creator>
		<pubDate>Thu, 15 Mar 2007 00:16:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/03/13/potentially-hazardous-asteroid-conferences/#comment-10738</guid>
		<description><![CDATA[&lt;i&gt;During that meeting NASA released its Congressionally-mandated report on how it would be able to detect 90 percent of all near Earth asteroids 140 meters in diameter and larger by 2020. (The report itself was quietly placed on the web late last week by NASA.) &lt;/i&gt;

That&#039;s misleading. As talked openly about at the Conference, the study mandated by Congress is not being released publicly - or even  to the Congress.  What was released (above) is a 28-page redaction overseen, as I understand it from what was said at the Conference, by the White House OMB. The Study itself - a glossy, 271-page report - has, it was reported last week at the Conference, only been distributed  - hardcopy only - to 100 people; many/most of them, members of the NASA-led effort who produced the report.
One person who requested a copy of the &#039;real&#039; report from NASA HQ was told, by email:
&quot;The document you requested was distributed as in hard copy as a &quot;thank you&quot; to team members and is not an official, distributable NASA publication.  Copies beyond those for the study team are not available.
 
An electronic copy will not be distributed or posted by NASA.  The document does not meet federal accessibility regulations (Section 508) and the cost of bringing the study document in line with these regulations has been determined to be prohibitive.&quot;

It is my understanding that a Freedom of Information Act request has now  been submitted for it.  I do not know what the differences are between the two reports.

I believe strongly in the democratic process - if it is allowed to work.  The Congressional study mandate was proper, far reaching, and an example of Congress actually doing its job well: asking for a technical assessment, and options, from one of the government&#039;s agencies on an issue of national and planetary safety and security, clearly a government responsibility.  It is also correctly not a partisan issue; in fact, it&#039;s primary proponent  was (still is, actually) a conservative Republican.
  Even if Congress received the full study, and decided to do nothing (e.g, no increase or re-prioritizing of the government budget to add more focus to the NEO issue), at least it would have been publicly debated and decided; so if it needs to be revisited later, everyone knows what was decided, and why.  We may only be shooting ourselves in the foot in not openly providing Congress all the information they asked for on this safety issue.]]></description>
		<content:encoded><![CDATA[<p><i>During that meeting NASA released its Congressionally-mandated report on how it would be able to detect 90 percent of all near Earth asteroids 140 meters in diameter and larger by 2020. (The report itself was quietly placed on the web late last week by NASA.) </i></p>
<p>That&#8217;s misleading. As talked openly about at the Conference, the study mandated by Congress is not being released publicly &#8211; or even  to the Congress.  What was released (above) is a 28-page redaction overseen, as I understand it from what was said at the Conference, by the White House OMB. The Study itself &#8211; a glossy, 271-page report &#8211; has, it was reported last week at the Conference, only been distributed  &#8211; hardcopy only &#8211; to 100 people; many/most of them, members of the NASA-led effort who produced the report.<br />
One person who requested a copy of the &#8216;real&#8217; report from NASA HQ was told, by email:<br />
&#8220;The document you requested was distributed as in hard copy as a &#8220;thank you&#8221; to team members and is not an official, distributable NASA publication.  Copies beyond those for the study team are not available.</p>
<p>An electronic copy will not be distributed or posted by NASA.  The document does not meet federal accessibility regulations (Section 508) and the cost of bringing the study document in line with these regulations has been determined to be prohibitive.&#8221;</p>
<p>It is my understanding that a Freedom of Information Act request has now  been submitted for it.  I do not know what the differences are between the two reports.</p>
<p>I believe strongly in the democratic process &#8211; if it is allowed to work.  The Congressional study mandate was proper, far reaching, and an example of Congress actually doing its job well: asking for a technical assessment, and options, from one of the government&#8217;s agencies on an issue of national and planetary safety and security, clearly a government responsibility.  It is also correctly not a partisan issue; in fact, it&#8217;s primary proponent  was (still is, actually) a conservative Republican.<br />
  Even if Congress received the full study, and decided to do nothing (e.g, no increase or re-prioritizing of the government budget to add more focus to the NEO issue), at least it would have been publicly debated and decided; so if it needs to be revisited later, everyone knows what was decided, and why.  We may only be shooting ourselves in the foot in not openly providing Congress all the information they asked for on this safety issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D. Messier</title>
		<link>http://www.spacepolitics.com/2007/03/13/potentially-hazardous-asteroid-conferences/#comment-10699</link>
		<dc:creator><![CDATA[D. Messier]]></dc:creator>
		<pubDate>Tue, 13 Mar 2007 20:27:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/03/13/potentially-hazardous-asteroid-conferences/#comment-10699</guid>
		<description><![CDATA[Not much NASA money for asteroid protection. Or environmental protection. Shows where the bushadmin&#039;s priorities lie. Get Aerospace Corp. to do a study then ignore it. It happened before with Hubble. Seems to be happening again. 

Bush&#039;s priorities: run out the clock for the next 22 months, let whoever takes over deal with the mess. A fine strategery.]]></description>
		<content:encoded><![CDATA[<p>Not much NASA money for asteroid protection. Or environmental protection. Shows where the bushadmin&#8217;s priorities lie. Get Aerospace Corp. to do a study then ignore it. It happened before with Hubble. Seems to be happening again. </p>
<p>Bush&#8217;s priorities: run out the clock for the next 22 months, let whoever takes over deal with the mess. A fine strategery.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donald F. Robertson</title>
		<link>http://www.spacepolitics.com/2007/03/13/potentially-hazardous-asteroid-conferences/#comment-10693</link>
		<dc:creator><![CDATA[Donald F. Robertson]]></dc:creator>
		<pubDate>Tue, 13 Mar 2007 16:55:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/03/13/potentially-hazardous-asteroid-conferences/#comment-10693</guid>
		<description><![CDATA[Jeff:  &lt;i&gt;One suspects that if someone dropped a billion dollars into Mike Griffinâ€™s lap, enhanced asteroid searches would not be on the top of his list of spending priorities.&lt;/i&gt;

I suspect he&#039;d find some way to use an Ares-1 launched Orion for this task!  (And, if he did, cynical as it may be, I would fully support him in that.)

-- Donald]]></description>
		<content:encoded><![CDATA[<p>Jeff:  <i>One suspects that if someone dropped a billion dollars into Mike Griffinâ€™s lap, enhanced asteroid searches would not be on the top of his list of spending priorities.</i></p>
<p>I suspect he&#8217;d find some way to use an Ares-1 launched Orion for this task!  (And, if he did, cynical as it may be, I would fully support him in that.)</p>
<p>&#8212; Donald</p>
]]></content:encoded>
	</item>
</channel>
</rss>
