<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Depth-First: Making the Case: OpenSMILES</title>
    <link>http://depth-first.com/articles/2007/11/14/making-the-case-opensmiles</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Walking the Web of Chemical Informatics</description>
    <item>
      <title>Making the Case: OpenSMILES</title>
      <description>&lt;p&gt;&lt;a href="http://www.opensmiles.org/"&gt;&lt;img src="http://depth-first.com/demo/20071114/osmi.png" align="right"&gt;&lt;/img&gt;&lt;/a&gt;&lt;a href="http://www.daylight.com/dayhtml/doc/theory/theory.smiles.html"&gt;SMILES&lt;/a&gt; is one of the most widely-used line notations in cheminformatics. Yet until very recently, there has been no concerted attempt to develop open SMILES encoding standards.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://www.opensmiles.org/"&gt;OpenSMILES&lt;/a&gt; aims to change that. By providing a forum in which concerns from the SMILES user community can be voiced, peer-reviewed, and addressed, OpenSMILES introduces a new way for the SMILES language to become better.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://www.opensmiles.org/spec/open-smiles.html"&gt;A draft OpenSMILES specification&lt;/a&gt; is now available for review. For now, the best way to raise issues and otherwise get involved is through the &lt;a href="https://lists.sourceforge.net/lists/listinfo/blueobelisk-smiles"&gt;OpenSMILES mailing list&lt;/a&gt;.&lt;/p&gt;</description>
      <pubDate>Wed, 14 Nov 2007 09:42:00 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:cf48057b-4988-415c-8d7b-fc13c0347d24</guid>
      <author>Rich Apodaca</author>
      <link>http://depth-first.com/articles/2007/11/14/making-the-case-opensmiles</link>
      <category>Open X</category>
      <category>smiles</category>
      <category>opensmiles</category>
    </item>
    <item>
      <title>"Making the Case: OpenSMILES" by Craig James</title>
      <description>&lt;p&gt;Indeed, Dave Weininger always encouraged the widespread adoption of SMILES, and helped anyone who wanted to write a parser.&lt;/p&gt;

&lt;p&gt;In my book, there are two equal halves to the definition of "open":  First, the specification is available to anyone to use (Daylight's meets that criterion).  And second, all experts in the field can participate on an equal footing in defining and improving the specification; the standard isn't controlled by one person or company.  In other word, "no gatekeeper" as Rich says.&lt;/p&gt;

&lt;p&gt;SMILES is a great invention, a truly brilliant solution to a hard problem in chemistry.  It is simple, elegant, powerful, and easily learned.  By getting the community's participation and expertise, we've given SMILES new momentum and life, solved a few of the lingering ambiguities about the language, but most importantly, we've made it a fully open specification.&lt;/p&gt;</description>
      <pubDate>Fri, 16 Nov 2007 09:45:56 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:1e7e6e4d-a587-4c19-8ea0-cd91c6f58015</guid>
      <link>http://depth-first.com/articles/2007/11/14/making-the-case-opensmiles#comment-254</link>
    </item>
    <item>
      <title>"Making the Case: OpenSMILES" by Rich Apodaca</title>
      <description>&lt;p&gt;True enough. If ever there was a word that could cause confusion, it's "open." I wish I had a better, more descriptive one to use.&lt;/p&gt;

&lt;p&gt;What I meant by "open" was firstly, a spec for which either no intellectual property, even copyright, was asserted - or which those rights were licensed in a way consistent with free use (&lt;a href="http://depth-first.com/articles/2006/09/27/hacking-pubchem-free-speech-or-free-beer" rel="nofollow"&gt;free as in speech&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;And secondly, a spec backed by a community review process where peers would work together to resolve conflicts and establish new directions. In other words... no gatekeeper.&lt;/p&gt;

&lt;p&gt;Just my own $0.02, of course. Come to think of it, I'm not really sure there's been any discussion of what the "Open" in "OpenSMILES" means...&lt;/p&gt;</description>
      <pubDate>Thu, 15 Nov 2007 19:47:05 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:b2401e91-0817-42cb-8469-e4a76fc6f015</guid>
      <link>http://depth-first.com/articles/2007/11/14/making-the-case-opensmiles#comment-251</link>
    </item>
    <item>
      <title>"Making the Case: OpenSMILES" by Andrew Dalke</title>
      <description>&lt;p&gt;To be fair, SMILES was pretty well defined in Weininger's JCICS 1988 paper, and he wrote an updated version of it for the "Handbook of Chemoinformatics" (ed. Gastinger, pub. Wiley).  By most definitions that means it's "open."&lt;/p&gt;

&lt;p&gt;However, they aren't formal in a CS sense, so there's no direct way to parse using standard tools, there are some ambiguities in a few parts, especially regarding aromaticity.&lt;/p&gt;</description>
      <pubDate>Thu, 15 Nov 2007 17:58:48 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:fa3677c7-0987-409e-996e-16f5b39db21c</guid>
      <link>http://depth-first.com/articles/2007/11/14/making-the-case-opensmiles#comment-249</link>
    </item>
  </channel>
</rss>
