<?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: Reimagining the Book Publishing World With XML</title>
	<atom:link href="http://thecontentwrangler.com/2010/02/01/reimagining-the-book-publishing-world-with-xml/feed/" rel="self" type="application/rss+xml" />
	<link>http://thecontentwrangler.com/2010/02/01/reimagining-the-book-publishing-world-with-xml/</link>
	<description>Content is a business asset worthy of being managed</description>
	<lastBuildDate>Fri, 18 May 2012 01:51:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mike McNamara</title>
		<link>http://thecontentwrangler.com/2010/02/01/reimagining-the-book-publishing-world-with-xml/comment-page-1/#comment-652</link>
		<dc:creator>Mike McNamara</dc:creator>
		<pubDate>Tue, 02 Feb 2010 22:44:21 +0000</pubDate>
		<guid isPermaLink="false">http://thecontentwrangler.com/?p=3859#comment-652</guid>
		<description>Good original article and it can only help again in getting the message out of the benefits of keeping your data in XML separate from any formatting so that you&#039;re prepared to produce anything in any format at any time!!

My current list of projects all have XML involved either right at the front end in Editorial or the processing XML from somewhere else and formatting it to eBooks and/or other formats.</description>
		<content:encoded><![CDATA[<p>Good original article and it can only help again in getting the message out of the benefits of keeping your data in XML separate from any formatting so that you&#8217;re prepared to produce anything in any format at any time!!</p>
<p>My current list of projects all have XML involved either right at the front end in Editorial or the processing XML from somewhere else and formatting it to eBooks and/or other formats.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://thecontentwrangler.com/2010/02/01/reimagining-the-book-publishing-world-with-xml/comment-page-1/#comment-651</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Tue, 02 Feb 2010 21:11:56 +0000</pubDate>
		<guid isPermaLink="false">http://thecontentwrangler.com/?p=3859#comment-651</guid>
		<description>&lt;blockquote&gt;For instance, innovative new authoring tools enable content to be created in XML using interfaces indistinguishable from Microsoft Word.&lt;/blockquote&gt;

Does the interface even have to be that complex? For certain types of books, probably not. A while back, I &lt;a href=&quot;http://www.dmncommunications.com/weblog/?p=834&quot; rel=&quot;nofollow&quot;&gt;mused&lt;/a&gt; about using an application with a very constrained interface and constrained templates to create documents using XML.

Obviously, this sort of solution won&#039;t work for every type of book or document. And writers will need to get over the fact that the editor isn&#039;t Word (or their favourite word processor) and doesn&#039;t work like it.</description>
		<content:encoded><![CDATA[<blockquote><p>For instance, innovative new authoring tools enable content to be created in XML using interfaces indistinguishable from Microsoft Word.</p></blockquote>
<p>Does the interface even have to be that complex? For certain types of books, probably not. A while back, I <a href="http://www.dmncommunications.com/weblog/?p=834" rel="nofollow">mused</a> about using an application with a very constrained interface and constrained templates to create documents using XML.</p>
<p>Obviously, this sort of solution won&#8217;t work for every type of book or document. And writers will need to get over the fact that the editor isn&#8217;t Word (or their favourite word processor) and doesn&#8217;t work like it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

