I agree with what you have said before, Miguel, that if you start reading "bogus" CIF files, you are starting down into a deep dark hole.

I vote to not support invalid CIF files.

Some documentation on our site that we could point users to in defense of this position would be a nice compromise. If it's just the inclusion of "data_" for example at the top of a file, users can figure out how to insert that prior to their naughty program getting upgraded.


Miguel wrote:

I think

http://www.iucr.org/iucr-top/cif/spec/version1.1/cifsyntax.html#syntax

is pretty clear on this (data_ required):


Q: What should our stance be on the support of invalid .cif files?

Q: The iucr wants people to refuse to read them in order to encourage
companies to be compliant ... should we support their position?


Miguel





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&opĚk
_______________________________________________
Jmol-developers mailing list
Jmol-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-developers

--

Robert M. Hanson, [EMAIL PROTECTED], 507-646-3107
Professor of Chemistry, St. Olaf College
1520 St. Olaf Ave., Northfield, MN 55057
mailto:[EMAIL PROTECTED]
http://www.stolaf.edu/people/hansonr

"Imagination is more important than knowledge."  - Albert Einstein


------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Jmol-developers mailing list Jmol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-developers

Reply via email to