<?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"
	>
<channel>
	<title>Comments on: Status tags for wiki pages?</title>
	<atom:link href="http://blog.tailorable.com/2008/01/22/status-tags-for-wiki-pages/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tailorable.com/2008/01/22/status-tags-for-wiki-pages/</link>
	<description>Robert's blog on collaboration, innovation and cool stuff</description>
	<pubDate>Fri,  5 Sep 2008 20:41:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Marcel</title>
		<link>http://blog.tailorable.com/2008/01/22/status-tags-for-wiki-pages/#comment-308</link>
		<dc:creator>Marcel</dc:creator>
		<pubDate>Thu, 13 Mar 2008 21:10:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tailorable.com/2008/01/22/status-tags-for-wiki-pages/#comment-308</guid>
		<description>Great idea to think about tagging here. Your current collection will work fine I think; adding more sub-disctinctions can be done later in the process. I agree with the comment of Jack "The key is helping people see what you want them to do with the tags" So I would suggest you to translate the different tags you came up with. Isn't it (technologically) possible (I don't know) to translate the words in a collection of assoicative pictograms which is more meaningful or atractive for users. I could imagine (quick braindump) something like a baby, youngster, mature, old person.  Just an idea.</description>
		<content:encoded><![CDATA[<p>Great idea to think about tagging here. Your current collection will work fine I think; adding more sub-disctinctions can be done later in the process. I agree with the comment of Jack &#8220;The key is helping people see what you want them to do with the tags&#8221; So I would suggest you to translate the different tags you came up with. Isn&#8217;t it (technologically) possible (I don&#8217;t know) to translate the words in a collection of assoicative pictograms which is more meaningful or atractive for users. I could imagine (quick braindump) something like a baby, youngster, mature, old person.  Just an idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://blog.tailorable.com/2008/01/22/status-tags-for-wiki-pages/#comment-214</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Mon, 18 Feb 2008 08:56:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tailorable.com/2008/01/22/status-tags-for-wiki-pages/#comment-214</guid>
		<description>Hi Ton,
We looked at Wikipedia indeed; that is for instance where the CandidateForDeletion comes from. We would like to see whether such a set of tags also works within an organizational context to maintain a user-generated list of wiki pages that need some maintenance.</description>
		<content:encoded><![CDATA[<p>Hi Ton,<br />
We looked at Wikipedia indeed; that is for instance where the CandidateForDeletion comes from. We would like to see whether such a set of tags also works within an organizational context to maintain a user-generated list of wiki pages that need some maintenance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ton Zijlstra</title>
		<link>http://blog.tailorable.com/2008/01/22/status-tags-for-wiki-pages/#comment-209</link>
		<dc:creator>Ton Zijlstra</dc:creator>
		<pubDate>Sat, 16 Feb 2008 11:34:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tailorable.com/2008/01/22/status-tags-for-wiki-pages/#comment-209</guid>
		<description>You could also have a look at the way Wikipedia marks pages whose content is under discussion, considered controversial, not within the Wikipedia guidelines in some way, or candidates for deletion.</description>
		<content:encoded><![CDATA[<p>You could also have a look at the way Wikipedia marks pages whose content is under discussion, considered controversial, not within the Wikipedia guidelines in some way, or candidates for deletion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://blog.tailorable.com/2008/01/22/status-tags-for-wiki-pages/#comment-160</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Tue, 29 Jan 2008 13:35:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tailorable.com/2008/01/22/status-tags-for-wiki-pages/#comment-160</guid>
		<description>My colleague Ruud suggests:
- "Preliminary": stage prior to a "FirstDraft". For instance: thoughts, notes about a brainstorm, initial ideas to start a discussion, and so and. Could also be called "NeedsDiscussion".
- "Final": maybe not suitable for a wiki, but could be a useful tag to indicate pages that are just "done". At least an alternative for "Official".</description>
		<content:encoded><![CDATA[<p>My colleague Ruud suggests:<br />
- &#8220;Preliminary&#8221;: stage prior to a &#8220;FirstDraft&#8221;. For instance: thoughts, notes about a brainstorm, initial ideas to start a discussion, and so and. Could also be called &#8220;NeedsDiscussion&#8221;.<br />
- &#8220;Final&#8221;: maybe not suitable for a wiki, but could be a useful tag to indicate pages that are just &#8220;done&#8221;. At least an alternative for &#8220;Official&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack Vinson</title>
		<link>http://blog.tailorable.com/2008/01/22/status-tags-for-wiki-pages/#comment-159</link>
		<dc:creator>Jack Vinson</dc:creator>
		<pubDate>Tue, 29 Jan 2008 03:40:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tailorable.com/2008/01/22/status-tags-for-wiki-pages/#comment-159</guid>
		<description>The key, I think, is helping people see what you want them to do with the tags.  So, maybe a front page that lets you slice and dice the tags and the underlying pages associated with them.  

The best examples of this I have seen are in a presentation from Jordan Frank of Traction Software (http://www.tractionsoftware.com) last fall.  He's seen clients use their software with very specific tags, and then those posts can be recombined in useful ways on a front page.  The example I perused also included machine tags, so you could sort/filter by creation date and owner and the like.</description>
		<content:encoded><![CDATA[<p>The key, I think, is helping people see what you want them to do with the tags.  So, maybe a front page that lets you slice and dice the tags and the underlying pages associated with them.  </p>
<p>The best examples of this I have seen are in a presentation from Jordan Frank of Traction Software (http://www.tractionsoftware.com) last fall.  He&#8217;s seen clients use their software with very specific tags, and then those posts can be recombined in useful ways on a front page.  The example I perused also included machine tags, so you could sort/filter by creation date and owner and the like.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
