<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Simplifying Complexity &#187; Social Media</title>
	<atom:link href="http://www.vanarsdall-infodesign.com/category/social_media/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vanarsdall-infodesign.com</link>
	<description>Technical Communication Services and Resources from VanArsdall InfoDesign</description>
	<lastBuildDate>Tue, 07 Sep 2010 03:39:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Flare Does DITA. Google Makes Waves.</title>
		<link>http://www.vanarsdall-infodesign.com/2009/06/04/flare-does-dita-google%c2%a0makes%c2%a0waves/</link>
		<comments>http://www.vanarsdall-infodesign.com/2009/06/04/flare-does-dita-google%c2%a0makes%c2%a0waves/#comments</comments>
		<pubDate>Fri, 05 Jun 2009 02:38:09 +0000</pubDate>
		<dc:creator>Eddie</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[MadCap Software]]></category>
		<category><![CDATA[Social Media]]></category>
		<category><![CDATA[madcap flare]]></category>

		<guid isPermaLink="false">http://www.vanarsdall-infodesign.com/?p=2667</guid>
		<description><![CDATA[This week, two significant events have created a buzz in the tech comm community. MadCap Flare 5 to be released soon On the tools front, MadCap Software will soon release Flare 5. The most significant feature is the addition of DITA as a project type. You can import DITA content, modify it, and publish it [...]]]></description>
			<content:encoded><![CDATA[<p></p><a name="top"></a>This week, two significant events have created a buzz in the tech comm community. </p>
<p><span id="more-2667"></span></p>
<h2>MadCap Flare 5 to be released soon</h2>
<p>On the tools front, MadCap Software will soon release Flare 5. The most significant feature is the addition of DITA as a project type. You can import DITA content, modify it, and publish it to various output types from Flare. </p>
<p>Paul Pehrson, a certified Flare trainer, developer, and MVP, has written an <a href="http://blog.paulpehrson.com/2009/06/03/pre-release-review-of-flare-v5/" title="Link to Paul Pehrson's blog" target="_blank">excellent, informative, pre-release review of Flare 5</a>. In addition to providing detail about the new DITA capabilities, Paul covers other new features.</p>
<p>If you&#8217;re a Flare user, I hope that you will share your impressions. Which of the new features will you use the most?</p>
<h2>Google unveils Google Wave</h2>
<p>Google recently announced <em>Google Wave</em>, a product that will have far-reaching ramifications for online communication and collaboration. For those who may not want to <a href="http://wave.google.com/" title="Link to Google Wave video" target="_blank">watch a nearly 90-minute video on Google Wave</a>, Austin-based writer/blogger <a href="http://greyfiti.com/?page_id=2">Shannon Greywalker</a> has done a thorough, effective job of explaining the technology. He has also written an intriguing, provocative take on how the technology will play a part in technical communication.</p>
<p>As a user of Gmail for personal and business email, I have long appreciated the threading and tagging features of Google mail. I used Gmail tagging long before I ever heard of folksonomies. I am excited to see Google take those features to a new level.</p>
<p>Even if you only use the Google search engine, <a href="http://greyfiti.com/?p=91" title="Link to Graywalker post on Google Wave" target="_blank">check out Shannon&#8217;s post</a>. If you&#8217;re curious and want to explore further, <a href="http://wave.google.com/" title="Link to Google Wave video" target="_blank">watch the Google video</a>. </p>
<h3>What others are saying about Google Wave</h3>
<ul>
<li><a href="http://googleblog.blogspot.com/2009/05/went-walkabout-brought-back-google-wave.html" title="Link to Google blog" target="_blank">Official Google Blog</a></li>
<li><a href="http://mashable.com/2009/05/28/google-wave-guide/" target="_blank">Mashable.com: A Complete Guide to Google Wave</a></li>
<li><a href="http://www.techcrunch.com/2009/05/28/google-wave-drips-with-ambition-can-it-fulfill-googles-grand-web-vision/" title="Link to TechCrunch post" target="_blank">TechCrunch: Google Wave Drips with Ambition</a></li>
</ul>
<h3>What do you think?</h3>
<p>Will Google Wave have a significant impact on the future of technical communication? What do you envision?</p>
<p><p><a href="#top">Back to top</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.vanarsdall-infodesign.com/2009/06/04/flare-does-dita-google%c2%a0makes%c2%a0waves/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Paving the Road to a User Utopia</title>
		<link>http://www.vanarsdall-infodesign.com/2009/05/31/paving-the-road-to-a-user-utopia/</link>
		<comments>http://www.vanarsdall-infodesign.com/2009/05/31/paving-the-road-to-a-user-utopia/#comments</comments>
		<pubDate>Sun, 31 May 2009 17:51:35 +0000</pubDate>
		<dc:creator>Eddie</dc:creator>
				<category><![CDATA[Information Design]]></category>
		<category><![CDATA[Information Development]]></category>
		<category><![CDATA[Social Media]]></category>
		<category><![CDATA[User Assistance]]></category>

		<guid isPermaLink="false">http://www.vanarsdall-infodesign.com/?p=2503</guid>
		<description><![CDATA[As writers of technical content, we strive to help reduce the number of technical support calls. Yet, a recent post on the blog of LugIron Software refers to a quote stating that documentation can also increase the number of service requests. Why? Users feel overwhelmed The first point in the quote states that overly comprehensive [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><a name="top"></a>As writers of technical content, we strive to help reduce the number of technical support calls. Yet, a <a href="http://blog.lugiron.com/2009/05/write-answers-not-documentation/" title="Link to LugIron Software blog post" target="_blank">recent post on the blog of LugIron Software</a> refers to a quote stating that documentation can also <em>increase</em> the number of service requests.</p>
<p>Why?</p>
<p><span id="more-2503"></span></p>
<h2>Users feel overwhelmed</h2>
<p>The first point in the quote states that overly comprehensive documentation scares users away. That may be true, but <em>comprehensive</em> simply means “of large scope” (<a href="http://dictionary.reference.com/" title="Link to Dictonary.com" target="_blank">Dictionary.com</a>) and says nothing about the quality of the documentation, how it is organized, or how it is tuned for search. </p>
<p>If you deliver a voluminous, printed tome, users will most likely avoid it. If you deliver a help site without clear points of entry and orientation, users will probably look elsewhere. If your information is difficult to browse and search results are low to non-existent, users will give up.</p>
<p>You can improve the likelihood of user satisfaction by</p>
<ul>
<li>Performing a careful user and task analysis</li>
<li>Single sourcing your content for modularity, reuse, and consistency</li>
<li>Ensuring that your information provides maximum search returns</li>
<li>Tailoring your information products to support roles and tasks.</li>
</ul>
<p>For example, nearly all users can benefit from a simple <em>Getting Started</em> guide or tutorial. The guide can cover installation and configuration and then provide a basic orientation to your software. Emphasize what they can do with the software&#8212;not how cool the UI is. From there, give them branching options tailored to their roles and desired outcomes.</p>
<h2>Users feel stimulated, but&#8230;</h2>
<p>The second point in the quote bears repeating:</p>
<blockquote><p>Documentation has so much cool stuff described, that it makes people’s imagination stimulated and they start thinking of other, even more exotic stuff they want to do but can not figure out and start a service request for it.</p></blockquote>
<p>This statement is indicative of a damned-if-you-do, damned-if-you-don&#8217;t problem. I have to wonder how user assistance information has been presented and organized if it is perceived mainly as describing “cool stuff.” I also wonder how it&#8217;s structured. My earlier comments about organization, orientation, and findability apply in this case, too.</p>
<p>Regardless, the “cool stuff” aspect of software  is a two-way street. If users want to improve the product or take it to another level, they need to provide feedback in the form of feature suggestions and enhancement requests. Product development teams cannot read their minds or restrain their imaginations.</p>
<h2>Users feel enabled</h2>
<p>Documentation that&#8217;s engaging should also make users feel that they have control. So how do you enable users without giving them too much?</p>
<p>You have created user profiles for your product, right? So why not ask &#8220;what type of user are you?&#8221; and give examples of typical users and associated tasks? Or ask &#8220;what would you like to do with Product X?&#8221; Then give readers some suggested branching points based on their roles and relevant tasks. Software and documentation need to be integrated in a way that provides a <em>solution for getting things done</em>. </p>
<p>Too often we waste a lot of words that over-emphasize the UI instead of including a separate UI reference section. If you find that you are constantly referring to the UI in ways that are not essential to performing tasks, then ask yourself whether the product design is truly effective or overly cumbersome. That may lead to a separate, challenging but necessary discussion for your product team.</p>
<h2>Users feel involved</h2>
<p>Our industry is buzzing about ways to get users more involved in contributing to product documentation by applying their product experience. Give them a voice and a stake in the process. </p>
<p>I completely support this approach. As a user, I rely heavily on active, peer-to-peer forums that not only share troubleshooting information but also &#8220;cool&#8221; tips. I understand how such forums can lessen user frustration and generate user excitement. </p>
<p>If you implement a process to enhance your documentation with user-generated content, don&#8217;t be surprised if the regular contributors comprise a small subset. Many users just want to use the product to get their tasks done. They don&#8217;t want to write the documentation. So even your participating users need to understand that the documentation must motivate, engage, and most importantly, provide answers for <em>all</em> users.</p>
<p>Even when user-generated content becomes part of your process, someone must manage it and ensure that it is accessible and usable. The most effective forums in which I participate have strong leadership.</p>
<h2>Users feel bored</h2>
<p>Regardless of what motivates or scares users away, I believe that our industry overlooks some of the obvious reasons why documentation often sucks. One factor that we ignore is the pervasive, stodgy writing style. </p>
<p>Companies should take a long, hard look at their style standards, or lack thereof. In this day and age of more casual conversation, why not integrate a more conversational tone into your documentation? As a long-time editor of tech docs, I have lobbied for a less formal tone for years, and I&#8217;m a lot older than many of my vibrant young peers. </p>
<p><strong>Examples:</strong></p>
<ul>
<li>We continue to write about how software &#8220;allows&#8221; or &#8220;lets&#8221; users accomplish a task instead of how it <em>enables</em> them. The only contexts for the word <em>allows</em> are access and security. And in a software context, I think that &#8220;lets&#8221; sounds ridiculous.</li>
<li>We write &#8220;If you <em>wish</em> to&#8230;&#8221; before notes and tasks. We&#8217;re afraid to use the stronger and less formal <em>want</em>, or simply the infinitive form: <em>To do x, click y</em>. <em>Wish</em> connotes longing.
<p><strong>Read:</strong> &#8220;When you wish upon a star&#8230;&#8221;</p>
<p> I&#8217;d wager that while using our software, users are <em>longing</em> to finish work and go home. Do you ask friends or colleagues if they <em>wish</em> to go to lunch?</li>
<li>We use <em>may</em> instead of the stronger, more enabling <em>can</em>. This usage sometimes creates confusion about whether we are giving permission or expressing that something <em>might</em> happen (as in <em>maybe</em>).</li>
</ul>
<p>These examples are often defended as &#8220;polite&#8221; usage. I simply believe that they make our words far less engaging and even a bit dull. They create the impression that software is controlling users instead of putting them in the driver&#8217;s seat.</p>
<p>Of course, software documentation isn&#8217;t the only kind of technical writing. Making policies and procedures sound more informal isn&#8217;t easy. Writing about the installation and operation of heavily regulated equipment is a serious business where inaccuracies and mistakes can have serious consequences. But I still believe that even those types of writing can benefit from clear, plain language that sounds more natural. </p>
<p>I&#8217;m not advocating a departure from formal writing, but I believe that we are redefining our definition of what&#8217;s formal. I have often <em>wished</em>&#8212;that is, <em>longed for</em>&#8212;a change, and I welcome it.</p>
<p>But I digress. Plain language is a subject for another post.</p>
<h2>Users feel content</h2>
<p>The rise of social media brings new possibilities and new challenges that are making us rethink how we provide user assistance. Regardless of what we try and what we find effective, we need to remember that what we are delivering is <em>user assistance</em>. The bottom line is, users use our products, read our policies, install, configure, and operate our equipment for one purpose: <em>to get things done</em>.</p>
<p>So when you develop information for users, keep these things in mind: </p>
<ul>
<li>Give them a clear orientation so that they can decide where they want to go.</li>
<li>Stop focusing on the “cool” factor of your product.</li>
<li>Strive to increase the likelihood that they will find what they&#8217;re looking for.</li>
<li>Consider their roles and provide tailored information.</li>
</ul>
<div class="note"><span class="notetext">Remember:</span> Focus on users and their tasks. Help them get their work done.</div>
<p>I welcome your comments and hope that you will share your own solutions for creating a better user experience.</p>
<p><a href="#top">Back to top</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.vanarsdall-infodesign.com/2009/05/31/paving-the-road-to-a-user-utopia/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>You Will Be Assimilated</title>
		<link>http://www.vanarsdall-infodesign.com/2009/05/27/you-will-be-assimilated/</link>
		<comments>http://www.vanarsdall-infodesign.com/2009/05/27/you-will-be-assimilated/#comments</comments>
		<pubDate>Thu, 28 May 2009 04:48:42 +0000</pubDate>
		<dc:creator>Eddie</dc:creator>
				<category><![CDATA[Social Media]]></category>

		<guid isPermaLink="false">http://www.vanarsdall-infodesign.com/?p=2463</guid>
		<description><![CDATA[Having recently seen and enjoyed the 2009 Star Trek movie, I can&#8217;t resist a Borg-inspired title. I&#8217;m no diehard trekkie, but I have seen several of the movies. I also watched the original series as a kid and have infrequently tuned in to some of the other series over the years. Does that make me [...]]]></description>
			<content:encoded><![CDATA[<p></p><a name="top"></a>
<div class="floatleft"><img src="http://www.vanarsdall-infodesign.com/wp-content/uploads/2009/05/borg_bear05_opt-112x150.jpg" alt="Borg Bear" title="Borg Bear" width="112" height="150" /></div>
<p>Having recently seen and enjoyed the 2009 <em>Star Trek</em> movie, I can&#8217;t resist a Borg-inspired title. I&#8217;m no diehard trekkie, but I have seen several of the movies. I also watched the original series as a kid and have infrequently tuned in to some of the other series over the years.</p>
<p>Does that make me a part-time trekkie? The level of trekkiness seems to have a scale based on participation and devotion. My partner has followed all of the series, knows all of the characters, and can explain story lines in technical and historical terms. Yet, he would never dress as a Romulan and go to a trekkie conference. </p>
<p>Social media seems to have a similar scale. Some love it. Some hate it. Some try it and “don&#8217;t get it.” Others approach it with hesitation and later become addicted. </p>
<p>I have friends who say that they would never use Facebook, and later I receive their invitations to connect. Many have stopped sending me email and only contact me in the Facebook space. Others who didn&#8217;t “get” Twitter are now tweeting so much that they&#8217;re sprouting wings.</p>
<p>So where does your level of participation fall on the social media scale? Have you joined the throng? Are you ready to become a publisher?</p>
<p><span id="more-2463"></span></p>
<h2>Becoming a citizen of Content Nation</h2>
<p>In <em>Content Nation: Surviving and Thriving as Social Media Changes Our Work, Our Lives, and Our Future</em>, author <a href="http://www.shore.com/us/team/jblossom.html" title="Link to John Blossom's bio" target="_blank">John Blossom</a> examines how the spreading wildfire of social media has transformed us into a “nation of publishers.” He traces this phenomenon back to its primitive origins, from nomadic tribes to “trade-oriented ownership economies” (p. xvi). Those economies created the need for published materials that began with monuments, scrolls, and primitive books. Subsequent publishing events shaped history and transformed society. Blossom cites Thomas Paine&#8217;s <em>Common Sense</em> and the arrival of the Gutenberg printing press as significant turning points.</p>
<p>The recurrent theme of <em>Content Nation</em> (used as the book title and as a description for the entity that we have become) is that the growth of social media publishing is the unparalleled phenomenon—the one that&#8217;s changing all the rules. This is most evident in the nomadic nature of free-form publishing. We&#8217;re running off in our own directions, tailoring our content to our own needs. Publishing institutions are trying to figure out how to domesticate us.</p>
<p>Most notably, we&#8217;re spreading <em>influence</em> in a way that is transforming the world. Our ability to publish on-demand content challenges news sources, exposes product weaknesses, and even saves lives.</p>
<h2>Following your tribe</h2>
<p>How we use social media can depend on which of the three publishing “tribes” we belong to (p. 60).</p>
<p><em>Personal</em> publishers use social media to gain both personal and professional benefits. If your passion is cooking, you can blog about food and publish recipes. You can start a wiki to collaborate on recipes with other cooking enthusiasts.</p>
<p><em>Media</em> publishers use social media to “market content and online services.” These publishers have traditionally been “manufacturers and distributors of content from centralized plants” (p. 44). Aggregation of content has traditionally been achieved through a layered pyramid structure. But that model has changed. We&#8217;re no longer bound to the layers used to filter and package published content. We can package and mix our own content, aggregating it from our own preferred sources. As consumers of information, this is great for us but challenging for traditional media publishers. Blossom cites <a href="http://www.nytimes.com/" title="Link to New York Times site" target="_blank">The New York Times</a> and <a href="http://www.chron.com/" title="Link to Houston Chronicle site" target="_blank">The Houston Chronicle</a> as examples of newspapers that have risen to the challenge and adapted well.</p>
<p><em>Enterprise</em> publishers use social media to improve communication and promote collaboration. But because many businesses still perceive social media applications as frivolous, their adoption rate has been relatively slow. Those businesses are not ready to flatten the corporate hierarchy by giving everyone a voice. Businesses who want to attract and retain younger workers need to change this perception. Blossom includes several examples of forward-looking enterprises that are developing a social media strategy and integrating tools such as blogs, wikis, and messaging.</p>
<h2>Understanding the new rules of&nbsp;buying&nbsp;and&nbsp;selling</h2>
<p>Becoming a citizen of Content Nation brings both benefits and challenges. It creates new opportunities while requiring that we adapt to new ways of thinking and working. </p>
<p>One of the most significant paradigm shifts is the relationship between buyers and sellers. Buyers have access to a growing number of sites that compare products and prices, enabling them to better discover and understand supply and demand. Blossom points out that this “builds efficient economies that benefit the most people” (p. 97). He cites <a href="http://www.ebay.com/" title="Link to eBay site" target="_blank">eBay</a> and <a href="http://www.craigslist.org/about/sites" title="Link to Craig's List site" target="_blank">Craig&#8217;s List</a> as examples.</p>
<p>Feedback from other buyers is more prevalent than ever. When you shop online, do you read the marketing fluff, or do you go straight to the consumer comments?  Blossom refers to research showing that a clear majority of consumers seek peer advice and are influenced by consumer reviews and ratings. Last year I was minutes away from ordering two office chairs when I paused to read the customer comments more closely. As a result, I ordered different chairs from a different manufacturer and saved several hundred dollars.</p>
<p>Advertising is still prevalent on the web and elsewhere. Viral marketing still exists. But social media brings on a new method of marketing that Blossom calls the <em>Big Sombrero</em> model. In this model,  mass markets give way to more effective small markets, which are based on more direct transactions. An example is the print-on-demand capability of <a href="http://www.lulu.com/?cid=eng_brand_nm&#038;gclid=CPX14oKQ3poCFQQrFQodsFzUzg" title="Link to Lulu site" target="_blank">Lulu.com</a>.</p>
<p>With the prevalence of peer-to-peer advice and more power behind small markets, marketers need to rethink their approach. When joining an online conversation, they need to function as peers to gain the trust of the community. </p>
<h2>Embracing change&#8230;</h2>
<h3>In politics</h3>
<p>Milestones in the evolution of publishing often centered around politics. Newspapers, journals, books, and television all made us more politically aware. Early blogs piggybacked on existing outlets before becoming news sources in their own right. In <em>Content Nation Redefines How Citizens Influence Governments</em>, Blossom impartially covers ways in which social media now plays a major role in politics. Although blogs were influential in the 2004 election, their influence was ubiquitous in 2008. Regardless of how the political tide turns, we can expect that influence to continue.</p>
<h3>In daily life</h3>
<p>The chapter <em>Content Nation Redefines How People Live Their Lives</em> explores the “social” in social media. We create “spaces for common experiences” (p. 201). We organize events. We build communities that promote cultural identity. We reveal our natural tendency toward altruism. As an example, Blossom cites the role of social media in mobilizing disaster relief after the 2004 tsunami in south Asia. </p>
<h3>In education</h3>
<p>For learners, the concept of “just-in-time training” is more crucial than ever. Quoting the author:</p>
<blockquote><p>&#8230;by the time young adults enter adulthood to put their education to use, the world has already changed significantly&#8230; Now, as our problem-solving needs shift from moment to moment, our need for education cannot wait for a book to put everything that we need together.</p></blockquote>
<p>Learning professionals refer to the marriage of social media and education as Learning 2.0. I am very interested in this trend and welcome reader comments.</p>
<h2>Looking toward the future</h2>
<p><em>Content Nation</em> is one of the more richly detailed and analytical books that I have read on social media. Each topic mentioned here is accompanied by a relevant set of social media rules and examples.</p>
<p>I periodically put the book down to ponder the rules, explore the examples, and oh, yes—get some work done. I took a break before reading the last three chapters, and nothing prepared me for their depth. In a way, everything else in the book was simply preparing for the story told in those chapters.</p>
<p>Blossom looks to the past to predict how publishing will play a part in our future. He returns to the subject of altruism—not as an innate abandonment of self-interest, but as a genetic predisposition to preserve our bloodline. This base genetic altruism eventually gave way to a clan-based version based on trade, setting the stage for the evolution of publishing. </p>
<p>To establish a system of trust, we needed contracts, which became a part of our first published content. As publishing became more sophisticated, it also became more centralized, setting the model for the institutions that we know today—the ones that are challenged by social media. With our “giving to get” nature, we are returning to our altruistic roots, this time with more interest in taking care of the earth and spreading global wealth through such online vehicles as microloans. Blossom brings our story full circle, linking our future to our nomadic, herd-chasing origins.</p>
<p>The book closes with glimpses of the future—50, 100, 1,000, and 10,000 years from now. In Blossom&#8217;s visions, what we now refer to as social media is fully integrated into our lives, our work, and in some cases, our chemistry. </p>
<p>I&#8217;ll stop there. Now <a href="http://contentnation.com/wiki/show/Content%20Nation%20-%20The%20Book" title="Link to Content Nation book page" target="_blank">read the book</a>!</p>
<h2>Informing by example</h2>
<p>The <em>Content Nation</em> book is a product of social media publishing. The content was first developed and published through a collaborative wiki on Blossom&#8217;s <a href="http://www.contentnation.com/wiki" title="Link to Content Nation site" target="_blank">Content Nation site</a>.  The “post-print” version continues online, demonstrating that “evolving social media forms use mass media more as a transient form than as a final goal” (p. 55).</p>
<p>The Content Nation site features links to many of the sites that are used as examples in the book. I encourage you to <a href="http://www.contentnation.com/wiki" title="Link to Content Nation site" target="_blank">explore the site and the links</a>.</p>
<h2>Getting ready for the next wave</h2>
<p>How will social media affect you? Why should you care?</p>
<p>You should care because it will affect your life in some way, even if it&#8217;s an indirect way. It&#8217;s not a matter of <em>how</em>, but <em>when</em>.</p>
<p>Just when you least expect it, you <em>will</em> be assimilated.</p>
<p><p><a href="#top">Back to top</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.vanarsdall-infodesign.com/2009/05/27/you-will-be-assimilated/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>
