<?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"
	>
<channel>
	<title>Comments on: Things to Avoid in a Scholarly Paper</title>
	<atom:link href="http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/feed/" rel="self" type="application/rss+xml" />
	<link>http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/</link>
	<description>A biblioblog</description>
	<pubDate>Sun, 12 Oct 2008 04:59:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Metacatholic &#124; A little unofficial Biblical Studies carnivalette</title>
		<link>http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-34828</link>
		<dc:creator>Metacatholic &#124; A little unofficial Biblical Studies carnivalette</dc:creator>
		<pubDate>Fri, 07 Dec 2007 12:19:45 +0000</pubDate>
		<guid isPermaLink="false">http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-34828</guid>
		<description>[...] the – oh, so tedious – reading of them. There is other advice and opinion on giving papers by Kevin Wilson, Chris Heard, Mark Goodacre and Judy Redman. As someone who regularly skipped lectures when I knew [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] the – oh, so tedious – reading of them. There is other advice and opinion on giving papers by Kevin Wilson, Chris Heard, Mark Goodacre and Judy Redman. As someone who regularly skipped lectures when I knew [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Things to Avoid in a Scholarly Presentation &#171; Hevel: A Chasing After Wind</title>
		<link>http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-34475</link>
		<dc:creator>Things to Avoid in a Scholarly Presentation &#171; Hevel: A Chasing After Wind</dc:creator>
		<pubDate>Mon, 03 Dec 2007 04:28:29 +0000</pubDate>
		<guid isPermaLink="false">http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-34475</guid>
		<description>[...] to Avoid in a Scholarly&#160;Presentation  I just saw this great post by Kevin Wilson over at Blue Cord. He lists several recommendations for things not to do in an [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] to Avoid in a Scholarly&nbsp;Presentation  I just saw this great post by Kevin Wilson over at Blue Cord. He lists several recommendations for things not to do in an [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blue Cord &#187; More on How to Give a Paper</title>
		<link>http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-33838</link>
		<dc:creator>Blue Cord &#187; More on How to Give a Paper</dc:creator>
		<pubDate>Sun, 25 Nov 2007 23:44:06 +0000</pubDate>
		<guid isPermaLink="false">http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-33838</guid>
		<description>[...] week while at the SBL, I wrote on things to avoid in a scholarly paper. It has generated some nice comments and has floated around the biblioblogosphere.  Chris Heard at [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] week while at the <acronym title="Society of Biblical Literature">SBL</acronym>, I wrote on things to avoid in a scholarly paper. It has generated some nice comments and has floated around the biblioblogosphere.  Chris Heard at [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Awilum.com &#187; Conference Presentations Post-Mortem(s)</title>
		<link>http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-33831</link>
		<dc:creator>Awilum.com &#187; Conference Presentations Post-Mortem(s)</dc:creator>
		<pubDate>Sun, 25 Nov 2007 21:10:16 +0000</pubDate>
		<guid isPermaLink="false">http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-33831</guid>
		<description>[...] material well enough that you can talk about it with the audience, not just read from a script.  Kevin Wilson gives some helpful technical tips such as avoiding the &#8220;air quote marks&#8221; and vocalizing abbreviations such as i.e.  [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] material well enough that you can talk about it with the audience, not just read from a script.  Kevin Wilson gives some helpful technical tips such as avoiding the &#8220;air quote marks&#8221; and vocalizing abbreviations such as i.e.  [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Higgaion &#187; Advice for conference presenters</title>
		<link>http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-33765</link>
		<dc:creator>Higgaion &#187; Advice for conference presenters</dc:creator>
		<pubDate>Sun, 25 Nov 2007 00:29:29 +0000</pubDate>
		<guid isPermaLink="false">http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-33765</guid>
		<description>[...] I get to my own suggestions, please allow me to commend Kevin Wilson&#8217;s. I agree with every point. Also, I should add that I&#8217;m not innocent in any of these matters; [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I get to my own suggestions, please allow me to commend Kevin Wilson&#8217;s. I agree with every point. Also, I should add that I&#8217;m not innocent in any of these matters; [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin A. Wilson</title>
		<link>http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-33287</link>
		<dc:creator>Kevin A. Wilson</dc:creator>
		<pubDate>Mon, 19 Nov 2007 06:23:49 +0000</pubDate>
		<guid isPermaLink="false">http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-33287</guid>
		<description>Instead of the bunny ears, use actual words.  Usually something like "so-called" or "supposed" will do.  The tone of your voice can also indicate when you are using the word ironically or in a way other than the standard meaning.</description>
		<content:encoded><![CDATA[<p>Instead of the bunny ears, use actual words.  Usually something like &#8220;so-called&#8221; or &#8220;supposed&#8221; will do.  The tone of your voice can also indicate when you are using the word ironically or in a way other than the standard meaning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Getz</title>
		<link>http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-33282</link>
		<dc:creator>Jim Getz</dc:creator>
		<pubDate>Mon, 19 Nov 2007 04:32:10 +0000</pubDate>
		<guid isPermaLink="false">http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-33282</guid>
		<description>Good advice. Though, if you're at my paper I might have to do the quote marks once just for fun ;-)</description>
		<content:encoded><![CDATA[<p>Good advice. Though, if you&#8217;re at my paper I might have to do the quote marks once just for fun <img src='http://bluecord.org/biblioblog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-33276</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Mon, 19 Nov 2007 03:15:13 +0000</pubDate>
		<guid isPermaLink="false">http://bluecord.org/biblioblog/2007/11/things-to-avoid-in-a-scholarly-paper/#comment-33276</guid>
		<description>Kevin, what do you suggest presenters do as a substitute for bunny ears? Or is it the fact of wanting to enclose some word or phrase in quote marks that annoys you?</description>
		<content:encoded><![CDATA[<p>Kevin, what do you suggest presenters do as a substitute for bunny ears? Or is it the fact of wanting to enclose some word or phrase in quote marks that annoys you?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
