<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Constructivist media for policy documents</title>
	<link>http://stc-on.org/quality/departments/news-quality-and-process/2006/09/03/constructivist-media-for-policy-documents/</link>
	<description>News and information from the QPI SIG, Society for Technical Communication</description>
	<pubDate>Fri, 10 Oct 2008 19:54:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Chris Whalley</title>
		<link>http://stc-on.org/quality/departments/news-quality-and-process/2006/09/03/constructivist-media-for-policy-documents/#comment-52</link>
		<pubDate>Thu, 07 Sep 2006 18:16:06 +0000</pubDate>
		<guid>http://stc-on.org/quality/departments/news-quality-and-process/2006/09/03/constructivist-media-for-policy-documents/#comment-52</guid>
					<description>I'm glad to see wikis are getting traction in the quality management and techinical communication worlds.  I've been experimenting with them for several years and I see two opportunities for wikis that have yet to be fully developed.  The first opportunity has to do with content control.  Wikis are famous, and notorious, for allowing anyone to post and edit content.  While this is good at empowering the readers to update the content, it also presents problems, especially in regulated industries where management approval of P&amp;#38;P content is required by law.  A wiki with an approval workflow built into the application is a huge opportunity.  I haven't seen this as an out-of-the-box feature yet and I believe it would further the adoption of wikis in the business world.  The second opportunity has to do with traditional electronic document management systems (EDMS).  EDMSs are entrenched in many organizations but it is often the case that documents are initially developed outside the EDMS and then imported as a complete first draft.  A wiki is the perfect place to collaboratively develop these draft documents.  The challenge is getting the wiki content, which is primarly web-based, into a document format such as Word.  Some wikis offer a Save Page as Word File option, but the quality of the output (in terms of styles and adherence to good word processing practices) is poor at best.  I think this could be another huge opportunities for wikis to gain market share in two ways... increasing the quality of wiki Save to Doc output and also the creation of a wiki module for EDMS systems such as Documentum or Master Control.  For anyone interested in experiment with a wiki, here's one that I've played with and like http://www.jotspot.com/ (no affiliation).</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad to see wikis are getting traction in the quality management and techinical communication worlds.  I&#8217;ve been experimenting with them for several years and I see two opportunities for wikis that have yet to be fully developed.  The first opportunity has to do with content control.  Wikis are famous, and notorious, for allowing anyone to post and edit content.  While this is good at empowering the readers to update the content, it also presents problems, especially in regulated industries where management approval of P&amp;P content is required by law.  A wiki with an approval workflow built into the application is a huge opportunity.  I haven&#8217;t seen this as an out-of-the-box feature yet and I believe it would further the adoption of wikis in the business world.  The second opportunity has to do with traditional electronic document management systems (EDMS).  EDMSs are entrenched in many organizations but it is often the case that documents are initially developed outside the EDMS and then imported as a complete first draft.  A wiki is the perfect place to collaboratively develop these draft documents.  The challenge is getting the wiki content, which is primarly web-based, into a document format such as Word.  Some wikis offer a Save Page as Word File option, but the quality of the output (in terms of styles and adherence to good word processing practices) is poor at best.  I think this could be another huge opportunities for wikis to gain market share in two ways&#8230; increasing the quality of wiki Save to Doc output and also the creation of a wiki module for EDMS systems such as Documentum or Master Control.  For anyone interested in experiment with a wiki, here&#8217;s one that I&#8217;ve played with and like <a href='http://www.jotspot.com/' rel='nofollow'>http://www.jotspot.com/</a> (no affiliation).
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
