<?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: Tone is not black and white</title>
	<atom:link href="http://www.turningnewsintoknowledge.com/2007/09/05/tone-is-not-black-and-white/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.turningnewsintoknowledge.com/2007/09/05/tone-is-not-black-and-white/</link>
	<description>Turning News Into Knowledge – Understanding Information</description>
	<lastBuildDate>Fri, 06 Jan 2012 16:21:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Alan Chumley</title>
		<link>http://www.turningnewsintoknowledge.com/2007/09/05/tone-is-not-black-and-white/comment-page-1/#comment-561</link>
		<dc:creator>Alan Chumley</dc:creator>
		<pubDate>Mon, 01 Oct 2007 15:11:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.turningnewsintoknowledge.com/2007/09/05/tone-is-not-black-and-white/#comment-561</guid>
		<description>Yup, tone can be tricky.  Couple of things.

1.  I think too many rely too much on tone as a measure of an article&#039;s quality.  It&#039;s important, but it&#039;s best looked on as one among many potentially more meaningful variables and metrics.  Say no to tone alone.  :)

2.  You&#039;re right.  Tone is subjective and therein lies the problem.  The solution lies in a) the client and vendor/researcher/supplier agreeing ahead of time, in clear terms, what constitutes positive and negative (and all shades of grey in between) and b) in building consistency among those toning into the methodology.  Here, intercoder reliabiilty testing is important.  Put simply, all coders need to be periodically tested against each other and against the pre-set standard put in place by client and supplier.  How reliable are the coders?  How consisten are they?  The importance of this cannot be understated.

3.  What some often fail to do is multi-tone.  So, toning not only the overall article at the aggregate level, but toning, for example, brand references, product references, exec quotes etc.</description>
		<content:encoded><![CDATA[<p>Yup, tone can be tricky.  Couple of things.</p>
<p>1.  I think too many rely too much on tone as a measure of an article&#8217;s quality.  It&#8217;s important, but it&#8217;s best looked on as one among many potentially more meaningful variables and metrics.  Say no to tone alone.  <img src='http://www.turningnewsintoknowledge.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>2.  You&#8217;re right.  Tone is subjective and therein lies the problem.  The solution lies in a) the client and vendor/researcher/supplier agreeing ahead of time, in clear terms, what constitutes positive and negative (and all shades of grey in between) and b) in building consistency among those toning into the methodology.  Here, intercoder reliabiilty testing is important.  Put simply, all coders need to be periodically tested against each other and against the pre-set standard put in place by client and supplier.  How reliable are the coders?  How consisten are they?  The importance of this cannot be understated.</p>
<p>3.  What some often fail to do is multi-tone.  So, toning not only the overall article at the aggregate level, but toning, for example, brand references, product references, exec quotes etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

