<?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: ChemSpider Structure Images Migrating to RSC Compound Pages</title>
	<atom:link href="http://www.chemspider.com/blog/chemspider-structure-images-migrating-to-rsc-compound-pages.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.chemspider.com/blog/chemspider-structure-images-migrating-to-rsc-compound-pages.html</link>
	<description>Building Community for Chemists</description>
	<lastBuildDate>Tue, 14 May 2013 21:50:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5</generator>
	<item>
		<title>By: Richard Kidd</title>
		<link>http://www.chemspider.com/blog/chemspider-structure-images-migrating-to-rsc-compound-pages.html/comment-page-1#comment-195079</link>
		<dc:creator>Richard Kidd</dc:creator>
		<pubDate>Sun, 31 Jan 2010 18:10:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.chemspider.com/blog/?p=1551#comment-195079</guid>
		<description><![CDATA[Good point Egon. We use the non-standard InChI internally for Prospect markup as some of the additional options are useful. However, we didn&#039;t think it was worth it to make a short-term fix to sort out our internal Prospect compound database to display the 1S/, when this database is being migrated into ChemSpider and our new MarkLogic-based publishing platform. As ever (hands up here), &#039;short-term&#039; became a bit longer than we expected. It&#039;ll be sorted out in the next few months as we reengineer our publishing processes, and in the meantime we&#039;ll happily supply a standard InChI to anyone who writes in on a postcard ;-)]]></description>
		<content:encoded><![CDATA[<p>Good point Egon. We use the non-standard InChI internally for Prospect markup as some of the additional options are useful. However, we didn&#8217;t think it was worth it to make a short-term fix to sort out our internal Prospect compound database to display the 1S/, when this database is being migrated into ChemSpider and our new MarkLogic-based publishing platform. As ever (hands up here), &#8216;short-term&#8217; became a bit longer than we expected. It&#8217;ll be sorted out in the next few months as we reengineer our publishing processes, and in the meantime we&#8217;ll happily supply a standard InChI to anyone who writes in on a postcard <img src='http://www.chemspider.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Egon Willighagen</title>
		<link>http://www.chemspider.com/blog/chemspider-structure-images-migrating-to-rsc-compound-pages.html/comment-page-1#comment-195078</link>
		<dc:creator>Egon Willighagen</dc:creator>
		<pubDate>Sun, 31 Jan 2010 09:46:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.chemspider.com/blog/?p=1551#comment-195078</guid>
		<description><![CDATA[I see that the info box shows the InChI=1/, and not the InChI=1S/ ... why is that? Any particular reason why the InChI=1/ should still be supported?]]></description>
		<content:encoded><![CDATA[<p>I see that the info box shows the InChI=1/, and not the InChI=1S/ &#8230; why is that? Any particular reason why the InChI=1/ should still be supported?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
