<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://imechanica.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>iMechanica - I am sorry to inform You: a collection of famous papers rejected, including EINSTEIN!! - Comments</title>
 <link>http://imechanica.org/node/3353</link>
 <description>Comments for &quot;I am sorry to inform You: a collection of famous papers rejected, including EINSTEIN!!&quot;</description>
 <language>en</language>
<item>
 <title>Einstein had a good performance in Science in 1905, but poor ..</title>
 <link>http://imechanica.org/node/3353#comment-7789</link>
 <description>&lt;p&gt;1905 was an excellent year for Einstein, 3 magic papers, see &lt;font size=&quot;3&quot;&gt;http://sb3.epfl.ch/gm-perso.data/Einstein100.ppt&lt;/font&gt; &lt;/p&gt;
&lt;p&gt;
&lt;font size=&quot;4&quot;&gt;But was very poor for his boss at patent office!&amp;nbsp; Very funny.... read this:&lt;br /&gt;
&lt;/font&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;font size=&quot;5&quot;&gt;&amp;#39;05 Annual Performance Review: Albert Einstein&lt;/font&gt;
&lt;/p&gt;
&lt;p&gt;			Employee&amp;#39;s Name: &lt;strong&gt;Albert Einstein&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;			Supervisor&amp;#39;s name: &lt;strong&gt;Dr. Friedrich Haller&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;			Title: &lt;strong&gt;Patent Clerk Third Class&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;			Location: &lt;strong&gt;Bern Patent Office&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;			Year: &lt;strong&gt;&amp;#39;05&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;			Overall Rating:&lt;br /&gt;
			Poor&lt;br /&gt;
			Excellent &lt;/p&gt;
&lt;p&gt;
&lt;em&gt;Instructions:  Please complete each part of each question and discuss with the employee during the performance review meeting.  &lt;/em&gt;
&lt;/p&gt;
&lt;p&gt;PART 1: JOB DEFINITION&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Describe the employee&amp;#39;s duties and responsibilities and indicate the relative priorities of key elements.
&lt;p&gt;
	&lt;strong&gt;This is a patent office, Albert.  Your job is to transform written&lt;br /&gt;
	patent applications into clear and precise language, and to  study&lt;br /&gt;
	applications and pick out the new ideas of an invention.  These are&lt;br /&gt;
	the priorities. Where does it say that your priorities are&lt;br /&gt;
	rewriting the rules of the&lt;br /&gt;
	Universe, unifying space and time, unifying radiation and matter,&lt;br /&gt;
	or demonstrating the existence of atoms?&lt;/strong&gt;
	&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;
	&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;Describe any&lt;br /&gt;
	changes that have occurred in the employee&amp;#39;s job since his or her last&lt;br /&gt;
	performance discussion.&lt;/p&gt;
&lt;p&gt;
	&lt;strong&gt;None.&lt;/strong&gt;
	&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;PART II: PERFORMANCE FACTORS&lt;/p&gt;
&lt;p&gt;			&amp;nbsp;&lt;br /&gt;
			Poor ... Excellent&lt;/p&gt;
&lt;p&gt;			1.&lt;/p&gt;
&lt;p&gt;			Works well with others&lt;/p&gt;
&lt;p&gt;			2.&lt;/p&gt;
&lt;p&gt;			Is willing worker in assigned responsibilities&lt;/p&gt;
&lt;p&gt;			3.&lt;/p&gt;
&lt;p&gt;			Demonstrates skill and proficiency in carrying out assignments&lt;/p&gt;
&lt;p&gt;			4.&lt;/p&gt;
&lt;p&gt;			Strives to improve work methods as a means toward greater efficiency&lt;/p&gt;
&lt;p&gt;			5.&lt;/p&gt;
&lt;p&gt;			Is willing to take on additional responsibilities&lt;/p&gt;
&lt;p&gt;			6.&lt;/p&gt;
&lt;p&gt;			Makes sound and timely decisions - analyzes facts and reaches logical conclusions&lt;/p&gt;
&lt;p&gt;			7.&lt;/p&gt;
&lt;p&gt;			Is a reliable employee (attendance, punctuality, consistent work)&lt;/p&gt;
&lt;p&gt;			8.&lt;/p&gt;
&lt;p&gt;			Shares credit appropriately&lt;br /&gt;
			&lt;/p&gt;
&lt;p&gt;PART III: PERFORMANCE SUMMARY&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;	List aspects of the employee&amp;#39;s approach that contribute to his or her effectiveness.
&lt;p&gt;
	&lt;strong&gt;Albert does a good job of processing patent applications.  He seems&lt;br /&gt;
	to enjoy his work and have a competence for it. I put him down for &amp;quot;excellent&amp;quot; at&lt;br /&gt;
	&amp;quot;analyzes facts and reaches logical conclusions&amp;quot; -- no problem there, we can all agree.&lt;br /&gt;
	&lt;/strong&gt;
	&lt;/p&gt;
&lt;p&gt;
	&lt;strong&gt;However this year he seems&lt;br /&gt;
	to have devoted much of his time to publishing a series of outside papers.&lt;br /&gt;
	While this is not the primary responsibility of his position,&lt;br /&gt;
	I have to say he has done reasonably well in this respect:&lt;br /&gt;
	&lt;/strong&gt;
	&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;
	&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;In March,  &lt;a href=&quot;http://lorentz.phl.jhu.edu/AnnusMirabilis/AeReserveArticles/eins_lq.pdf&quot;&gt;&lt;em&gt;On a heuristic viewpoint concerning the production and transformation of light&lt;/em&gt;&lt;/a&gt;, contradicted the&lt;br /&gt;
		well-established wave theory of light, replacing it with a quantum light theory, based&lt;br /&gt;
		on evidence from the photoelectric effect and other prior experiments.  You called&lt;br /&gt;
		this paper &amp;quot;revolutionary,&amp;quot; and many physicists agreed, although some resisted your&lt;br /&gt;
		conclusions.&lt;br /&gt;
		&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;In April, your PhD dissertation &lt;a href=&quot;http://lorentz.phl.jhu.edu/AnnusMirabilis/AeReserveArticles/eins_diss.pdf&quot;&gt;&lt;em&gt;A New Determination of Molecular Dimensions&lt;/em&gt;&lt;/a&gt;&lt;br /&gt;
		measured the size of atoms (and also Avogadro&amp;#39;s number), making the&lt;br /&gt;
		theory of atoms more concrete, particularly the kinetic theory of heat,&lt;br /&gt;
		based on an analysis of data&lt;br /&gt;
		about solutions of sugar in water. While atoms had been proposed 2500&lt;br /&gt;
		years ago and were widely believed in, you helped provide evidence for&lt;br /&gt;
		them.&lt;br /&gt;
		&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;In May, &lt;a href=&quot;http://lorentz.phl.jhu.edu/AnnusMirabilis/AeReserveArticles/eins_brownian.pdf&quot;&gt;&lt;em&gt;On the motion of small particles suspended in liquids at rest required by the molecular-kinetic theory of heat&lt;/em&gt;&lt;/a&gt;&lt;br /&gt;
		further demonstrates&lt;br /&gt;
		the existence of atoms, explains Brownian motion, and shows that the&lt;br /&gt;
		second law of thermodynamics is just a statistical summary, not an&lt;br /&gt;
		absolute law.&lt;br /&gt;
		&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;In June, &lt;a href=&quot;http://www.fourmilab.ch/etexts/einstein/specrel/www/&quot;&gt;&lt;em&gt;On the electrodynamics of moving bodies&lt;/em&gt;&lt;/a&gt;&lt;br /&gt;
		introduces what&lt;br /&gt;
		you call the special theory of relativity that shows that there is no&lt;br /&gt;
		distinguished&lt;br /&gt;
		state of rest in the Universe, and no one distinguished notion of time;&lt;br /&gt;
		rather that time and motion are relative to the observer.&lt;br /&gt;
		&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;In September, &lt;a href=&quot;http://www.fourmilab.ch/etexts/einstein/E_mc2/e_mc2.pdf&quot;&gt;&lt;em&gt;Does the inertia of a body depend on its energy content?&lt;/em&gt;&lt;/a&gt; follows up on the June paper and shows that radiation converts mass to energy according to the formula &lt;em&gt;E = mc2&lt;/em&gt;.&lt;br /&gt;
		&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;
	&amp;nbsp;
	&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;	List aspects of employee&amp;#39;s approach which require improvement for greater effectiveness.
&lt;p&gt;
	&lt;strong&gt;Regrettably, I had to put you down as &amp;quot;poor&amp;quot; for &amp;quot;works well with&lt;br /&gt;
	others&amp;quot;&lt;br /&gt;
	and &amp;quot;shares credit appropriately.&amp;quot; You had no co-authors on your five&lt;br /&gt;
	papers,&lt;br /&gt;
	and your citations were quite skimpy: no citations at all in your June&lt;br /&gt;
	and September paper,&lt;br /&gt;
	only one citation in your April paper, and not much better on the&lt;br /&gt;
	others. You wrote&lt;br /&gt;
	that your special theory of relativity came to you after a discussion&lt;br /&gt;
	with your friend Michele Besso. But you didn&amp;#39;t even acknowledge him in&lt;br /&gt;
	your June paper. This&lt;br /&gt;
	is an area for improvement.&lt;br /&gt;
	&lt;/strong&gt;
	&lt;/p&gt;
&lt;p&gt;
	&lt;strong&gt;On the other hand, famous physicists are beginning to visit the offices here in Bern;&lt;br /&gt;
	Albert you must make sure that any hours spent in talking to them are subtracted&lt;br /&gt;
	from your time card and made up for later.  You are responsible for making&lt;br /&gt;
	sure these visits do not cause a distraction for others in the office.&lt;br /&gt;
	&lt;/strong&gt;
	&lt;/p&gt;
&lt;p&gt;
	&lt;strong&gt;In addition, I would have to say your output, while at times quite&lt;br /&gt;
	extraordinary, has been inconsistent. In Q1 you managed to publish one&lt;br /&gt;
	paper&lt;br /&gt;
	in the final two weeks of the quarter. In Q2 you improved productivity,&lt;br /&gt;
	with your dissertation in April, the Brownian Motion paper in May, and&lt;br /&gt;
	the Special Relativity paper in June. Not bad for a quarter, not bad at&lt;br /&gt;
	all.&lt;br /&gt;
	But then you seemed to slump: you did finish one paper 3 days before&lt;br /&gt;
	the close of Q3, but it was only 3 pages long. I admit that some&lt;br /&gt;
	reviewers&lt;br /&gt;
	did find it noteworthy, but really, couldn&amp;#39;t it have been the&lt;br /&gt;
	conclusion of your June paper? It almost seems like you held it back&lt;br /&gt;
	just to have something to show for Q3. (This flippant, almost&lt;br /&gt;
	disrespectful attitude is also&lt;br /&gt;
	evident in your dissertation: when told by your respected thesis&lt;br /&gt;
	committee that your thesis&lt;br /&gt;
	was too short, you added one sentence.) And then in Q4 -- no&lt;br /&gt;
	publications at all.&lt;br /&gt;
	&lt;/strong&gt;
	&lt;/p&gt;
&lt;p&gt;
	&lt;strong&gt;You wrote that &amp;quot;A storm broke out in my mind&amp;quot; this year.  Let me remind you&lt;br /&gt;
	that our Employee Assistance Plan (EAP) covers up to three psychiatric treatments,&lt;br /&gt;
	should you find them necessary.&lt;br /&gt;
	&lt;/strong&gt;
	&lt;/p&gt;
&lt;p&gt;
	&lt;strong&gt;You seem to lack a flare for self-promotion. Lucky for us our PR department&lt;br /&gt;
	stepped in and changed your &lt;em&gt;L/c2&lt;/em&gt; equation into the much&lt;br /&gt;
	more marketable &lt;em&gt;E = mc2&lt;/em&gt;.  &lt;/strong&gt;
	&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;	Is the employee ready for increased responsibility?  If yes, please explain.
&lt;p&gt;
	&lt;strong&gt;Based on his performance as a patent clerk, I cannot recommend Albert for a promotion&lt;br /&gt;
	at this time.&lt;/strong&gt;
	&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;
	&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;	Does the employee require additional training? If yes, please explain.
&lt;p&gt;
	&lt;strong&gt;First, congratulations for completing your &lt;a href=&quot;http://lorentz.phl.jhu.edu/AnnusMirabilis/AeReserveArticles/eins_diss.pdf&quot;&gt;doctoral dissertation&lt;/a&gt;&lt;br /&gt;
	in April. (Make sure you fill out form EDUR-4 to be reimbursed for a&lt;br /&gt;
	portion of your tuition.) I was impressed that Prof. Alfred Kleiner&lt;br /&gt;
	wrote that &amp;quot;Herr Einstein has provided evidence that he is capable of&lt;br /&gt;
	occupying himself successfully with scientific problems.&amp;quot; So clearly,&lt;br /&gt;
	you need no more&lt;br /&gt;
	formal education.&lt;br /&gt;
	&lt;/strong&gt;
	&lt;/p&gt;
&lt;p&gt;
	&lt;strong&gt;However, based on your file photo below, I would suggest you sign up for&lt;br /&gt;
	the &amp;quot;Dress for Success&amp;quot; class.  Really: a striped shirt with a plaid suit?&lt;/strong&gt;
	&lt;/p&gt;
&lt;p&gt;
	&lt;img src=&quot;http://www.th.physik.uni-frankfurt.de/%7Ejr/gif/phys/einst_pat.jpg&quot; alt=&quot;&quot; /&gt;
	&lt;/p&gt;
&lt;p&gt;
	&amp;nbsp;
	&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Further Reading&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;http://www.amazon.com/exec/obidos/tg/detail/-/0674015444/&quot;&gt;Einstein 1905: The Standard of Greatness&lt;/a&gt; (book by John S. Rigden)
	&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;http://lorentz.phl.jhu.edu/AnnusMirabilis/&quot;&gt;EINSTEIN&amp;#39;S ANNUS MIRABILIS 1905: HOME PAGE&lt;/a&gt; (for Johns Hopkins Univ. course 150.435)
	&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;http://www.pitt.edu/%7Ejdnorton/teaching/2509_Einstein_1905.html&quot;&gt;Einstein 1905&lt;/a&gt; (for Univ. of Pittsburgh course HPS 2590)
	&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;http://www.google.com/search?client=safari&amp;amp;rls=en&amp;amp;q=einstein+1905&amp;amp;ie=UTF-8&amp;amp;oe=UTF-8&quot;&gt;[einstein 1905]&lt;/a&gt; (web search)
	&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href=&quot;http://norvig.com/&quot;&gt;Peter Norvig&lt;/a&gt;&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;</description>
 <pubDate>Mon, 16 Jun 2008 09:22:15 -0400</pubDate>
 <dc:creator>Mike Ciavarella</dc:creator>
 <guid isPermaLink="false">comment 7789 at http://imechanica.org</guid>
</item>
<item>
 <title>I am sorry to inform You: a collection of famous papers rejected, including EINSTEIN!!</title>
 <link>http://imechanica.org/node/3353</link>
 <description>&lt;p&gt;&lt;font size=&quot;5&quot;&gt;We Are Sorry to Inform You&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;December 2005&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;			&lt;img src=&quot;http://www.computer.org/portal/cms_docs_cise/cise/images/send_print/send_icon.gif&quot; border=&quot;0&quot; alt=&quot;Send Link&quot; width=&quot;26&quot; height=&quot;23&quot; align=&quot;absmiddle&quot; /&gt;&lt;a href=&quot;void(send_email_popup(escape(&amp;#039;We+Are+Sorry+to+Inform+You&amp;#039;),&amp;#039;computer/homepage/1205&amp;#039;,&amp;#039;profession.xml&amp;#039;,&amp;#039;1015&amp;#039;,&amp;#039;2005-12-01&amp;#039;));&quot;&gt;Send Link&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;			&lt;img src=&quot;http://www.computer.org/portal/cms_docs_cise/cise/images/send_print/print_icon.gif&quot; border=&quot;0&quot; alt=&quot;Printer Friendly&quot; width=&quot;26&quot; height=&quot;23&quot; align=&quot;absmiddle&quot; /&gt;&lt;a href=&quot;void(PrintOnly2(&amp;#039;computer/homepage/1205&amp;#039;,&amp;#039;profession.xml&amp;#039;,&amp;#039;1015&amp;#039;));&quot;&gt;Printer Friendly&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.computer.org/portal/site/computer/index.jsp?pageID=computer_level1_article_list&amp;amp;TheCat=1015&quot;&gt;The Profession&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;We Are Sorry to Inform You&lt;/p&gt;
&lt;p&gt;Simone Santini, University of California, San Diego&lt;/p&gt;
&lt;p&gt;
&lt;span class=&quot;deptdropcap&quot;&gt;O&lt;/span&gt;nce upon a time there was a little-known&lt;br /&gt;
patent clerk in Bern who received a disappointing annual performance review in&lt;br /&gt;
&amp;#39;05 (&lt;a href=&quot;http://www.norvig.com/performance-review.html&quot;&gt;www.norvig.com/performance-review.html&lt;/a&gt;).
&lt;/p&gt;
&lt;p&gt;E.W. DIJKSTRA&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;&amp;quot;Goto Statement Considered Harmful.&amp;quot;&lt;/strong&gt; This paper tries to&lt;br /&gt;
convince us that the well-known goto statement should be eliminated from our&lt;br /&gt;
programming languages or, at least (since I don&amp;#39;t think that it will ever be&lt;br /&gt;
eliminated), that programmers should not use it. It is not clear what should&lt;br /&gt;
replace it. The paper doesn&amp;#39;t explain to us what would be the use of the&lt;br /&gt;
&amp;quot;if&amp;quot; statement without a &amp;quot;goto&amp;quot; to redirect the flow of&lt;br /&gt;
execution: Should all our postconditions consist of a single statement, or&lt;br /&gt;
should we only use the arithmetic &amp;quot;if,&amp;quot; which doesn&amp;#39;t contain the&lt;br /&gt;
offensive &amp;quot;goto&amp;quot;?&lt;br /&gt;
And how will one deal with the case in which, having reached the end of an&lt;br /&gt;
alternative, the program needs to continue the execution somewhere else?&lt;br /&gt;
The author is a proponent of the so-called &amp;quot;structured programming&amp;quot;&lt;br /&gt;
style, in which, if I get it right, gotos are replaced by indentation.&lt;br /&gt;
Structured programming is a nice academic exercise, which works well for small&lt;br /&gt;
examples, but I doubt that any real-world program will ever be written in such&lt;br /&gt;
a style. More than 10 years of industrial experience with Fortran have proved&lt;br /&gt;
conclusively to everybody concerned that, in the real world, the goto is useful&lt;br /&gt;
and necessary: its presence might cause some inconveniences in debugging, but&lt;br /&gt;
it is a de facto standard and we must live with it. It will take more than the&lt;br /&gt;
academic elucubrations of a purist to remove it from our languages.&lt;br /&gt;
Publishing this would waste valuable paper: Should it be published, I am as&lt;br /&gt;
sure it will go uncited and unnoticed as I am confident that, 30 years from&lt;br /&gt;
now, the goto will still be alive and well and used as widely as it is&lt;br /&gt;
today.&lt;br /&gt;
Confidential comments to the editor: The author should withdraw the paper and&lt;br /&gt;
submit it someplace where it will not be peer reviewed. A letter to the editor&lt;br /&gt;
would be a perfect choice: Nobody will notice it there!
&lt;/p&gt;
&lt;p&gt;E.F. CODD&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;&amp;quot;A Relational Model of Data for Large Shared Data Banks.&amp;quot;&lt;/strong&gt;&lt;br /&gt;
This paper proposes that all data in a database be represented in the form of&lt;br /&gt;
relations&amp;mdash;sets of tuples&amp;mdash;and that all the operations relative to&lt;br /&gt;
data access be made on this model. Some of the ideas presented in the paper are&lt;br /&gt;
interesting and may be of some use, but, in general, this very preliminary work&lt;br /&gt;
fails to make a convincing point as to their implementation, performance, and&lt;br /&gt;
practical usefulness. The paper?s general point is that the tabular form&lt;br /&gt;
presented should be suitable for general data access, but I see two problems&lt;br /&gt;
with this statement: expressivity and efficiency.&lt;br /&gt;
The paper contains no real-world example to convince us that any model of&lt;br /&gt;
practical interest can be cast in it. Quite the contrary, at first sight I&lt;br /&gt;
doubt that anything complex enough to be of practical interest can be modeled&lt;br /&gt;
using relations. The simplicity of the model prevents one from, for instance,&lt;br /&gt;
representing hierarchies directly and forces their replacement with complicated&lt;br /&gt;
systems of &amp;quot;foreign keys.&amp;quot; In this situation, any realistic model might&lt;br /&gt;
end up requiring dozens of interconnected tables&amp;mdash;hardly a practical&lt;br /&gt;
solution given that, probably, we can represent the same model using two or&lt;br /&gt;
three properly formatted files.&lt;br /&gt;
Even worse, the paper contains no efficiency evaluation: There are no&lt;br /&gt;
experiments with real or synthetic data to show how the proposed approach&lt;br /&gt;
compares with traditional ones on real-world problems. The main reason for&lt;br /&gt;
using specialized file formats is efficiency: Data can be laid out in such a&lt;br /&gt;
way that the common access patterns are efficient. This paper proposes a model&lt;br /&gt;
in which, to extract any significant answer from any real database, the user&lt;br /&gt;
will end up with the very inefficient solution of doing a large number of&lt;br /&gt;
joins. Yet we are given no experimental result or indication of how this&lt;br /&gt;
solution might scale up.&lt;br /&gt;
The formalism is needlessly complex and mathematical, using concepts and&lt;br /&gt;
notation with which the average data bank practitioner is unfamiliar. The paper&lt;br /&gt;
doesn&amp;#39;t tell us how to translate its arcane operations into executable block&lt;br /&gt;
access.&lt;br /&gt;
Adding together the lack of any real-world example, performance experiment, and&lt;br /&gt;
implementation indication or detail, we are left with an obscure exercise using&lt;br /&gt;
unfamiliar mathematics and of little or no practical consequence. It can be&lt;br /&gt;
safely rejected.
&lt;/p&gt;
&lt;p&gt;A. TURING&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;&amp;quot;On Computable Numbers, with an Application to the Entscheidungs&lt;br /&gt;
Problem.&amp;quot;&lt;/strong&gt; This is a bizarre paper. It begins by defining a computing&lt;br /&gt;
device absolutely unlike anything I have seen, then proceeds to show&amp;mdash;I&lt;br /&gt;
haven&amp;#39;t quite followed the needlessly complicated formalism&amp;mdash;that there&lt;br /&gt;
are numbers that it can&amp;#39;t compute. As I see it, there are two alternatives that&lt;br /&gt;
apply to any machine that will ever be built: Either these numbers are too big&lt;br /&gt;
to be represented in the machine, in which case the conclusion is obvious, or&lt;br /&gt;
they are not; in that case, a machine that can&amp;#39;t compute them is simply&lt;br /&gt;
broken!&lt;br /&gt;
Any tabulating machine worth its rent can compute all the values in the range&lt;br /&gt;
it represents, and any number computable by a function&amp;mdash;that is, by&lt;br /&gt;
applying the four operations a number of times&amp;mdash;can be computed by any&lt;br /&gt;
modern tabulating machine since these machines&amp;mdash;unlike the one proposed&lt;br /&gt;
here with its bizarre mechanism&amp;mdash;&amp;mdash;have the four operations&lt;br /&gt;
hardwired. It seems that the &amp;quot;improvement&amp;quot; proposed by Turing is not an&lt;br /&gt;
improvement over current technology at all, and I strongly suspect the machine&lt;br /&gt;
is too simple to be of any use.&lt;br /&gt;
If the article is accepted, Turing should remember that the language of this&lt;br /&gt;
journal is English and change the title accordingly.
&lt;/p&gt;
&lt;p&gt;C.E. SHANNON&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;&amp;quot;A Mathematical Theory of Communication.&amp;quot;&lt;/strong&gt; This paper is&lt;br /&gt;
poorly motivated and excessively abstract. It is unclear for what practical&lt;br /&gt;
problem it might be relevant. The author claims that &amp;quot;semantic aspects of&lt;br /&gt;
communication are irrelevant to the engineering problems,&amp;quot; which seems to&lt;br /&gt;
indicate that his theory is suitable mostly for transmitting gibberish. Alas,&lt;br /&gt;
people will not pay to have gibberish transmitted anywhere.&lt;br /&gt;
I don&amp;#39;t understand the relevance of discrete sources: No matter what one does,&lt;br /&gt;
in the end, the signal will have to be modulated using good old-fashioned&lt;br /&gt;
vacuum tubes, so the signal on the &amp;quot;&amp;#39;channel&amp;quot;&amp;#39; will always be&lt;br /&gt;
analogical.&lt;br /&gt;
A running example would have helped make the presentation clearer and less&lt;br /&gt;
theoretical, but none is provided. Also, the author presents no implementation&lt;br /&gt;
details or experiments taken from a practical application.&lt;br /&gt;
Confidential comments to the editor: The only thing absolutely wrong with this&lt;br /&gt;
paper is that it doesn&amp;#39;t quite &amp;quot;resonate&amp;quot; with what the research&lt;br /&gt;
community finds exciting. At any point, there are sexy topics and unsexy ones:&lt;br /&gt;
these days, television is sexy and color television is even sexier. Discrete&lt;br /&gt;
channels with a finite number of symbols are good for telegraphy, but&lt;br /&gt;
telegraphy is 100 years old, hardly a good research topic.&lt;br /&gt;
The author mentions computing machines, such as the recent ENIAC. Well, I guess&lt;br /&gt;
one could connect such machines, but a recent IBM memo stated that a dozen or&lt;br /&gt;
so such machines will be sufficient for all the computing that we&amp;#39;ll ever need&lt;br /&gt;
in the foreseeable future, so there won&amp;#39;t be a whole lot of connecting going on&lt;br /&gt;
with only a dozen ENIACs!&lt;br /&gt;
IBM has decided to stay out of the electronic computing business, and this&lt;br /&gt;
journal should probably do the same!
&lt;/p&gt;
&lt;p&gt;C.A.R. HOARE&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;&amp;quot;An Axiomatic Basis for Computer Programming.&amp;quot;&lt;/strong&gt; I am not sure&lt;br /&gt;
I understand this article. It claims to be about programming, but it doesn&amp;#39;t&lt;br /&gt;
contain a single line of code.&lt;br /&gt;
The paper introduces the idea that certain inference rules can be associated to&lt;br /&gt;
statements in a program and used to show that the program does indeed compute&lt;br /&gt;
what it is supposed to. I have some reservations that the program&amp;#39;s purpose can&lt;br /&gt;
be defined in the terms the author claims&amp;mdash;we all know how fuzzily defined&lt;br /&gt;
the features of real programs are&amp;mdash;but the idea, if suitably justified,&lt;br /&gt;
might have some merit. However, in its current state, the work is far too&lt;br /&gt;
preliminary to be considered for a journal. It may well be insufficient for any&lt;br /&gt;
kind of publication, so I would advise the author to try a workshop at which&lt;br /&gt;
these kinds of preliminary ideas will be more likely to find a home.&lt;br /&gt;
Before the author attempts journal publication, he should complete this work in&lt;br /&gt;
several respects. The method assumes that the function of a program can be&lt;br /&gt;
specified as the final value of certain variables. This is an unrealistic view&lt;br /&gt;
for interactive programs: The author should show how his method fits with the&lt;br /&gt;
industry&amp;#39;s standard way of specifying requirements. He should also extend the&lt;br /&gt;
method to be applicable to a standard programming language such as COBOL or&lt;br /&gt;
PL/I and provide the details of his implementation, possibly with a few&lt;br /&gt;
graphics to show how the system works in practice.&lt;br /&gt;
Until this is done, I fear the work is too tentative and preliminary for&lt;br /&gt;
publication.
&lt;/p&gt;
&lt;p&gt;R.L. RIVEST, A. SHAMIR, AND L. ADELMAN&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;&amp;quot;A Method for Obtaining Digital Signatures and Public-Key&lt;br /&gt;
Cryptosystems.&amp;quot;&lt;/strong&gt; According to the (very short) introduction, this paper&lt;br /&gt;
purports to present a practical implementation of Diffie and Hellman&amp;#39;s&lt;br /&gt;
public-key cryptosystem for applications in the electronic mail realm. If this&lt;br /&gt;
is indeed the premise, the paper should be rejected both for a failure to live&lt;br /&gt;
up to it and for its irrelevance.&lt;br /&gt;
I doubt that a system such as this one will ever be practical. The paper does a&lt;br /&gt;
poor job of convincing the reader that practicality is attainable. For one&lt;br /&gt;
thing, there is the issue of the number n used to factor the message.&lt;br /&gt;
The scheme&amp;#39;s security relies on the factorization of n in prime factors taking&lt;br /&gt;
so long as to be impractical. The authors also stress that the encryption&lt;br /&gt;
algorithm must be fast and&amp;mdash;if their application, electronic mail, is to&lt;br /&gt;
make sense&amp;mdash;the algorithm should run on all sorts of machines. Let us be&lt;br /&gt;
generous and assume that every computer user has access to a latest-generation&lt;br /&gt;
minicomputer such as the VAX. This 32-bit machine&amp;#39;s speed considerations limit&lt;br /&gt;
the choice of n to n &amp;lt; 232 = 4,294,967,296. Granted, this is a large&lt;br /&gt;
number, but by the very results of the paper&amp;#39;s Table 1, it can be factored in a&lt;br /&gt;
couple of hours. Scarcely a time margin that will grant security!
&lt;/p&gt;
&lt;p&gt;
Further, as the authors acknowledge, a data encryption standard already&lt;br /&gt;
exists, supported by both the US National Bureau of Standards and IBM,&lt;br /&gt;
currently the largest computer manufacturer. It is unlikely that any method&lt;br /&gt;
that runs counter to this standard will be adopted in any significant degree.&lt;br /&gt;
True, the IBM method presents the problem of distributing the encryption key,&lt;br /&gt;
but their method is a standard and we must live with it. Instead of creating&lt;br /&gt;
nonstandard methods that will soon be dead for lack of users, the authors&lt;br /&gt;
should try to extend the standard and devise ways to distribute the encryption&lt;br /&gt;
keys securely.&lt;br /&gt;
Finally, there is the question of the application. Electronic mail on the&lt;br /&gt;
Arpanet is indeed a nice gizmo, but it is unlikely it will ever be diffused&lt;br /&gt;
outside academic circles and public laboratories&amp;mdash;environments in which&lt;br /&gt;
the need to maintain confidentiality is scarcely pressing. Laboratories with&lt;br /&gt;
military contracts will never communicate through the Arpanet! Either normal&lt;br /&gt;
people or small companies will be able to afford a VAX each, or the market for&lt;br /&gt;
electronic mail will remain tiny. Granted, we are seeing the appearance of&lt;br /&gt;
so-called microcomputers, such as the recently announced Apple II, but their&lt;br /&gt;
limitations are so great that neither they nor their descendants will have the&lt;br /&gt;
power necessary to communicate through a network.&lt;br /&gt;
The introduction is only two paragraphs long, the relevant literature is not&lt;br /&gt;
presented or cited, and there is virtually no comparison with the relevant work&lt;br /&gt;
in the area. In summary, it looks as if this paper is a mathematical exercise&lt;br /&gt;
with little originality (the authors claim that most of their ideas come from&lt;br /&gt;
other papers), too far from practical applicability, running against the&lt;br /&gt;
established standards, and with a declared application area of dubious&lt;br /&gt;
feasibility. Not the kind of material our readers like to see in the journal.&lt;br /&gt;
Reject.&lt;br /&gt;
And the rest is history.
&lt;/p&gt;
&lt;p&gt;
Simone Santini is a project researcher at the University of California, San&lt;br /&gt;
Diego. Contact him at &lt;a href=&quot;mailto:ssantini@sdsc.edu&quot;&gt;ssantini@sdsc.edu.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;http://www.computer.org/portal/cms_docs_computer/computer/images/spacer.gif&quot; border=&quot;0&quot; alt=&quot; &quot; width=&quot;490&quot; height=&quot;1&quot; /&gt;&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;</description>
 <comments>http://imechanica.org/node/3353#comments</comments>
 <category domain="http://imechanica.org/taxonomy/term/76">research</category>
 <category domain="http://imechanica.org/taxonomy/term/2465">rejections</category>
 <category domain="http://imechanica.org/taxonomy/term/2388">review process</category>
 <category domain="http://imechanica.org/taxonomy/term/2466">reviewers lower than authors</category>
 <category domain="http://imechanica.org/taxonomy/term/2467">unprofessional reviewers</category>
 <pubDate>Mon, 16 Jun 2008 09:10:57 -0400</pubDate>
 <dc:creator>Mike Ciavarella</dc:creator>
 <guid isPermaLink="false">3353 at http://imechanica.org</guid>
</item>
</channel>
</rss>
