<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: MS Wiki Vs Wiki</title>
	<atom:link href="http://itsallkm.wordpress.com/2007/04/02/ms-wiki-vs-wiki/feed/" rel="self" type="application/rss+xml" />
	<link>http://itsallkm.wordpress.com/2007/04/02/ms-wiki-vs-wiki/</link>
	<description>A guide to all things Knowledge Management</description>
	<lastBuildDate>Sun, 09 Mar 2008 12:04:41 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Arjun Thomas</title>
		<link>http://itsallkm.wordpress.com/2007/04/02/ms-wiki-vs-wiki/#comment-36</link>
		<dc:creator>Arjun Thomas</dc:creator>
		<pubDate>Mon, 09 Apr 2007 01:47:05 +0000</pubDate>
		<guid isPermaLink="false">http://itsallkm.wordpress.com/2007/04/02/ms-wiki-vs-wiki/#comment-36</guid>
		<description>It&#039;s a start. but from what i&#039;ve seen the wiki is actually structured like a document library on sharepoint. Which means you might be able to attach meta-tags to each &quot;article&quot;. Even if this is so, the freedom of being able to define which category your article belongs to , and have a navigation structure based on those categories is not something that is achievable out of the  box. We have managed to create some additional functionalities around sharepoint 2007 , but not in the wiki space as yet. 

Bottom line.... i&#039;m still waiting ver 2.0</description>
		<content:encoded><![CDATA[<p>It&#8217;s a start. but from what i&#8217;ve seen the wiki is actually structured like a document library on sharepoint. Which means you might be able to attach meta-tags to each &#8220;article&#8221;. Even if this is so, the freedom of being able to define which category your article belongs to , and have a navigation structure based on those categories is not something that is achievable out of the  box. We have managed to create some additional functionalities around sharepoint 2007 , but not in the wiki space as yet. </p>
<p>Bottom line&#8230;. i&#8217;m still waiting ver 2.0</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vincent Armato</title>
		<link>http://itsallkm.wordpress.com/2007/04/02/ms-wiki-vs-wiki/#comment-33</link>
		<dc:creator>Vincent Armato</dc:creator>
		<pubDate>Sun, 08 Apr 2007 15:17:20 +0000</pubDate>
		<guid isPermaLink="false">http://itsallkm.wordpress.com/2007/04/02/ms-wiki-vs-wiki/#comment-33</guid>
		<description>I&#039;m pretty certain that you can achieve a categorization in Sharepoint 2007 by simply content-typing each of the Wiki&#039;s which can enforce (or leave optional) a type specific attribute which you could call &#039;Category&#039;.  Every wiki then created could have this attribute that could drive all sorts of stuff like categorized views or even audience profiling based upon Wiki categories.</description>
		<content:encoded><![CDATA[<p>I&#8217;m pretty certain that you can achieve a categorization in Sharepoint 2007 by simply content-typing each of the Wiki&#8217;s which can enforce (or leave optional) a type specific attribute which you could call &#8216;Category&#8217;.  Every wiki then created could have this attribute that could drive all sorts of stuff like categorized views or even audience profiling based upon Wiki categories.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arjun Thomas</title>
		<link>http://itsallkm.wordpress.com/2007/04/02/ms-wiki-vs-wiki/#comment-24</link>
		<dc:creator>Arjun Thomas</dc:creator>
		<pubDate>Thu, 05 Apr 2007 04:35:54 +0000</pubDate>
		<guid isPermaLink="false">http://itsallkm.wordpress.com/2007/04/02/ms-wiki-vs-wiki/#comment-24</guid>
		<description>You make a good point Bob , and thanks for the response!!. While this is a great first step from microsoft, specially for a &quot;traditional&quot; Fortune 500. I think there is quite a ways to go before Microsoft can fully leverage the power of a Wiki engine. 

Would go a long way towards ensuring that things like PPT&#039;s and documents get created using this application. In my view making collaboration a whole lot easier, i&#039;ve battled with the whole &quot;versioning&quot; of documents on sharepoint... and honestly , this is far more user friendly...</description>
		<content:encoded><![CDATA[<p>You make a good point Bob , and thanks for the response!!. While this is a great first step from microsoft, specially for a &#8220;traditional&#8221; Fortune 500. I think there is quite a ways to go before Microsoft can fully leverage the power of a Wiki engine. </p>
<p>Would go a long way towards ensuring that things like PPT&#8217;s and documents get created using this application. In my view making collaboration a whole lot easier, i&#8217;ve battled with the whole &#8220;versioning&#8221; of documents on sharepoint&#8230; and honestly , this is far more user friendly&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Iliff</title>
		<link>http://itsallkm.wordpress.com/2007/04/02/ms-wiki-vs-wiki/#comment-22</link>
		<dc:creator>Bob Iliff</dc:creator>
		<pubDate>Wed, 04 Apr 2007 14:20:31 +0000</pubDate>
		<guid isPermaLink="false">http://itsallkm.wordpress.com/2007/04/02/ms-wiki-vs-wiki/#comment-22</guid>
		<description>I work for a &quot;traditional&quot; Fortune 500, and have really been rattling the bars on why we need wikis. I was (finally) told that SharePoint was coming, and have now looked at some of the online tutorials. What I was struck by is how MS Wiki (your term) seems to subordinate wikis as compilation &quot;editors&quot; to specific Office Documents. Does your team need to make a PowerPoint deck? Open a wiki. Create a Word document? Open a wiki!. I think this is actually very crafty! For an organization such as mine that is Office Document driven, the wiki is just a messy closet sitting (thankfully) somewhere else away from the Document Library. Can it still be useful in these structure? I think so, especially if the document title is: Why we only need the wiki.</description>
		<content:encoded><![CDATA[<p>I work for a &#8220;traditional&#8221; Fortune 500, and have really been rattling the bars on why we need wikis. I was (finally) told that SharePoint was coming, and have now looked at some of the online tutorials. What I was struck by is how MS Wiki (your term) seems to subordinate wikis as compilation &#8220;editors&#8221; to specific Office Documents. Does your team need to make a PowerPoint deck? Open a wiki. Create a Word document? Open a wiki!. I think this is actually very crafty! For an organization such as mine that is Office Document driven, the wiki is just a messy closet sitting (thankfully) somewhere else away from the Document Library. Can it still be useful in these structure? I think so, especially if the document title is: Why we only need the wiki.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
