I just noticed that the cif_core.dic file in the GitHub tag (https://github.com/COMCIFS/cif_core/blob/3.2.0/cif_core.dic) and on the IUCr website (https://www.iucr.org/__data/iucr/cif/dictionaries/cif_core_3.2.0.dic) are slightly different. The main difference lies in the addition of a dictionary DOI, the changing of import URLs from local ones to global ones (resolvable URLs instead of file names) and a minor change in date changes.
I wonder, would it be possible to somehow update the release process so that corresponding files in these two locations are identical. I do understand that there might be some chicken-and-egg problems involved here (e.g. can a DOI for a URL be coined before that URL points to a dictionary?). However, I imagine that most of these changes could be done semi-automatically in the release branches.
The benefits of this would be that the files would be byte-by-byte identical and the dictionary would undergo out usual testing procedures before the release. For example, while this is in no sense a breaking change, the dictionary update date and the date of the last _dictionary_audit.revision entry on the IUCr website do not match.
I just noticed that the
cif_core.dicfile in the GitHub tag (https://github.com/COMCIFS/cif_core/blob/3.2.0/cif_core.dic) and on the IUCr website (https://www.iucr.org/__data/iucr/cif/dictionaries/cif_core_3.2.0.dic) are slightly different. The main difference lies in the addition of a dictionary DOI, the changing of import URLs from local ones to global ones (resolvable URLs instead of file names) and a minor change in date changes.I wonder, would it be possible to somehow update the release process so that corresponding files in these two locations are identical. I do understand that there might be some chicken-and-egg problems involved here (e.g. can a DOI for a URL be coined before that URL points to a dictionary?). However, I imagine that most of these changes could be done semi-automatically in the release branches.
The benefits of this would be that the files would be byte-by-byte identical and the dictionary would undergo out usual testing procedures before the release. For example, while this is in no sense a breaking change, the dictionary update date and the date of the last
_dictionary_audit.revisionentry on the IUCr website do not match.