Request for discussion: dual-version CIF conformance
- To: "Discussion list of the IUCr Committee for the Maintenance of the CIFStandard (COMCIFS) (firstname.lastname@example.org)" <email@example.com>
- Subject: Request for discussion: dual-version CIF conformance
- From: "Bollinger, John C" <John.Bollinger@STJUDE.ORG>
- Date: Tue, 18 Jul 2017 20:15:31 +0000
- Accept-Language: en-US
- authentication-results: iucr.org; dkim=none (message not signed)header.d=none;iucr.org; dmarc=none action=none header.from=STJUDE.ORG;
- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=SJCRH.onmicrosoft.com; s=selector1-stjude-org;h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;bh=z0lLN0Dgh993jakdJxu23o5+X/JnSLRnaiUyRrCM85k=;b=QEBfVw2Qa7cq6pI62JD4mrmJYHqMAI7U7tSxo+PlrmmLGMlHHn06licBHh4TnudMzZGkLBZU0LXUcxmq7G61okVMVCYmKVcpil2jxOYIivwjO+LBTheSfpEm3S6MF8WrfhuGcRkv5kLG6OAWaSBC1Ozj4ErfIsswoK3HEWa8ksw=
- spamdiagnosticmetadata: NSPM
- spamdiagnosticoutput: 1:99
I have lately been scrutinizing the CIF 1.1 specifications in ITvG and carefully considering a variety of unusual cases. One of the less obscure questions I have examined in the course of this process is whether a CIF can simultaneously comply with both CIF 1.1 and CIF 2.0. Up to now I have supposed that CIF 2.0’s requirement for a leading version-identifying comment prevents a file conforming to CIF 2.0 from also conforming to CIF 1.1, but I am having trouble supporting that with the letter of the CIF 1.1 specifications. In particular,
- momentarily disregarding the question of version-identification comments, there is, in fact, a common subset of CIF 1.1 and CIF 2.0 syntaxes on those systems where local text conventions line up with CIF 2.0’s encoding and line-termination requirements.
- CIF 1.1 does not require a version-identification comment to appear at all.
- Although CIF 1.1 defines a format for a version comment that claims conformance with CIF 1.1, it does not specify that files claiming conformance to a different version thereby fail to conform to CIF 1.1.
- In fact, the text seems to suppose that a file may conform to multiple CIF versions, for it remarks that “A CIF may be considered compliant against the most recent version for which it in practice it satisfies all syntactic and content rules […],” and it characterizes the version comment as embodying only a creation-time conformance assertion.
- If it were necessary, a version comment specifying CIF 2.0 could be interpreted as a plain comment in CIF 1.1.
Does anyone want to mount a counterargument? Or am I maybe late to this party?
As a concrete example, consider a machine whose text conventions rely on an ASCII-compatible encoding and use a line feed character as a line terminator (maybe some flavor of Linux). If the following text is recorded on that machine in a file complying with its text conventions, then does the file simultaneously conform with both CIF 1.1 and CIF 2.0?
### end of CIF ###
Note that this is a different question from whether a processor that supports only CIF 1.1 should assume that it can handle such a file.
John C. Bollinger, Ph.D.
Computing and X-Ray Scientist
Department of Structural Biology
St. Jude Children's Research Hospital
(901) 595-3166 [office]
Email Disclaimer: www.stjude.org/emaildisclaimer
Consultation Disclaimer: www.stjude.org/consultationdisclaimer
Reply to: [list | sender only]
- Re: Request for discussion: dual-version CIF conformance (James Hester)
- Prev by Date: Re: CIF-JSON draft standard
- Next by Date: Re: Request for discussion: dual-version CIF conformance
- Prev by thread: Re: COMCIFS open meeting in Hyderabad 25th August 13:05 MR 2.06
- Next by thread: Re: Request for discussion: dual-version CIF conformance