<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Journalism is outlining</title>
	<atom:link href="http://blogs.law.harvard.edu/doc/2012/11/30/journals-are-outlines-journalism-is-outlining/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/doc/2012/11/30/journals-are-outlines-journalism-is-outlining/</link>
	<description>Same old blog, brand new place</description>
	<lastBuildDate>Tue, 14 May 2013 21:32:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Social Media Tools for Work &#38; Learning &#187; Jay Cross &#8211; 2012&#8242;s Top Articles on Working Smarter</title>
		<link>http://blogs.law.harvard.edu/doc/2012/11/30/journals-are-outlines-journalism-is-outlining/comment-page-1/#comment-310257</link>
		<dc:creator>Social Media Tools for Work &#38; Learning &#187; Jay Cross &#8211; 2012&#8242;s Top Articles on Working Smarter</dc:creator>
		<pubDate>Sun, 30 Dec 2012 03:36:08 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=5728#comment-310257</guid>
		<description>[...] Journalism is outlining DOC SEARLS  &#124;  FRIDAY, NOVEMBER 30, 2012 [...]</description>
		<content:encoded><![CDATA[<p>[...] Journalism is outlining DOC SEARLS  |  FRIDAY, NOVEMBER 30, 2012 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Internet Time Blog : 2012&#8242;s Top articles on Working Smarter</title>
		<link>http://blogs.law.harvard.edu/doc/2012/11/30/journals-are-outlines-journalism-is-outlining/comment-page-1/#comment-310223</link>
		<dc:creator>Internet Time Blog : 2012&#8242;s Top articles on Working Smarter</dc:creator>
		<pubDate>Fri, 28 Dec 2012 23:29:25 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=5728#comment-310223</guid>
		<description>[...] Journalism is outlining DOC SEARLS   &#124;  FRIDAY, NOVEMBER 30, 2012 [...]</description>
		<content:encoded><![CDATA[<p>[...] Journalism is outlining DOC SEARLS   |  FRIDAY, NOVEMBER 30, 2012 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doc Searls</title>
		<link>http://blogs.law.harvard.edu/doc/2012/11/30/journals-are-outlines-journalism-is-outlining/comment-page-1/#comment-309428</link>
		<dc:creator>Doc Searls</dc:creator>
		<pubDate>Wed, 05 Dec 2012 00:21:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=5728#comment-309428</guid>
		<description>MichelBel, this is a personal blog. You and my other readers are my copy editors. Thanks to that help I often go back and make corrections. 

But I won&#039;t in this case, at least not yet. I meant journals where I used the word. Not journalists. I get now that this wasn&#039;t clear, but I&#039;m not sure its worth changing. On re-reading it with that in mind, do you think I should change it?</description>
		<content:encoded><![CDATA[<p>MichelBel, this is a personal blog. You and my other readers are my copy editors. Thanks to that help I often go back and make corrections. </p>
<p>But I won&#8217;t in this case, at least not yet. I meant journals where I used the word. Not journalists. I get now that this wasn&#8217;t clear, but I&#8217;m not sure its worth changing. On re-reading it with that in mind, do you think I should change it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MicheBel</title>
		<link>http://blogs.law.harvard.edu/doc/2012/11/30/journals-are-outlines-journalism-is-outlining/comment-page-1/#comment-309422</link>
		<dc:creator>MicheBel</dc:creator>
		<pubDate>Tue, 04 Dec 2012 20:19:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=5728#comment-309422</guid>
		<description>In your first few paragraphs, you use the word &quot;journals&quot; when I think you mean &quot;journalists.&quot;

Copy editing seems to be more of a dying art than good journalism.

--M</description>
		<content:encoded><![CDATA[<p>In your first few paragraphs, you use the word &#8220;journals&#8221; when I think you mean &#8220;journalists.&#8221;</p>
<p>Copy editing seems to be more of a dying art than good journalism.</p>
<p>&#8211;M</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Seitz</title>
		<link>http://blogs.law.harvard.edu/doc/2012/11/30/journals-are-outlines-journalism-is-outlining/comment-page-1/#comment-309386</link>
		<dc:creator>Bill Seitz</dc:creator>
		<pubDate>Mon, 03 Dec 2012 19:52:31 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=5728#comment-309386</guid>
		<description>I think outlines are great for creating and communicating sense through structure.

But in Jeff&#039;s case it seems like it&#039;s *data* he wants more than macro sense. (Or at least, the data piece is the part most-badly-served at the moment.)

This actually smells like a SemanticWeb use-case. We want every claim/statement to have some structured data, esp: (a) who&#039;s making the claim (could be person or institution); (b) location-stamp (lat/long or object-name); (c) timestamp. Then we probably want to be able to assign multiple tags to a claim (&quot;DownedTrees&quot;, &quot;Flooding&quot;, &quot;Trains&quot;, etc.). And some way for others to comment on each claim. 

Then some kind of GUI that integrates map view/filter with tag info and time-filtering (distinguish fresh claims from old claims).

(Hmm, hack idea - use FlickR since lots of photos have lat/long and timestamps. And the photo becomes a key part of the claim.)</description>
		<content:encoded><![CDATA[<p>I think outlines are great for creating and communicating sense through structure.</p>
<p>But in Jeff&#8217;s case it seems like it&#8217;s *data* he wants more than macro sense. (Or at least, the data piece is the part most-badly-served at the moment.)</p>
<p>This actually smells like a SemanticWeb use-case. We want every claim/statement to have some structured data, esp: (a) who&#8217;s making the claim (could be person or institution); (b) location-stamp (lat/long or object-name); (c) timestamp. Then we probably want to be able to assign multiple tags to a claim (&#8220;DownedTrees&#8221;, &#8220;Flooding&#8221;, &#8220;Trains&#8221;, etc.). And some way for others to comment on each claim. </p>
<p>Then some kind of GUI that integrates map view/filter with tag info and time-filtering (distinguish fresh claims from old claims).</p>
<p>(Hmm, hack idea &#8211; use FlickR since lots of photos have lat/long and timestamps. And the photo becomes a key part of the claim.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scripting News: iTunes is an outliner. &#124; Echo of Scripting News</title>
		<link>http://blogs.law.harvard.edu/doc/2012/11/30/journals-are-outlines-journalism-is-outlining/comment-page-1/#comment-309353</link>
		<dc:creator>Scripting News: iTunes is an outliner. &#124; Echo of Scripting News</dc:creator>
		<pubDate>Sun, 02 Dec 2012 16:29:15 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=5728#comment-309353</guid>
		<description>[...] Searls posted an item yesterday explaining how journalism is an [...]</description>
		<content:encoded><![CDATA[<p>[...] Searls posted an item yesterday explaining how journalism is an [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doc Searls</title>
		<link>http://blogs.law.harvard.edu/doc/2012/11/30/journals-are-outlines-journalism-is-outlining/comment-page-1/#comment-309349</link>
		<dc:creator>Doc Searls</dc:creator>
		<pubDate>Sun, 02 Dec 2012 11:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=5728#comment-309349</guid>
		<description>I&#039;ve added more to the post above to address the comments here.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve added more to the post above to address the comments here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bowerbird</title>
		<link>http://blogs.law.harvard.edu/doc/2012/11/30/journals-are-outlines-journalism-is-outlining/comment-page-1/#comment-309342</link>
		<dc:creator>bowerbird</dc:creator>
		<pubDate>Sun, 02 Dec 2012 06:54:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=5728#comment-309342</guid>
		<description>doc-

thanks for the answers.

winer has seen _everything_ as an outline
for about 3 decades, so i&#039;d have thought
that this idea would have occurred to him.
either way, now you know for next time...

i do not think lists on one blog could give
jarvis the full information he&#039;s looking for.
he clearly invokes leveraging of the social
that &quot;would let anyone in town annotate&quot;
and keep the information freshly updated.

i&#039;d certainly like to see your idea brought to
reality, as it could be a real breakthrough.

-bowerbird</description>
		<content:encoded><![CDATA[<p>doc-</p>
<p>thanks for the answers.</p>
<p>winer has seen _everything_ as an outline<br />
for about 3 decades, so i&#8217;d have thought<br />
that this idea would have occurred to him.<br />
either way, now you know for next time&#8230;</p>
<p>i do not think lists on one blog could give<br />
jarvis the full information he&#8217;s looking for.<br />
he clearly invokes leveraging of the social<br />
that &#8220;would let anyone in town annotate&#8221;<br />
and keep the information freshly updated.</p>
<p>i&#8217;d certainly like to see your idea brought to<br />
reality, as it could be a real breakthrough.</p>
<p>-bowerbird</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rex Hammock</title>
		<link>http://blogs.law.harvard.edu/doc/2012/11/30/journals-are-outlines-journalism-is-outlining/comment-page-1/#comment-309335</link>
		<dc:creator>Rex Hammock</dc:creator>
		<pubDate>Sat, 01 Dec 2012 21:50:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=5728#comment-309335</guid>
		<description>I (of course) agree w/ you 100% and on my list of &quot;things I will do next&quot; is a mastery of outlining, ala Dave&#039;s project, except for one thing: 

&quot;Go deeper than wikis. Wonderful as they are, wikis are very flat as outlines go.&quot;

The wiki platform (WikiMedia, in this reference) is open-source and is merely a content management system for collecting blank pages into an infinitely customizable taxonomy. While the configuration of the platform of Wikipedia may seem flat, there is nothing to prevent a wiki from utilizing an outlining approach. 

The Semantic MediaWiki community is filled with people who seem to be motivated by the same callings as the outlining community. (I don&#039;t know exactly what they mean by *semantic* as they use it, but it&#039;s community of people who seem to develop all the cool extensions that you don&#039;t see in Wikipedia, but make other wikis do cool things.)

Outlines can&#039;t be beat in ways that allow the writer / reader to go deep (vertically) into a topic. Wikis are great for connecting horizontal content.</description>
		<content:encoded><![CDATA[<p>I (of course) agree w/ you 100% and on my list of &#8220;things I will do next&#8221; is a mastery of outlining, ala Dave&#8217;s project, except for one thing: </p>
<p>&#8220;Go deeper than wikis. Wonderful as they are, wikis are very flat as outlines go.&#8221;</p>
<p>The wiki platform (WikiMedia, in this reference) is open-source and is merely a content management system for collecting blank pages into an infinitely customizable taxonomy. While the configuration of the platform of Wikipedia may seem flat, there is nothing to prevent a wiki from utilizing an outlining approach. </p>
<p>The Semantic MediaWiki community is filled with people who seem to be motivated by the same callings as the outlining community. (I don&#8217;t know exactly what they mean by *semantic* as they use it, but it&#8217;s community of people who seem to develop all the cool extensions that you don&#8217;t see in Wikipedia, but make other wikis do cool things.)</p>
<p>Outlines can&#8217;t be beat in ways that allow the writer / reader to go deep (vertically) into a topic. Wikis are great for connecting horizontal content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://blogs.law.harvard.edu/doc/2012/11/30/journals-are-outlines-journalism-is-outlining/comment-page-1/#comment-309332</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Sat, 01 Dec 2012 19:04:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=5728#comment-309332</guid>
		<description>The question of where someone stands is always predicated on where they sit. What journalist is going to get rewarded for putting together the lists? When there were news &#039;organizations&#039; there were people who had &#039;beats&#039; and the territory was clearly delineated and someone could be put on the utility issue and told to get and verify the service area. 
Now we have freelance nation, and every single journo is looking to make a mark- put out that story or image that differentiates them from the rest of the flock of wandering storytellers. That is how we have gotten the recent famous flameouts and cheats who didn&#039;t even bother with honest story telling but embellished or just made up stuff to have their names on something noteworthy enough to create a better paycheck.  
Again we have a situation where the business model trails the technology. And we have those with steady stable situations kibitzing- being off the field while they do- observing, judging and wondering why we don&#039;t have better observers who are working an unstable model. We haven&#039;t done any real work on deconstructing what was really valuable from tradition and making sure that we keep it when we &#039;innovate&#039;.
Ironically this parallels what we have in the broader world in which &quot;Sandy&quot; is something we need reporting on. We have consistently ignored the very apparent intelligence is in nature, whether it be how to learn, design, or just what to consume, that puts us in the situation of something like &quot;Sandy&quot; being a disaster instead of just one big storm that we take note of and adjust accordingly to.</description>
		<content:encoded><![CDATA[<p>The question of where someone stands is always predicated on where they sit. What journalist is going to get rewarded for putting together the lists? When there were news &#8216;organizations&#8217; there were people who had &#8216;beats&#8217; and the territory was clearly delineated and someone could be put on the utility issue and told to get and verify the service area.<br />
Now we have freelance nation, and every single journo is looking to make a mark- put out that story or image that differentiates them from the rest of the flock of wandering storytellers. That is how we have gotten the recent famous flameouts and cheats who didn&#8217;t even bother with honest story telling but embellished or just made up stuff to have their names on something noteworthy enough to create a better paycheck.<br />
Again we have a situation where the business model trails the technology. And we have those with steady stable situations kibitzing- being off the field while they do- observing, judging and wondering why we don&#8217;t have better observers who are working an unstable model. We haven&#8217;t done any real work on deconstructing what was really valuable from tradition and making sure that we keep it when we &#8216;innovate&#8217;.<br />
Ironically this parallels what we have in the broader world in which &#8220;Sandy&#8221; is something we need reporting on. We have consistently ignored the very apparent intelligence is in nature, whether it be how to learn, design, or just what to consume, that puts us in the situation of something like &#8220;Sandy&#8221; being a disaster instead of just one big storm that we take note of and adjust accordingly to.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
