You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The IHM file format should use a different suffix than ".cif", I suggest ".ihm". This will allow software that reads this format to easily identify the dictionary in use, distinguishing it from the mmCIF dictionary that covers only atomic models.
The idea of sticking with ".cif" and putting some table in the file that identifies that this is an IHM flavor cif file will make it much harder for software developers to add support for reading this file because essentially all software distinguishes file types by the file suffix, rather than looking inside the file.
I suggest we should call these "integrated hybrid model" or IHM files, not "mmCIF" files when talking about the format. mmCIF is strongly associated with atomic-only resolution models, so that name is very misleading when applied to IHM files.
The text was updated successfully, but these errors were encountered:
While separation of content and format are important considerations adopting naming
conventions, overloading the file name extension to carry both of these details is not path that we would prefer to follow. We would prefer to follow to follow a convention where the file extension
identifies the parsing syntax, and then separately specify the content specification (e.g. supporting dictionary/schema). For example, in file released by PDB in recent years, audit records are provided in the mmCIF files and schema records in PDBML files to identify content specifications.
As a practical alternative to using the file extension to convey content details, we would prefer to
use a combination internal audit records and standard file naming templates to convey this
information. For example, accession-code-ihm.cif ) .
One proposal from last week's Skype meeting was to use the extension .ihm.cif for these files. This allows for packages such as ChimeraX to recognize the files as using the IHM dictionary based purely on the file extension, while at the same time allowing non-IHM software (such as legacy Chimera) to visualize at least the atomic information in the file.
The IHM file format should use a different suffix than ".cif", I suggest ".ihm". This will allow software that reads this format to easily identify the dictionary in use, distinguishing it from the mmCIF dictionary that covers only atomic models.
The idea of sticking with ".cif" and putting some table in the file that identifies that this is an IHM flavor cif file will make it much harder for software developers to add support for reading this file because essentially all software distinguishes file types by the file suffix, rather than looking inside the file.
I suggest we should call these "integrated hybrid model" or IHM files, not "mmCIF" files when talking about the format. mmCIF is strongly associated with atomic-only resolution models, so that name is very misleading when applied to IHM files.
The text was updated successfully, but these errors were encountered: