The cctbx provides comprehensive tools for handling mmcif files (and indeed all types of cif files - it is not fussy), freely available under the BSD-style cctbx licence.
Cheers, Richard On 7 Aug 2013, at 19:16, "Jeffrey, Philip D." <pjeff...@princeton.edu> wrote: > Are all the APIs open source ? I was under the impression that CCP4 had > moved away from that, which might justifiably reduce interest in any > limited-availability API. > > Phil Jeffrey > Princeton > ________________________________________ > From: CCP4 bulletin board [CCP4BB@JISCMAIL.AC.UK] on behalf of James Stroud > [xtald...@gmail.com] > Sent: Wednesday, August 07, 2013 1:51 PM > To: CCP4BB@JISCMAIL.AC.UK > Subject: Re: [ccp4bb] mmCIF as working format? > > On Aug 5, 2013, at 4:33 AM, Eugene Krissinel wrote: >> I just hope that one day we all will be discussing a sort of universal API >> to read/write structural information instead of referencing to raw formats, >> and routines to query MX data, which would be more appropriate than grep >> (would many SB students/postdocs use grep these days? but many if them would >> need to inspect files somehow). This, in essence, is similar to discussing >> read/write primitives in C/C++/Fortran rather than I/O functions of BIOS and >> HDD/BUS commands that they drive. > > I just want to reinforce this point by quoting it verbatim and also emphasize > that it was not lost on some of us. > > In the long term, the MM structure community should perhaps get its > inspiration from SQL, which focuses on the scope of data and the semantics > its manipulation, rather than how the data is encoded beneath the surface. > > James -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
