<?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: Newspaper Wiki: Schematics</title>
	<atom:link href="http://informationarchitects.jp/newspaper-wiki-schematics/feed/" rel="self" type="application/rss+xml" />
	<link>http://informationarchitects.jp/newspaper-wiki-schematics/</link>
	<description>Information Architects Japan</description>
	<lastBuildDate>Fri, 09 Oct 2009 11:49:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: NERT: User Generated Panoramas &#124; stk.</title>
		<link>http://informationarchitects.jp/newspaper-wiki-schematics/comment-page-1/#comment-151645</link>
		<dc:creator>NERT: User Generated Panoramas &#124; stk.</dc:creator>
		<pubDate>Wed, 15 Oct 2008 10:11:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/newspaper-wiki-schematics#comment-151645</guid>
		<description>&lt;p&gt;[...] Nachrichtenseite als Wiki auf. Klingt bescheuert? Ist es aber gar nicht so arg, wenn man sich die genaueren Ausfuehrungen dort durchliest. Der Workflow sieht relativ durchdacht aus, und vor allem ist auch Raum fuer [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Nachrichtenseite als Wiki auf. Klingt bescheuert? Ist es aber gar nicht so arg, wenn man sich die genaueren Ausfuehrungen dort durchliest. Der Workflow sieht relativ durchdacht aus, und vor allem ist auch Raum fuer [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: A wiki newspaper? &#124; The Harvard Voice</title>
		<link>http://informationarchitects.jp/newspaper-wiki-schematics/comment-page-1/#comment-135445</link>
		<dc:creator>A wiki newspaper? &#124; The Harvard Voice</dc:creator>
		<pubDate>Tue, 05 Feb 2008 15:58:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/newspaper-wiki-schematics#comment-135445</guid>
		<description>&lt;p&gt;[...] more here, and here.    You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] more here, and here.    You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Zac Echola is muffin but trouble &#187; Will MinnPost.com work?</title>
		<link>http://informationarchitects.jp/newspaper-wiki-schematics/comment-page-1/#comment-82854</link>
		<dc:creator>Zac Echola is muffin but trouble &#187; Will MinnPost.com work?</dc:creator>
		<pubDate>Mon, 27 Aug 2007 17:49:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/newspaper-wiki-schematics#comment-82854</guid>
		<description>&lt;p&gt;[...] And then read this [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] And then read this [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: anmut und demut - DasMagazin.ch</title>
		<link>http://informationarchitects.jp/newspaper-wiki-schematics/comment-page-1/#comment-80634</link>
		<dc:creator>anmut und demut - DasMagazin.ch</dc:creator>
		<pubDate>Wed, 15 Aug 2007 20:59:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/newspaper-wiki-schematics#comment-80634</guid>
		<description>&lt;p&gt;[...] Journalisten schreiben, Amateure schreiben, Leser kommentieren und Besucher lesen. Ganz einfach. Und es sieht auch noch unglaublich sch&#246;n [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Journalisten schreiben, Amateure schreiben, Leser kommentieren und Besucher lesen. Ganz einfach. Und es sieht auch noch unglaublich sch&#246;n [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver Reichenstein</title>
		<link>http://informationarchitects.jp/newspaper-wiki-schematics/comment-page-1/#comment-71589</link>
		<dc:creator>Oliver Reichenstein</dc:creator>
		<pubDate>Tue, 03 Jul 2007 10:10:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/newspaper-wiki-schematics#comment-71589</guid>
		<description>&lt;p&gt;Franky,&lt;/p&gt;

&lt;p&gt;I rarely delete comments. Here are the reasons to delete comments:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;If I feel that someone is spamming &lt;/li&gt;
&lt;li&gt;If there is a propaganda-suspiscion&lt;/li&gt;
&lt;li&gt;Childish and offensive comments&lt;/li&gt;
&lt;li&gt;If someone goes on and on trying to prove his point for a lost cause, getting obsessive (I have no time for that)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If I deleted one of your comments because I misjudged it, I am sorry, but I don&#039;t censor people because of their opinion.&lt;/p&gt;

&lt;p&gt;Of course, I am only human, if I have a bad day, and someone just really pisses me off, I kick that bastard off my site. &lt;/p&gt;

&lt;p&gt;Lately I get a lot of iPhone and anti-iPhone propaganda. I delete most of it.&lt;/p&gt;

&lt;p&gt;The other day I had one of those anti-iPhone dudes here that posted a long seemingly prefabricated argumentation in spanish why some spanish woman shouldn&#039;t buy the iPhone. And I had a bad day. So that means hasta la vista. It&#039;s not a spanish site and it&#039;s not meant to be used as a propaganda platform.&lt;/p&gt;

&lt;p&gt;Accusing me of censorship after all I allow here (check out the 95% typography post), actually kind of pisses me off, but I have a good day, and it?s a relevant suspicion (are these just the positive posts? - Answer no!) &lt;/p&gt;

&lt;p&gt;In the beginning I had a lot of moaning and whining and complaining about my grammar, but recently people became quite nice. &lt;/p&gt;

&lt;p&gt;Ah yes, and there was this anonymous stalker, that thried to find a weak point on every single post, trying to bully me on my site. Guess what, I tracked him down and told him, I&#039;d post his crap, if I could use his real name. And guess what again? He didn?t want me to.&lt;/p&gt;

&lt;p&gt;So which post did I delete that you felt had a good argument?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Franky,</p>

<p>I rarely delete comments. Here are the reasons to delete comments:</p>

<ul>
<li>If I feel that someone is spamming </li>
<li>If there is a propaganda-suspiscion</li>
<li>Childish and offensive comments</li>
<li>If someone goes on and on trying to prove his point for a lost cause, getting obsessive (I have no time for that)</li>
</ul>

<p>If I deleted one of your comments because I misjudged it, I am sorry, but I don&#8217;t censor people because of their opinion.</p>

<p>Of course, I am only human, if I have a bad day, and someone just really pisses me off, I kick that bastard off my site. </p>

<p>Lately I get a lot of iPhone and anti-iPhone propaganda. I delete most of it.</p>

<p>The other day I had one of those anti-iPhone dudes here that posted a long seemingly prefabricated argumentation in spanish why some spanish woman shouldn&#8217;t buy the iPhone. And I had a bad day. So that means hasta la vista. It&#8217;s not a spanish site and it&#8217;s not meant to be used as a propaganda platform.</p>

<p>Accusing me of censorship after all I allow here (check out the 95% typography post), actually kind of pisses me off, but I have a good day, and it?s a relevant suspicion (are these just the positive posts? &#8211; Answer no!) </p>

<p>In the beginning I had a lot of moaning and whining and complaining about my grammar, but recently people became quite nice. </p>

<p>Ah yes, and there was this anonymous stalker, that thried to find a weak point on every single post, trying to bully me on my site. Guess what, I tracked him down and told him, I&#8217;d post his crap, if I could use his real name. And guess what again? He didn?t want me to.</p>

<p>So which post did I delete that you felt had a good argument?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Franky Flowers</title>
		<link>http://informationarchitects.jp/newspaper-wiki-schematics/comment-page-1/#comment-71587</link>
		<dc:creator>Franky Flowers</dc:creator>
		<pubDate>Tue, 03 Jul 2007 09:38:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/newspaper-wiki-schematics#comment-71587</guid>
		<description>&lt;p&gt;Hm, the fact some comments get simply erased if you re not comfortable with em, sounds a bit like censorship.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hm, the fact some comments get simply erased if you re not comfortable with em, sounds a bit like censorship.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Thuan Huynh</title>
		<link>http://informationarchitects.jp/newspaper-wiki-schematics/comment-page-1/#comment-65465</link>
		<dc:creator>Thuan Huynh</dc:creator>
		<pubDate>Sun, 17 Jun 2007 08:55:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/newspaper-wiki-schematics#comment-65465</guid>
		<description>&lt;p&gt;I agree on the role that an easy text editor could play. Just a suggestion: the text editor should also contain flag and other tags used by the wiki engine. Tags are the way to turn a wiki build for raw text files to a more structured system.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I agree on the role that an easy text editor could play. Just a suggestion: the text editor should also contain flag and other tags used by the wiki engine. Tags are the way to turn a wiki build for raw text files to a more structured system.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: David Wark</title>
		<link>http://informationarchitects.jp/newspaper-wiki-schematics/comment-page-1/#comment-63210</link>
		<dc:creator>David Wark</dc:creator>
		<pubDate>Mon, 11 Jun 2007 12:43:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/newspaper-wiki-schematics#comment-63210</guid>
		<description>&lt;p&gt;Fascinating - fascinated already&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Fascinating &#8211; fascinated already</p>]]></content:encoded>
	</item>
	<item>
		<title>By: hypernarrative.com</title>
		<link>http://informationarchitects.jp/newspaper-wiki-schematics/comment-page-1/#comment-50651</link>
		<dc:creator>hypernarrative.com</dc:creator>
		<pubDate>Sat, 21 Apr 2007 00:40:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/newspaper-wiki-schematics#comment-50651</guid>
		<description>&lt;p&gt;[...] Information Architects Japan » iA Notebook » Newspaper Wiki: Schematics (tags: media internet wiki washingtonpost newspaper news) [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Information Architects Japan » iA Notebook » Newspaper Wiki: Schematics (tags: media internet wiki washingtonpost newspaper news) [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Barkow</title>
		<link>http://informationarchitects.jp/newspaper-wiki-schematics/comment-page-1/#comment-49098</link>
		<dc:creator>Tim Barkow</dc:creator>
		<pubDate>Fri, 13 Apr 2007 15:03:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/newspaper-wiki-schematics#comment-49098</guid>
		<description>&lt;p&gt;I&#039;m wondering about the user roles and whether they could be simplified. The language in the Duties row morphs from &quot;duties&quot; to &quot;responsibilities&quot; and &quot;potential punishments&quot; once it gets to users, which makes me a little nervous. &lt;/p&gt;

&lt;p&gt;I don&#039;t remember all the details on the LA Times wiki debacle, but I suspect that like most big media companies, they figured they could just bolt on community and sell ads on the resulting traffic. The very fact that they were unprepared for the chaos that ensued pretty much proves this out. Anyone who&#039;s managed an online community knows how much tending it takes to be successful. It&#039;s very much like gardening (public, community gardening).&lt;/p&gt;

&lt;p&gt;What you can learn from successful startups like Flickr is that 1) you have to spend a lot of time on your site answering questions and helping new users learn their way around, and 2) eventually, you are going to need your user community to help with #1. If you&#039;ve built a valuable resource your users care about, they will want to help out.&lt;/p&gt;

&lt;p&gt;But to get there requires trust.&lt;/p&gt;

&lt;p&gt;Who do you value more: Journalist Joe who writes a popular column on the site, or User Sally who spends hours in the comment threads, keeping conversations on track and answering questions? They both have an important role to play.&lt;/p&gt;

&lt;p&gt;So -- I&#039;d flatten the user roles by combining Journalist, Amateur, and Commenter.&lt;/p&gt;

&lt;p&gt;Requiring registration, the ability to flag objectionable content, ban users, and having an attentive human moderator will allow you to protect the space you&#039;ve created while trusting your users.  &lt;/p&gt;

&lt;p&gt;As for Jeff&#039;s comment on structured data, it&#039;s true that wiki pages don&#039;t include that as a default. But I wonder if you couldn&#039;t achieve much of the same thing (without the db efficiencies, of course) by using custom input forms that could translate an obituary, for example, and display it as a microformat? Bit of a hack, I admit.&lt;/p&gt;

&lt;p&gt;I&#039;m definitely on Jeff&#039;s side re: semantic, structured data. The advent of the Django (what Ellington CMS is built on) and Ruby on Rails Web app frameworks is really changing the entire software game, and you really need to be thinking about re-evaluating your software strategy.&lt;/p&gt;

&lt;p&gt;These frameworks are radically changing how Web apps are developed, deployed and managed. And the risks involved in going with a custom solution can often be lower than customizing a large open source project.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;m wondering about the user roles and whether they could be simplified. The language in the Duties row morphs from &#8220;duties&#8221; to &#8220;responsibilities&#8221; and &#8220;potential punishments&#8221; once it gets to users, which makes me a little nervous. </p>

<p>I don&#8217;t remember all the details on the LA Times wiki debacle, but I suspect that like most big media companies, they figured they could just bolt on community and sell ads on the resulting traffic. The very fact that they were unprepared for the chaos that ensued pretty much proves this out. Anyone who&#8217;s managed an online community knows how much tending it takes to be successful. It&#8217;s very much like gardening (public, community gardening).</p>

<p>What you can learn from successful startups like Flickr is that 1) you have to spend a lot of time on your site answering questions and helping new users learn their way around, and 2) eventually, you are going to need your user community to help with #1. If you&#8217;ve built a valuable resource your users care about, they will want to help out.</p>

<p>But to get there requires trust.</p>

<p>Who do you value more: Journalist Joe who writes a popular column on the site, or User Sally who spends hours in the comment threads, keeping conversations on track and answering questions? They both have an important role to play.</p>

<p>So &#8212; I&#8217;d flatten the user roles by combining Journalist, Amateur, and Commenter.</p>

<p>Requiring registration, the ability to flag objectionable content, ban users, and having an attentive human moderator will allow you to protect the space you&#8217;ve created while trusting your users.  </p>

<p>As for Jeff&#8217;s comment on structured data, it&#8217;s true that wiki pages don&#8217;t include that as a default. But I wonder if you couldn&#8217;t achieve much of the same thing (without the db efficiencies, of course) by using custom input forms that could translate an obituary, for example, and display it as a microformat? Bit of a hack, I admit.</p>

<p>I&#8217;m definitely on Jeff&#8217;s side re: semantic, structured data. The advent of the Django (what Ellington CMS is built on) and Ruby on Rails Web app frameworks is really changing the entire software game, and you really need to be thinking about re-evaluating your software strategy.</p>

<p>These frameworks are radically changing how Web apps are developed, deployed and managed. And the risks involved in going with a custom solution can often be lower than customizing a large open source project.</p>]]></content:encoded>
	</item>
</channel>
</rss>
