<?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: How (not) to write an abstract</title>
	<atom:link href="http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/</link>
	<description>Security Research, Computer Laboratory, University of Cambridge</description>
	<lastBuildDate>Sat, 28 Jan 2012 18:43:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: yishuai</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/comment-page-1/#comment-22054</link>
		<dc:creator>yishuai</dc:creator>
		<pubDate>Fri, 18 May 2007 08:50:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/#comment-22054</guid>
		<description>Dear Mr. Markus:

I am so impressed with your advise that I can not resist translating its main content to Chinese and sharing it with my friends in my blog. The original link of your post is refered in my post. Please allow me do it. Thanks!

Sincerely
Yishuai</description>
		<content:encoded><![CDATA[<p>Dear Mr. Markus:</p>
<p>I am so impressed with your advise that I can not resist translating its main content to Chinese and sharing it with my friends in my blog. The original link of your post is refered in my post. Please allow me do it. Thanks!</p>
<p>Sincerely<br />
Yishuai</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quinn DuPont</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/comment-page-1/#comment-21151</link>
		<dc:creator>Quinn DuPont</dc:creator>
		<pubDate>Wed, 28 Mar 2007 05:40:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/#comment-21151</guid>
		<description>There is a reason why they are called &quot;computer science&quot; students, and not &quot;humanities&quot; or &quot;arts&quot; students.  Seriously though, at the undergraduate level there is exactly one desideratum for humanities students: the ability to clearly articulate an argument.  No such similar emphasis exists for the sciences, much less the engineering/IT sciences.

Your suggestions for an abstract are exactly right.  It does no good to try to pressure a publisher into offering full-text for indexing, since that would defeat the purpose of a well-written abstract.  The abstract SHOULD include all the keywords, and SHOULD give a clear distillation of the emphasis of the paper, so a potential reader can assess the likelihood of substantial value arising from reading the full text.</description>
		<content:encoded><![CDATA[<p>There is a reason why they are called &#8220;computer science&#8221; students, and not &#8220;humanities&#8221; or &#8220;arts&#8221; students.  Seriously though, at the undergraduate level there is exactly one desideratum for humanities students: the ability to clearly articulate an argument.  No such similar emphasis exists for the sciences, much less the engineering/IT sciences.</p>
<p>Your suggestions for an abstract are exactly right.  It does no good to try to pressure a publisher into offering full-text for indexing, since that would defeat the purpose of a well-written abstract.  The abstract SHOULD include all the keywords, and SHOULD give a clear distillation of the emphasis of the paper, so a potential reader can assess the likelihood of substantial value arising from reading the full text.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Bond</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/comment-page-1/#comment-21132</link>
		<dc:creator>Mike Bond</dc:creator>
		<pubDate>Mon, 26 Mar 2007 13:03:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/#comment-21132</guid>
		<description>Peter Lewis writes:

&lt;i&gt;But I agree with Markus: it’s annoying when you come across an abstract that reads more like the back of a novel: `will we ever find out whose FuzzyClass classifier was trained by the resulting output?!’&lt;/i&gt;

This is an interesting comparison. The back covers of books contain just a few sentences very carefully crafted to catch the browser&#039;s attention and get them to read the book.

It is very telling that some (or indeed many) academics appear not to want this advertising service from an Abstract. But yet we all want our papers to be read and noticed, don&#039;t we?

Maybe one day papers might have two brief paragraphs on the front? An &quot;advert&quot; and a &quot;synopsis&quot;.

Mike.</description>
		<content:encoded><![CDATA[<p>Peter Lewis writes:</p>
<p><i>But I agree with Markus: it’s annoying when you come across an abstract that reads more like the back of a novel: `will we ever find out whose FuzzyClass classifier was trained by the resulting output?!’</i></p>
<p>This is an interesting comparison. The back covers of books contain just a few sentences very carefully crafted to catch the browser&#8217;s attention and get them to read the book.</p>
<p>It is very telling that some (or indeed many) academics appear not to want this advertising service from an Abstract. But yet we all want our papers to be read and noticed, don&#8217;t we?</p>
<p>Maybe one day papers might have two brief paragraphs on the front? An &#8220;advert&#8221; and a &#8220;synopsis&#8221;.</p>
<p>Mike.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stone Rice Big dot Net :: How to sell your papers :: March :: 2007</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/comment-page-1/#comment-20774</link>
		<dc:creator>Stone Rice Big dot Net :: How to sell your papers :: March :: 2007</dc:creator>
		<pubDate>Thu, 22 Mar 2007 16:55:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/#comment-20774</guid>
		<description>[...] of difficulties in writing a good abstract. Markus Kuhn from lightbluetouchpaper gives some useful advice on writing an [...]</description>
		<content:encoded><![CDATA[<p>[...] of difficulties in writing a good abstract. Markus Kuhn from lightbluetouchpaper gives some useful advice on writing an [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrei Serjantov</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/comment-page-1/#comment-19514</link>
		<dc:creator>Andrei Serjantov</dc:creator>
		<pubDate>Sun, 18 Mar 2007 22:48:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/#comment-19514</guid>
		<description>A good presentation on how to write a research paper from Simon Peyton-Jones

http://research.microsoft.com/~simonpj/papers/giving-a-talk/writing-a-paper-slides.pdf</description>
		<content:encoded><![CDATA[<p>A good presentation on how to write a research paper from Simon Peyton-Jones</p>
<p><a href="http://research.microsoft.com/~simonpj/papers/giving-a-talk/writing-a-paper-slides.pdf" rel="nofollow">http://research.microsoft.com/~simonpj/papers/giving-a-talk/writing-a-paper-slides.pdf</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Lewis</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/comment-page-1/#comment-18635</link>
		<dc:creator>Peter Lewis</dc:creator>
		<pubDate>Thu, 15 Mar 2007 11:52:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/#comment-18635</guid>
		<description>If ‘young researchers’ and other people interested in finding good sources quickly are spending some time looking through online abstract services, then surely they&#039;ll get a good idea about how to write a good abstract quite quickly: a good abstract is one that follows the style of those associated with the useful sources you found easily.

So if young researchers are making good use of abstract services, then they ought to have a good (if ostensive...) idea about what an abstract ought to contain.

But I agree with Markus: it’s annoying when you come across an abstract that reads more like the back of a novel: ‘will we ever find out whose FuzzyClass classifier was trained by the resulting output?!’</description>
		<content:encoded><![CDATA[<p>If ‘young researchers’ and other people interested in finding good sources quickly are spending some time looking through online abstract services, then surely they&#8217;ll get a good idea about how to write a good abstract quite quickly: a good abstract is one that follows the style of those associated with the useful sources you found easily.</p>
<p>So if young researchers are making good use of abstract services, then they ought to have a good (if ostensive&#8230;) idea about what an abstract ought to contain.</p>
<p>But I agree with Markus: it’s annoying when you come across an abstract that reads more like the back of a novel: ‘will we ever find out whose FuzzyClass classifier was trained by the resulting output?!’</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Domber&#8217;s Basecamp &#187; Blog Archive &#187; What&#8217;s the difference between an abstract and an introduction?</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/comment-page-1/#comment-18615</link>
		<dc:creator>Domber&#8217;s Basecamp &#187; Blog Archive &#187; What&#8217;s the difference between an abstract and an introduction?</dc:creator>
		<pubDate>Thu, 15 Mar 2007 01:10:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/#comment-18615</guid>
		<description>[...] but I have doubts about myself in writing &#8220;good&#8221; abstracts. Markus Kuhn from lightbluetouchpaper.org wrote a nice summary about do&#8217;s and dont&#8217;s concerning writing abstracts and [...]</description>
		<content:encoded><![CDATA[<p>[...] but I have doubts about myself in writing &#8220;good&#8221; abstracts. Markus Kuhn from lightbluetouchpaper.org wrote a nice summary about do&#8217;s and dont&#8217;s concerning writing abstracts and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clive Robinson</title>
		<link>http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/comment-page-1/#comment-18586</link>
		<dc:creator>Clive Robinson</dc:creator>
		<pubDate>Wed, 14 Mar 2007 13:12:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/03/14/how-not-to-write-an-abstract/#comment-18586</guid>
		<description>Writing any kind of paper is quite a difficult task in itself. Let alone writing the abstract, which is, as you say, the only part that becomes public for free (due to tradition and publishers).

As you note just about the only initial contact people will have with your paper is the abstract, often in form of a search result in a citation / abstract database on CD/DVD or online.

I used to work for the founding company in that game and I know from experience that the abstracts have many failings, not just the two you mentioned in your last paragraph.

Unfortunately citation / abstract databases are the way more and more young researchers are finding papers (often it&#039;s the way they are shown by their Uni Learning Resource Center). 

So the abstract is becoming critical not just to your paper but to your career and it should not be, which is unfortunately an issue that you can lay at the paper publisher&#039;s door. In general they only allow the abstract to become public and as they want to minimise their costs they place quite severe limits on its size.

To be really useful the abstract, introduction and optionally the conclusion need to be searched and seen by the researcher. In the past with paper publications held in the Uni library this was not too much of an issue as the abstract acted as just a &quot;taster&quot; or pointer, today however this is often not the case and a researcher or student has to use an online or CD service.

As paper writers you should be pushing the publishers to make the full text of the paper available to the citation / abstract database companies to provide full text searching. Also you need to push for more than just a 250 word abstract to be made available in the search results, but as a minimum a more length introduction and ideally part or all of the conclusion.

Otherwise you will have to change the old maxim &quot;publish or perish&quot; to something new as publishing alone just will not get you &quot;noticed and quoted&quot; any more.</description>
		<content:encoded><![CDATA[<p>Writing any kind of paper is quite a difficult task in itself. Let alone writing the abstract, which is, as you say, the only part that becomes public for free (due to tradition and publishers).</p>
<p>As you note just about the only initial contact people will have with your paper is the abstract, often in form of a search result in a citation / abstract database on CD/DVD or online.</p>
<p>I used to work for the founding company in that game and I know from experience that the abstracts have many failings, not just the two you mentioned in your last paragraph.</p>
<p>Unfortunately citation / abstract databases are the way more and more young researchers are finding papers (often it&#8217;s the way they are shown by their Uni Learning Resource Center). </p>
<p>So the abstract is becoming critical not just to your paper but to your career and it should not be, which is unfortunately an issue that you can lay at the paper publisher&#8217;s door. In general they only allow the abstract to become public and as they want to minimise their costs they place quite severe limits on its size.</p>
<p>To be really useful the abstract, introduction and optionally the conclusion need to be searched and seen by the researcher. In the past with paper publications held in the Uni library this was not too much of an issue as the abstract acted as just a &#8220;taster&#8221; or pointer, today however this is often not the case and a researcher or student has to use an online or CD service.</p>
<p>As paper writers you should be pushing the publishers to make the full text of the paper available to the citation / abstract database companies to provide full text searching. Also you need to push for more than just a 250 word abstract to be made available in the search results, but as a minimum a more length introduction and ideally part or all of the conclusion.</p>
<p>Otherwise you will have to change the old maxim &#8220;publish or perish&#8221; to something new as publishing alone just will not get you &#8220;noticed and quoted&#8221; any more.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

