<?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 for The Future of Context</title>
	<atom:link href="http://www.futureofcontext.com/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://www.futureofcontext.com</link>
	<description>Getting the bigger picture online.</description>
	<lastBuildDate>Tue, 07 Sep 2010 01:24:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on Abolish tags, say hi to relationships by Reg Chua</title>
		<link>http://www.futureofcontext.com/?p=32#comment-1024</link>
		<dc:creator>Reg Chua</dc:creator>
		<pubDate>Tue, 07 Sep 2010 01:24:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.futureofcontext.com/?p=32#comment-1024</guid>
		<description>I agree heartily that tags are a very primitive way to organize information; but even more contextual and categorized tags will likely be limited.  They&#039;ll help search, but what we really ought to be doing is looking at the structure of the information we create, so that we optimize the form for the content. 

For example, imagine a comprehensive stock market report or sports story that&#039;s micro-tagged to within an inch of its life; it&#039;s still not as useful as a table of stocks or a box score.  That&#039;s not to say the stories are useful; only that the tables, by virtue of layout and structure, also have value.  

A lot of the discussion about search, and information, is centered around text (and to some extent images) in the narrative form and how to make it more contextual or searchable, etc; that&#039;s important, but so too is thinking about the form of that text, and whether it should be captured more in tabular or other data structures, ala Politifact. 

I muse more on this at my blog, structureofnews.wordpress.com</description>
		<content:encoded><![CDATA[<p>I agree heartily that tags are a very primitive way to organize information; but even more contextual and categorized tags will likely be limited.  They&#8217;ll help search, but what we really ought to be doing is looking at the structure of the information we create, so that we optimize the form for the content. </p>
<p>For example, imagine a comprehensive stock market report or sports story that&#8217;s micro-tagged to within an inch of its life; it&#8217;s still not as useful as a table of stocks or a box score.  That&#8217;s not to say the stories are useful; only that the tables, by virtue of layout and structure, also have value.  </p>
<p>A lot of the discussion about search, and information, is centered around text (and to some extent images) in the narrative form and how to make it more contextual or searchable, etc; that&#8217;s important, but so too is thinking about the form of that text, and whether it should be captured more in tabular or other data structures, ala Politifact. </p>
<p>I muse more on this at my blog, structureofnews.wordpress.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Abolish tags, say hi to relationships by Getting Beyond Getting Beyond Tags &#171; (Re)Structuring Journalism</title>
		<link>http://www.futureofcontext.com/?p=32#comment-1023</link>
		<dc:creator>Getting Beyond Getting Beyond Tags &#171; (Re)Structuring Journalism</dc:creator>
		<pubDate>Tue, 07 Sep 2010 01:12:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.futureofcontext.com/?p=32#comment-1023</guid>
		<description>[...] Beyond Getting Beyond&#160;Tags    Over at The Future of Context, a post on the limitations of tags, which I heartily endorse.  Tags, it notes, are a very primitive way of [...]</description>
		<content:encoded><![CDATA[<p>[...] Beyond Getting Beyond&nbsp;Tags    Over at The Future of Context, a post on the limitations of tags, which I heartily endorse.  Tags, it notes, are a very primitive way of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Get rid of articles and stories, follow topics by Reg Chua</title>
		<link>http://www.futureofcontext.com/?p=29#comment-1022</link>
		<dc:creator>Reg Chua</dc:creator>
		<pubDate>Mon, 06 Sep 2010 10:36:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.futureofcontext.com/?p=29#comment-1022</guid>
		<description>I agree that topics pages - as curated, well-thought-out summaries of information - are critical, and can and should easily supplant articles for a host of types of information.

The real problem is that they can be - with the exception of Wikipedia - very costly to produce in any kind of real-time if we want them to be any good.   One thing I&#039;m trying to address on my blog is how we can mechanize some parts of this, by restructuring the process of journalism, the way that Politifact (www.politifact.com) did very effectively for fact-checking statements of politicians. 

That&#039;s not a perfect solution, but it&#039;s relatively cost-effective, and continually updated - what we want any topics page to be.</description>
		<content:encoded><![CDATA[<p>I agree that topics pages &#8211; as curated, well-thought-out summaries of information &#8211; are critical, and can and should easily supplant articles for a host of types of information.</p>
<p>The real problem is that they can be &#8211; with the exception of Wikipedia &#8211; very costly to produce in any kind of real-time if we want them to be any good.   One thing I&#8217;m trying to address on my blog is how we can mechanize some parts of this, by restructuring the process of journalism, the way that Politifact (www.politifact.com) did very effectively for fact-checking statements of politicians. </p>
<p>That&#8217;s not a perfect solution, but it&#8217;s relatively cost-effective, and continually updated &#8211; what we want any topics page to be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Abolish tags, say hi to relationships by Ikaika Hussey</title>
		<link>http://www.futureofcontext.com/?p=32#comment-1021</link>
		<dc:creator>Ikaika Hussey</dc:creator>
		<pubDate>Sat, 28 Aug 2010 19:30:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.futureofcontext.com/?p=32#comment-1021</guid>
		<description>@Stijn: I&#039;ve been following your posts here and your blog re relationships; excellent suggestions. We&#039;re working on implementing your ideas on our local news site, The Hawaii Independent. I&#039;ll let you know how it goes. FYI, we&#039;re running on ExpressionEngine, which has a very flexible templating system and makes it easy to relate posts to each other. We&#039;ve got one weblog for all of our &quot;stories,&quot; and then separate weblogs for an index of people, and index of organizations, and index of events, and an index of topics and themes. We&#039;re using a wonderful relationship plug-in called Playa to interrelate our story posts with respective people, orgs, topics, etc. It&#039;s going well -- the next challenge is to train our staff and readers to understand and take advantage of this architecture. I&#039;m grateful for the time you&#039;ve put into thinking this through, and we&#039;re happy to (try to) implement it.

Ikaika Hussey
Publisher, The Hawaii Independendent</description>
		<content:encoded><![CDATA[<p>@Stijn: I&#8217;ve been following your posts here and your blog re relationships; excellent suggestions. We&#8217;re working on implementing your ideas on our local news site, The Hawaii Independent. I&#8217;ll let you know how it goes. FYI, we&#8217;re running on ExpressionEngine, which has a very flexible templating system and makes it easy to relate posts to each other. We&#8217;ve got one weblog for all of our &#8220;stories,&#8221; and then separate weblogs for an index of people, and index of organizations, and index of events, and an index of topics and themes. We&#8217;re using a wonderful relationship plug-in called Playa to interrelate our story posts with respective people, orgs, topics, etc. It&#8217;s going well &#8212; the next challenge is to train our staff and readers to understand and take advantage of this architecture. I&#8217;m grateful for the time you&#8217;ve put into thinking this through, and we&#8217;re happy to (try to) implement it.</p>
<p>Ikaika Hussey<br />
Publisher, The Hawaii Independendent</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on After the panel by Robert Nagle</title>
		<link>http://www.futureofcontext.com/?p=59#comment-1020</link>
		<dc:creator>Robert Nagle</dc:creator>
		<pubDate>Sun, 11 Jul 2010 15:09:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.futureofcontext.com/?p=59#comment-1020</guid>
		<description>And the most important thing: the &lt;a href=&quot;http://audio.sxsw.com/2010/podcasts/031510i_FutureOfContext.mp3&quot; rel=&quot;nofollow&quot;&gt;mp3 of the panel&lt;/a&gt;!</description>
		<content:encoded><![CDATA[<p>And the most important thing: the <a href="http://audio.sxsw.com/2010/podcasts/031510i_FutureOfContext.mp3" rel="nofollow">mp3 of the panel</a>!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Giving context a voice by eyeconoclast</title>
		<link>http://www.futureofcontext.com/?p=26#comment-1019</link>
		<dc:creator>eyeconoclast</dc:creator>
		<pubDate>Thu, 08 Jul 2010 23:15:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.futureofcontext.com/?p=26#comment-1019</guid>
		<description>While voice may be compelling for deeper dives, my sense is that visual presentation is more important in a high-level overview that &quot;hooks&quot; the reader into further exploration. Specifically, interactive graphics such as timelines with clickable events utilize our innate graphical processing capabilities and allow drilling down on topic facets in a flexible manner.</description>
		<content:encoded><![CDATA[<p>While voice may be compelling for deeper dives, my sense is that visual presentation is more important in a high-level overview that &#8220;hooks&#8221; the reader into further exploration. Specifically, interactive graphics such as timelines with clickable events utilize our innate graphical processing capabilities and allow drilling down on topic facets in a flexible manner.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Do verbal and visual work differently as context? by Ecks</title>
		<link>http://www.futureofcontext.com/?p=37#comment-1018</link>
		<dc:creator>Ecks</dc:creator>
		<pubDate>Wed, 12 May 2010 16:49:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.futureofcontext.com/?p=37#comment-1018</guid>
		<description>No, it&#039;s not a visual vs. verbal thing, because if you got a picture of someone carrying out a revealing act (kicking the proverbial puppy, sneering at the proverbial proffered baby) there&#039;s no way you wouldn&#039;t use it. The difference is that when you take a picture of someone just standing around or talking, and all you are trying to judge is how attractive they are in the photo, or whether this is a typical countenance for them, it is trivially easy to get a photo that looks bad. Take photos of anybody talking and you can quickly catch them with their mouth open and an asymmetrical expression that looks ugly - because cameras freeze moments without context that are shorter than watching humans would be able to process in real time. Publishing such a photo therefore says more about the photographers agenda (i.e., &quot;I want to make person X look ugly&quot;) than it does about the truth of the matter being photographed. 

Even verbal quotes we aren&#039;t supposed to take TOO badly out of context. If a candidate in a tight race went home at the end of a very long night saying to the local reporter &quot;ok, that&#039;s it, I&#039;m gone,&quot; it would be very irresponsible of the reporter to publish a headline that said &quot;candidate in tight race:&quot;I&#039;m gone!&quot;&quot;  

So in short, it&#039;s not verbal vs. visual, it&#039;s minimal context necessary to establish meaning.</description>
		<content:encoded><![CDATA[<p>No, it&#8217;s not a visual vs. verbal thing, because if you got a picture of someone carrying out a revealing act (kicking the proverbial puppy, sneering at the proverbial proffered baby) there&#8217;s no way you wouldn&#8217;t use it. The difference is that when you take a picture of someone just standing around or talking, and all you are trying to judge is how attractive they are in the photo, or whether this is a typical countenance for them, it is trivially easy to get a photo that looks bad. Take photos of anybody talking and you can quickly catch them with their mouth open and an asymmetrical expression that looks ugly &#8211; because cameras freeze moments without context that are shorter than watching humans would be able to process in real time. Publishing such a photo therefore says more about the photographers agenda (i.e., &#8220;I want to make person X look ugly&#8221;) than it does about the truth of the matter being photographed. </p>
<p>Even verbal quotes we aren&#8217;t supposed to take TOO badly out of context. If a candidate in a tight race went home at the end of a very long night saying to the local reporter &#8220;ok, that&#8217;s it, I&#8217;m gone,&#8221; it would be very irresponsible of the reporter to publish a headline that said &#8220;candidate in tight race:&#8221;I&#8217;m gone!&#8221;"  </p>
<p>So in short, it&#8217;s not verbal vs. visual, it&#8217;s minimal context necessary to establish meaning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Get rid of articles and stories, follow topics by Steve Myers</title>
		<link>http://www.futureofcontext.com/?p=29#comment-1013</link>
		<dc:creator>Steve Myers</dc:creator>
		<pubDate>Tue, 11 May 2010 22:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.futureofcontext.com/?p=29#comment-1013</guid>
		<description>For a post on Poynter Online today, &lt;a href=&quot;http://www.poynter.org/column.asp?id=101&amp;aid=183065&quot; rel=&quot;nofollow&quot;&gt;I  took a look at several different ways to provide background and context on the oil spill in the Gulf&lt;/a&gt;. 

Topic pages are an option, though they&#039;re limited for such a complex story. I agree with Ryan that it&#039;s really important to include a curated summary, which acts as a gentle introduction to the story. &lt;a href=&quot;http://topics.nytimes.com/top/reference/timestopics/subjects/o/oil_spills/gulf_of_mexico_2010/index.html?scp=2&amp;sq=deepwater%20horizon&amp;st=cse&quot; rel=&quot;nofollow&quot;&gt;The summary on NYT&#039;s topic page on the spill&lt;/a&gt; is set up mostly as a chronology of how the news unfolded. I think users would find it more useful to read a summary organized around topics (which is why I thought &lt;a href=&quot;http://www.propublica.org/ion/blog/item/gulf-oil-spill-faq-what-happened-what-may-have-caused-it-and-whos-responsib&quot; rel=&quot;nofollow&quot;&gt;ProPublica&#039;s Q&amp;A was a good guide to the key issues&lt;/a&gt;.)

I tried Google&#039;s &quot;Living Stories&quot; plugin for WordPress to see how it would work for this purpose. It&#039;s buggy and not ready for use in a newsroom, but it does let you divide the coverage into &quot;themes,&quot; which users can use to filter the stories listed on the topic page. I think the inclusion of these themes is one of the main contributions of the Living Stories approach. Themes (and other ways of personalizing the presentation) make a topic page useful not only for the uninitiated user, but the informed person who wants to investigate a particular issue.</description>
		<content:encoded><![CDATA[<p>For a post on Poynter Online today, <a href="http://www.poynter.org/column.asp?id=101&amp;aid=183065" rel="nofollow">I  took a look at several different ways to provide background and context on the oil spill in the Gulf</a>. </p>
<p>Topic pages are an option, though they&#8217;re limited for such a complex story. I agree with Ryan that it&#8217;s really important to include a curated summary, which acts as a gentle introduction to the story. <a href="http://topics.nytimes.com/top/reference/timestopics/subjects/o/oil_spills/gulf_of_mexico_2010/index.html?scp=2&amp;sq=deepwater%20horizon&amp;st=cse" rel="nofollow">The summary on NYT&#8217;s topic page on the spill</a> is set up mostly as a chronology of how the news unfolded. I think users would find it more useful to read a summary organized around topics (which is why I thought <a href="http://www.propublica.org/ion/blog/item/gulf-oil-spill-faq-what-happened-what-may-have-caused-it-and-whos-responsib" rel="nofollow">ProPublica&#8217;s Q&amp;A was a good guide to the key issues</a>.)</p>
<p>I tried Google&#8217;s &#8220;Living Stories&#8221; plugin for WordPress to see how it would work for this purpose. It&#8217;s buggy and not ready for use in a newsroom, but it does let you divide the coverage into &#8220;themes,&#8221; which users can use to filter the stories listed on the topic page. I think the inclusion of these themes is one of the main contributions of the Living Stories approach. Themes (and other ways of personalizing the presentation) make a topic page useful not only for the uninitiated user, but the informed person who wants to investigate a particular issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Get rid of articles and stories, follow topics by Ryan Pitts</title>
		<link>http://www.futureofcontext.com/?p=29#comment-999</link>
		<dc:creator>Ryan Pitts</dc:creator>
		<pubDate>Wed, 21 Apr 2010 22:27:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.futureofcontext.com/?p=29#comment-999</guid>
		<description>That&#039;s the approach we&#039;re taking with our Topic pages - a curated summary of an issue (with embedded links to further detail) coupled with a feed of latest updates. The pages also have a spot to provide background detail on an issue&#039;s key people and places.

Our purpose in creating them is the same as yours - we have no idea WHEN a new reader moved to town or otherwise decided to start paying attention to a local issue. So summarizing important local topics this way is a valuable act of journalism. These are the pages where you can get caught up, and then stay caught up.

They&#039;re simple, straightforward pages, but this is one of my favorite things we&#039;ve done in quite a while. I&#039;m not sure you can truly *replace* the article with a topic page, though -- I think the two pieces have a harmonious relationship. Because our stories are automatically aware of any Topic page they belong to, regardless of how you&#039;re coming into the story, that background is available. For example:

http://www.spokesman.com/stories/2010/apr/21/charge-stands-in-zehm-case/

http://www.spokesman.com/topics/otto-zehm/

I certainly would like to wire in notifications, though, so interested readers can more efficiently follow topics, like you describe.</description>
		<content:encoded><![CDATA[<p>That&#8217;s the approach we&#8217;re taking with our Topic pages &#8211; a curated summary of an issue (with embedded links to further detail) coupled with a feed of latest updates. The pages also have a spot to provide background detail on an issue&#8217;s key people and places.</p>
<p>Our purpose in creating them is the same as yours &#8211; we have no idea WHEN a new reader moved to town or otherwise decided to start paying attention to a local issue. So summarizing important local topics this way is a valuable act of journalism. These are the pages where you can get caught up, and then stay caught up.</p>
<p>They&#8217;re simple, straightforward pages, but this is one of my favorite things we&#8217;ve done in quite a while. I&#8217;m not sure you can truly *replace* the article with a topic page, though &#8212; I think the two pieces have a harmonious relationship. Because our stories are automatically aware of any Topic page they belong to, regardless of how you&#8217;re coming into the story, that background is available. For example:</p>
<p><a href="http://www.spokesman.com/stories/2010/apr/21/charge-stands-in-zehm-case/" rel="nofollow">http://www.spokesman.com/stories/2010/apr/21/charge-stands-in-zehm-case/</a></p>
<p><a href="http://www.spokesman.com/topics/otto-zehm/" rel="nofollow">http://www.spokesman.com/topics/otto-zehm/</a></p>
<p>I certainly would like to wire in notifications, though, so interested readers can more efficiently follow topics, like you describe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Get rid of articles and stories, follow topics by WSJ.com and Twitter @Anywhere &#171; Government 2.0</title>
		<link>http://www.futureofcontext.com/?p=29#comment-996</link>
		<dc:creator>WSJ.com and Twitter @Anywhere &#171; Government 2.0</dc:creator>
		<pubDate>Thu, 15 Apr 2010 22:20:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.futureofcontext.com/?p=29#comment-996</guid>
		<description>[...] the @twittermedia account &#8212; which has a beautiful blog &#8212; for the tip. Read more about &#8220;the future of context&#8221; and the concept that became reality with @JobsWSJ. #futureofcontext  [...]</description>
		<content:encoded><![CDATA[<p>[...] the @twittermedia account &#8212; which has a beautiful blog &#8212; for the tip. Read more about &#8220;the future of context&#8221; and the concept that became reality with @JobsWSJ. #futureofcontext  [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
