<div dir="ltr"><div><div><div><div>John B asks what the significance of COMCIFS approval would be. I have perhaps used the word "approval" rather loosely. By "approval" what I mean is that (1) COMCIFS endorses the
standard and (2) COMCIFS agrees to become the custodian of standard, that is, to ensure that it is published, developed and maintained. <br></div></div><br></div><div>A communications standard depends on widespread adoption to be effective. Having a long-term, credible custodian of a standard is important in encouraging adoption, as developers are less inclined to write code for something that is seen as ad-hoc, poorly managed or likely to disappear. <br><br></div><div>Note that I would be expecting COMCIFS to delegate CIF-JSON development and maintenance responsibilities back to the cif-developers group.<br></div><br></div><div>An alternative to full adoption by COMCIFS could be links (or full contents) on IUCr webpages and inclusion in Vol G, with appropriate disclaimers if this seems too much like endorsement.<br><br></div><div>This topic also touches on the questions around what the relationship of COMCIFS should be to work on the periphery of IUCr concerns, e.g. spectroscopy ontologies.<br></div><div><br></div><div>James.<br></div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On 24 May 2017 at 23:06, Bollinger, John C <span dir="ltr"><<a href="mailto:John.Bollinger@stjude.org" target="_blank">John.Bollinger@stjude.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US">
<div class="m_-8040586476653774876WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Dear James and Colleages,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I am satisfied with the current CIF-JSON draft, but I am uncertain what the significance of COMCIFS’s approval would be. Why are we considering this step?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">John<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Courier New";color:#1f497d">--
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Courier New";color:#1f497d">John C. Bollinger, Ph.D.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Courier New";color:#1f497d">Computing and X-Ray Scientist<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Courier New";color:#1f497d">Department of Structural Biology<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Courier New";color:#1f497d">St. Jude Children's Research Hospital<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Courier New";color:#1f497d"><a href="mailto:John.Bollinger@StJude.org" target="_blank">John.Bollinger@StJude.org</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Courier New";color:#1f497d"><a href="tel:(901)%20595-3166" value="+19015953166" target="_blank">(901) 595-3166</a> [office]<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Courier New";color:#1f497d"><a href="http://www.stjude.org/" target="_blank">www.stjude.org</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> comcifs [mailto:<a href="mailto:comcifs-bounces@iucr.org" target="_blank">comcifs-bounces@iucr.<wbr>org</a>]
<b>On Behalf Of </b>James Hester<br>
<b>Sent:</b> Tuesday, May 23, 2017 8:21 PM<br>
<b>To:</b> Discussion list of the IUCr Committee for the Maintenance of the CIF Standard (COMCIFS) <<a href="mailto:comcifs@iucr.org" target="_blank">comcifs@iucr.org</a>><br>
<b>Subject:</b> CIF-JSON draft standard<u></u><u></u></span></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Dear COMCIFS,<u></u><u></u></p>
</div>
<p class="MsoNormal">The cif-developers mailing list has developed a standard for expressing CIF information in JSON form. The resulting draft is available at
<a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcomcifs.github.io%2Fcif-json&data=01%7C01%7CJohn.Bollinger%40stjude.org%7Cfc5e0c10293746b2d08a08d4a2433350%7C22340fa892264871b677d3b3e377af72%7C0&sdata=SjHKghqSXFIZZIkc0%2FkBC26xdE1HZclKjIk7XfVxO%2Bc%3D&reserved=0" target="_blank">
https://comcifs.github.io/cif-<wbr>json</a> .<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">The discussions around the development of this standard are available in the cif-developers archive:
<a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.iucr.org%2Fiucr-top%2Flists%2Fcif-developers%2F&data=01%7C01%7CJohn.Bollinger%40stjude.org%7Cfc5e0c10293746b2d08a08d4a2433350%7C22340fa892264871b677d3b3e377af72%7C0&sdata=vcW4wMyjdzsxT0UL%2FXdbFrWeo0fNXN51jMaBb8Z16kM%3D&reserved=0" target="_blank">
http://www.iucr.org/iucr-top/<wbr>lists/cif-developers/</a><u></u><u></u></p>
</div>
<p class="MsoNormal">If no substantial issues are raised here in the next 6 weeks, this standard will be considered to have been approved by COMCIFS. Any substantial change to the standard will be routed through the cif-developers list (which anybody may join)
before being returned here for final approval. I propose that the approval period is reduced to 3 weeks for any subsequent drafts.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">James Hester (chair)<u></u><u></u></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<p class="MsoNormal">-- <u></u><u></u></p>
<div>
<p class="MsoNormal">T <a href="tel:+61%202%209717%209907" value="+61297179907" target="_blank">+61 (02) 9717 9907</a><br>
F <a href="tel:+61%202%209717%203145" value="+61297173145" target="_blank">+61 (02) 9717 3145</a><br>
M +61 (04) 0249 4148<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div></div></div>
<br>
<hr>
<font color="Gray" face="Arial" size="2"><br>
Email Disclaimer: <a href="http://www.stjude.org/emaildisclaimer" target="_blank">www.stjude.org/emaildisclaimer</a><br>
Consultation Disclaimer: <a href="http://www.stjude.org/consultationdisclaimer" target="_blank">www.stjude.org/<wbr>consultationdisclaimer</a><br>
</font>
</div>
<br>______________________________<wbr>_________________<br>
comcifs mailing list<br>
<a href="mailto:comcifs@iucr.org">comcifs@iucr.org</a><br>
<a href="http://mailman.iucr.org/cgi-bin/mailman/listinfo/comcifs" rel="noreferrer" target="_blank">http://mailman.iucr.org/cgi-<wbr>bin/mailman/listinfo/comcifs</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">T +61 (02) 9717 9907<br>F +61 (02) 9717 3145<br>M +61 (04) 0249 4148</div>
</div>