<?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: Three useful XML schemas in publishing</title>
	<atom:link href="http://blog.threepress.org/2009/11/19/three-useful-xml-schemas-in-publishing/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.threepress.org/2009/11/19/three-useful-xml-schemas-in-publishing/</link>
	<description>Threepress creates software for publishers, educators and authors.</description>
	<lastBuildDate>Fri, 12 Mar 2010 09:22:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Liza Daly</title>
		<link>http://blog.threepress.org/2009/11/19/three-useful-xml-schemas-in-publishing/comment-page-1/#comment-1383</link>
		<dc:creator>Liza Daly</dc:creator>
		<pubDate>Fri, 27 Nov 2009 15:22:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=931#comment-1383</guid>
		<description>Adrienne: You should have no problem with ePub given your background. Good luck!</description>
		<content:encoded><![CDATA[<p>Adrienne: You should have no problem with ePub given your background. Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrienne Adams</title>
		<link>http://blog.threepress.org/2009/11/19/three-useful-xml-schemas-in-publishing/comment-page-1/#comment-1369</link>
		<dc:creator>Adrienne Adams</dc:creator>
		<pubDate>Thu, 26 Nov 2009 02:37:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=931#comment-1369</guid>
		<description>I have just discovered your blog at the end of a full day of researching ebook publishing. I&#039;m a web designer/frontend developer, and am keenly interested in interoperable publishing formats; delighted, as well, to see that some of my expertise with XHTML and CSS can be applied to e-publishing. I look forward to keeping up with your posts and learning more about this subject.</description>
		<content:encoded><![CDATA[<p>I have just discovered your blog at the end of a full day of researching ebook publishing. I&#8217;m a web designer/frontend developer, and am keenly interested in interoperable publishing formats; delighted, as well, to see that some of my expertise with XHTML and CSS can be applied to e-publishing. I look forward to keeping up with your posts and learning more about this subject.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stuart yeates</title>
		<link>http://blog.threepress.org/2009/11/19/three-useful-xml-schemas-in-publishing/comment-page-1/#comment-1277</link>
		<dc:creator>stuart yeates</dc:creator>
		<pubDate>Fri, 20 Nov 2009 20:52:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=931#comment-1277</guid>
		<description>The tool that I wrote for converting our TEI works to ePub (via our website) is at http://wiki.tei-c.org/index.php/Cocoon_epub_Compiler If anyone is seriously interested in using it, poke me and I&#039;ll update it to the latest and greatest version that we&#039;re using in live.</description>
		<content:encoded><![CDATA[<p>The tool that I wrote for converting our TEI works to ePub (via our website) is at <a href="http://wiki.tei-c.org/index.php/Cocoon_epub_Compiler" rel="nofollow">http://wiki.tei-c.org/index.php/Cocoon_epub_Compiler</a> If anyone is seriously interested in using it, poke me and I&#8217;ll update it to the latest and greatest version that we&#8217;re using in live.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: keith</title>
		<link>http://blog.threepress.org/2009/11/19/three-useful-xml-schemas-in-publishing/comment-page-1/#comment-1263</link>
		<dc:creator>keith</dc:creator>
		<pubDate>Thu, 19 Nov 2009 22:42:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=931#comment-1263</guid>
		<description>It may turn out that the XML way of writing HTML5 allows publishers to get a little bit more semantics than they currently get from XHTML 1.0 without sacrificing broad ubiquity.</description>
		<content:encoded><![CDATA[<p>It may turn out that the XML way of writing HTML5 allows publishers to get a little bit more semantics than they currently get from XHTML 1.0 without sacrificing broad ubiquity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: liza</title>
		<link>http://blog.threepress.org/2009/11/19/three-useful-xml-schemas-in-publishing/comment-page-1/#comment-1261</link>
		<dc:creator>liza</dc:creator>
		<pubDate>Thu, 19 Nov 2009 21:22:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=931#comment-1261</guid>
		<description>John: Sure, but there&#039;s no &quot;built-in&quot; way to do that.  Of course it&#039;s totally possible to use class attributes that way, but without a constrained vocabulary, different content producers will do it differently. That&#039;s only bad insofar as it prevents easy interchange.</description>
		<content:encoded><![CDATA[<p>John: Sure, but there&#8217;s no &#8220;built-in&#8221; way to do that.  Of course it&#8217;s totally possible to use class attributes that way, but without a constrained vocabulary, different content producers will do it differently. That&#8217;s only bad insofar as it prevents easy interchange.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Maxwell</title>
		<link>http://blog.threepress.org/2009/11/19/three-useful-xml-schemas-in-publishing/comment-page-1/#comment-1260</link>
		<dc:creator>John Maxwell</dc:creator>
		<pubDate>Thu, 19 Nov 2009 21:19:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=931#comment-1260</guid>
		<description>Of XHTML&#039;s lack of “semantically meaningful elements,” wouldn&#039;t you agree that the  “class” attribute—which is typically used to provide stylesheet hooks—can be usefully employed to denote semantic structures? Any reason why we really shouldn&#039;t be doing that?</description>
		<content:encoded><![CDATA[<p>Of XHTML&#8217;s lack of “semantically meaningful elements,” wouldn&#8217;t you agree that the  “class” attribute—which is typically used to provide stylesheet hooks—can be usefully employed to denote semantic structures? Any reason why we really shouldn&#8217;t be doing that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kaveh Bazargan</title>
		<link>http://blog.threepress.org/2009/11/19/three-useful-xml-schemas-in-publishing/comment-page-1/#comment-1258</link>
		<dc:creator>Kaveh Bazargan</dc:creator>
		<pubDate>Thu, 19 Nov 2009 19:38:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=931#comment-1258</guid>
		<description>Just a quick comment to say how useful these snippets of information are, at least to one person. ;-) I keenly await future posts...</description>
		<content:encoded><![CDATA[<p>Just a quick comment to say how useful these snippets of information are, at least to one person. ;-) I keenly await future posts&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Scott</title>
		<link>http://blog.threepress.org/2009/11/19/three-useful-xml-schemas-in-publishing/comment-page-1/#comment-1257</link>
		<dc:creator>Brad Scott</dc:creator>
		<pubDate>Thu, 19 Nov 2009 17:17:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=931#comment-1257</guid>
		<description>I&#039;ve used all three in my time, but do have a soft spot for TEI, which I have used when designing data for a number of publishers, including the &lt;a href=&quot;http://www.mlahandbook.org/fragment/public_index&quot; rel=&quot;nofollow&quot;&gt;MLA Handbook&lt;/a&gt;, &lt;a href=&quot;http://www.dictionaryofeconomics.com/dictionary&quot; rel=&quot;nofollow&quot;&gt;Palgrave Dictionary of Economics&lt;/a&gt;, and the Statesman&#039;s Yearbook. It&#039;s very flexible and certainly makes it easier to get results more quickly than trying to reinvent the wheel.

Funnily enough I&#039;d only just read the post on the &lt;a href=&quot;http://historycompass.wordpress.com/2009/11/19/new-resources-online/&quot; rel=&quot;nofollow&quot;&gt;History Compass blog&lt;/a&gt; about the &lt;a href=&quot;http://www.english.ox.ac.uk/holinshed/&quot; rel=&quot;nofollow&quot;&gt;Holinshed&lt;/a&gt; site, also using TEI and in particular the &lt;a href=&quot;http://blogs.oucs.ox.ac.uk/jamesc/2009/09/04/tei-comparator/&quot; rel=&quot;nofollow&quot;&gt;Comparator&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve used all three in my time, but do have a soft spot for TEI, which I have used when designing data for a number of publishers, including the <a href="http://www.mlahandbook.org/fragment/public_index" rel="nofollow">MLA Handbook</a>, <a href="http://www.dictionaryofeconomics.com/dictionary" rel="nofollow">Palgrave Dictionary of Economics</a>, and the Statesman&#8217;s Yearbook. It&#8217;s very flexible and certainly makes it easier to get results more quickly than trying to reinvent the wheel.</p>
<p>Funnily enough I&#8217;d only just read the post on the <a href="http://historycompass.wordpress.com/2009/11/19/new-resources-online/" rel="nofollow">History Compass blog</a> about the <a href="http://www.english.ox.ac.uk/holinshed/" rel="nofollow">Holinshed</a> site, also using TEI and in particular the <a href="http://blogs.oucs.ox.ac.uk/jamesc/2009/09/04/tei-comparator/" rel="nofollow">Comparator</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
