<?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: XML Documentation of Dialplan Applications and Functions</title>
	<atom:link href="http://www.russellbryant.net/blog/2008/10/29/xml-documentation-of-dialplan-applications-and-functions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.russellbryant.net/blog/2008/10/29/xml-documentation-of-dialplan-applications-and-functions/</link>
	<description>Asterisk Open Source Software Engineering</description>
	<lastBuildDate>Wed, 17 Feb 2010 15:24:56 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chuck Wagner</title>
		<link>http://www.russellbryant.net/blog/2008/10/29/xml-documentation-of-dialplan-applications-and-functions/comment-page-1/#comment-771</link>
		<dc:creator>Chuck Wagner</dc:creator>
		<pubDate>Mon, 08 Dec 2008 00:10:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.russellbryant.net/blog/?p=157#comment-771</guid>
		<description>A suggestion - I&#039;m working on a similar project for an api provided by our product to our partners.  I found that XML imposed such a high readability barrier that actually writing documentation was problematic.  We&#039;ve switched to YAML instead, and it&#039;s turned out to be much more effective. (And simple, since we can even embed XML fragments in the documentation without any special escaping.)</description>
		<content:encoded><![CDATA[<p>A suggestion &#8211; I&#8217;m working on a similar project for an api provided by our product to our partners.  I found that XML imposed such a high readability barrier that actually writing documentation was problematic.  We&#8217;ve switched to YAML instead, and it&#8217;s turned out to be much more effective. (And simple, since we can even embed XML fragments in the documentation without any special escaping.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
