<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:media="http://search.yahoo.com/mrss/"
> <channel><title>Comments on: What&#8217;s in a News Wiki?</title> <atom:link href="http://www.copress.org/2009/02/18/whats-in-a-news-wiki/feed/" rel="self" type="application/rss+xml" /><link>http://www.copress.org/2009/02/18/whats-in-a-news-wiki/</link> <description>Building a Better Technical Ecosystem for Student News Organizations</description> <lastBuildDate>Mon, 10 May 2010 13:35:43 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.1.1</generator> <item><title>By: Google Living Stories, Google Analytics and BCNI Philly &#124; CoPress</title><link>http://www.copress.org/2009/02/18/whats-in-a-news-wiki/comment-page-1/#comment-2409</link> <dc:creator>Google Living Stories, Google Analytics and BCNI Philly &#124; CoPress</dc:creator> <pubDate>Sun, 13 Dec 2009 01:18:26 +0000</pubDate> <guid
isPermaLink="false">http://www.copress.org/?p=1012#comment-2409</guid> <description>[...] Currently there&#8217;s no functionality for users to participate in the production of the page, a key component of the news wiki idea I&#8217;ve written about before, but what they have is a very cool start. Paul Bradshaw has more. (tks Brian [...]</description> <content:encoded><![CDATA[<p>[...] Currently there&#8217;s no functionality for users to participate in the production of the page, a key component of the news wiki idea I&#8217;ve written about before, but what they have is a very cool start. Paul Bradshaw has more. (tks Brian [...]</p> ]]></content:encoded> </item> <item><title>By: #swineflu and the News Ecology - Daniel Bachhuber</title><link>http://www.copress.org/2009/02/18/whats-in-a-news-wiki/comment-page-1/#comment-1611</link> <dc:creator>#swineflu and the News Ecology - Daniel Bachhuber</dc:creator> <pubDate>Mon, 27 Apr 2009 03:55:43 +0000</pubDate> <guid
isPermaLink="false">http://www.copress.org/?p=1012#comment-1611</guid> <description>[...] wasn&#8217;t satisfied with how the New York Times presented information to me. If they launched a true news wiki with similar or superior accessibility, I think they could steal my attention back for one reason: the New York Time has a brand of [...]</description> <content:encoded><![CDATA[<p>[...] wasn&#8217;t satisfied with how the New York Times presented information to me. If they launched a true news wiki with similar or superior accessibility, I think they could steal my attention back for one reason: the New York Time has a brand of [...]</p> ]]></content:encoded> </item> <item><title>By: Appropriate Mediums for Appropriate Conversations - Daniel Bachhuber</title><link>http://www.copress.org/2009/02/18/whats-in-a-news-wiki/comment-page-1/#comment-616</link> <dc:creator>Appropriate Mediums for Appropriate Conversations - Daniel Bachhuber</dc:creator> <pubDate>Wed, 25 Mar 2009 22:54:15 +0000</pubDate> <guid
isPermaLink="false">http://www.copress.org/?p=1012#comment-616</guid> <description>[...] and context your reporters are finding. A wiki dedicated specifically to this topic, much like the topical wiki I&#8217;ve described before, could provide the background information necessary to bring people up to speed, including how many [...]</description> <content:encoded><![CDATA[<p>[...] and context your reporters are finding. A wiki dedicated specifically to this topic, much like the topical wiki I&#8217;ve described before, could provide the background information necessary to bring people up to speed, including how many [...]</p> ]]></content:encoded> </item> <item><title>By: Wikis to (Re)build the News - Daniel Bachhuber</title><link>http://www.copress.org/2009/02/18/whats-in-a-news-wiki/comment-page-1/#comment-474</link> <dc:creator>Wikis to (Re)build the News - Daniel Bachhuber</dc:creator> <pubDate>Wed, 11 Mar 2009 22:25:17 +0000</pubDate> <guid
isPermaLink="false">http://www.copress.org/?p=1012#comment-474</guid> <description>[...] TechCrunch, then I would visit it every day. Innovate with the formats of journalism too; start a topical wiki that aggregates and synthesizes information on any given subject.  If you create an account on the site, or sign in via OpenID, allows users [...]</description> <content:encoded><![CDATA[<p>[...] TechCrunch, then I would visit it every day. Innovate with the formats of journalism too; start a topical wiki that aggregates and synthesizes information on any given subject.  If you create an account on the site, or sign in via OpenID, allows users [...]</p> ]]></content:encoded> </item> <item><title>By: Daniel Bachhuber</title><link>http://www.copress.org/2009/02/18/whats-in-a-news-wiki/comment-page-1/#comment-314</link> <dc:creator>Daniel Bachhuber</dc:creator> <pubDate>Wed, 18 Feb 2009 21:53:08 +0000</pubDate> <guid
isPermaLink="false">http://www.copress.org/?p=1012#comment-314</guid> <description>@Jeremy, I think you raise a good point about &quot;getting users to actually explore the ASUO wiki link.&quot; A bit of CSS (to distinguish between internal and external links) and reader education would easily fix this. You could also allow the option of reporting to the FB News Feed every time you made a significant contribution to the wiki. With the right design, I don&#039;t actually think this would be too big of a problem.</description> <content:encoded><![CDATA[<p>@Jeremy, I think you raise a good point about &#8220;getting users to actually explore the ASUO wiki link.&#8221; A bit of CSS (to distinguish between internal and external links) and reader education would easily fix this. You could also allow the option of reporting to the FB News Feed every time you made a significant contribution to the wiki. With the right design, I don&#8217;t actually think this would be too big of a problem.</p> ]]></content:encoded> </item> <item><title>By: Andrew</title><link>http://www.copress.org/2009/02/18/whats-in-a-news-wiki/comment-page-1/#comment-310</link> <dc:creator>Andrew</dc:creator> <pubDate>Wed, 18 Feb 2009 16:54:39 +0000</pubDate> <guid
isPermaLink="false">http://www.copress.org/?p=1012#comment-310</guid> <description>Nice post, some really great ideas in there. I also like the idea of keeping the articles short.I think that the biggest obstacle here would be the use of it. In past experience the hardest part about getting wikis (and even group blogs) off of the ground is getting students to actually use them. Our generation just seems to be too comfortable in consuming info without producing any.</description> <content:encoded><![CDATA[<p>Nice post, some really great ideas in there. I also like the idea of keeping the articles short.</p><p>I think that the biggest obstacle here would be the use of it. In past experience the hardest part about getting wikis (and even group blogs) off of the ground is getting students to actually use them. Our generation just seems to be too comfortable in consuming info without producing any.</p> ]]></content:encoded> </item> <item><title>By: Jeremy Blanchard</title><link>http://www.copress.org/2009/02/18/whats-in-a-news-wiki/comment-page-1/#comment-306</link> <dc:creator>Jeremy Blanchard</dc:creator> <pubDate>Wed, 18 Feb 2009 08:27:15 +0000</pubDate> <guid
isPermaLink="false">http://www.copress.org/?p=1012#comment-306</guid> <description>This is one of the most winning ideas I&#039;ve heard from you, Daniel.I think the contextualization that you&#039;re suggesting (by using a wiki) is wonderful. Reminds me a bit of the &lt;a href=&quot;http://en.wikipedia.org/wiki/Semantic_Web&quot; rel=&quot;nofollow&quot;&gt;Semantic Web&lt;/a&gt; concept that has been generating buzz the last year or two (maybe longer?).I think keeping the articles to a limited size is important.Couple risks I see: 1) Trying to have all the content in the world under one roof. 2) Getting users to actually explore the ASUO wiki link. They would need a way to know that it&#039;s a short summary instead of a link to their home page.Couple other comments:
Although it doesn&#039;t directly relate to the idea your proposing, I think &lt;a href=&quot;http://en.wikinews.org/wiki/Main_Page&quot; rel=&quot;nofollow&quot;&gt;wiki news&lt;/a&gt; deserves a mention.It&#039;s funny you should mention the confusing ASUO system. Every time I am involved with something, I constantly take mental notes about how the processes could be improved for the future. In terms of my recent work with the ASUO, I&#039;ve considered making a wiki specifically about the ASUO and their processes. It would be nearly impossible to get anyone besides myself to contribute content, but it would be insanely useful (if anyone were able to find it, which would be difficult also). I think the focus of the wiki would be to provide &quot;use cases&quot; for your interaction with the ASUO. Then you can see step-by-step directions. It would be a roadmap for interactions.Maybe I should get the senate to create a new position: Web Czar. I could make their website usable and effective. Haha.</description> <content:encoded><![CDATA[<p>This is one of the most winning ideas I&#8217;ve heard from you, Daniel.</p><p>I think the contextualization that you&#8217;re suggesting (by using a wiki) is wonderful. Reminds me a bit of the <a
href="http://en.wikipedia.org/wiki/Semantic_Web" rel="nofollow">Semantic Web</a> concept that has been generating buzz the last year or two (maybe longer?).</p><p>I think keeping the articles to a limited size is important.</p><p>Couple risks I see: 1) Trying to have all the content in the world under one roof. 2) Getting users to actually explore the ASUO wiki link. They would need a way to know that it&#8217;s a short summary instead of a link to their home page.</p><p>Couple other comments:<br
/> Although it doesn&#8217;t directly relate to the idea your proposing, I think <a
href="http://en.wikinews.org/wiki/Main_Page" rel="nofollow">wiki news</a> deserves a mention.</p><p>It&#8217;s funny you should mention the confusing ASUO system. Every time I am involved with something, I constantly take mental notes about how the processes could be improved for the future. In terms of my recent work with the ASUO, I&#8217;ve considered making a wiki specifically about the ASUO and their processes. It would be nearly impossible to get anyone besides myself to contribute content, but it would be insanely useful (if anyone were able to find it, which would be difficult also). I think the focus of the wiki would be to provide &#8220;use cases&#8221; for your interaction with the ASUO. Then you can see step-by-step directions. It would be a roadmap for interactions.</p><p>Maybe I should get the senate to create a new position: Web Czar. I could make their website usable and effective. Haha.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (user agent is rejected)
Database Caching 15/30 queries in 0.034 seconds using disk

Served from: www.copress.org @ 2012-02-08 23:35:42 -->
