Discussion List Archives

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Draft JSON specification for CIF

I'd like to see an actual CIF or mmCIF file turned into JSON by this spec before judging.
But I'm pretty sure this is exactly what Jmol does already.

My first reaction is that "dataname.a" is problematic. The presence of the period demands that ["dataname.a"] syntax be used. And it suggest poor parsing of the data labels. But it might be the  simplest option.

An important aspect it seems to me is how to parse data names that include "." vs. "_". Jmol ignores this difference completely,  partially because mmCIF and CIF seem to differ some on this. (I can't remember what the IUCr spec says on "." vs. "_".)

The CIF file as shown is invalid. I presume there is an implied CIF2 header?

I would recommend REQUIRING a CIF2 header.

Bob Hanson

cif-developers mailing list

Reply to: [list | sender only]
International Union of Crystallography

Scientific Union Member of the International Science Council (admitted 1947). Member of CODATA, the ISC Committee on Data. Partner with UNESCO, the United Nations Educational, Scientific and Cultural Organization in the International Year of Crystallography 2014.

International Science Council Scientific Freedom Policy

The IUCr observes the basic policy of non-discrimination and affirms the right and freedom of scientists to associate in international scientific activity without regard to such factors as ethnic origin, religion, citizenship, language, political stance, gender, sex or age, in accordance with the Statutes of the International Council for Science.