[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
I'm gradually starting to appreciate Herbert's CIF1.5 idea. In particular, I'm quite keen to start using
lists, even within the apparent confines of CIF1 and regardless of the DDLm use.
It would be a shame if the CIF2 changes were so unpalatable that they hindered introduction
of something that could already be very useful in current CIFs.
However, I look forward to seeing a full description of CIF2 syntax in the hope that it will, after all the
toing and froing, be as elegant and unambiguous as its predecessor.
From: Joe Krahn <krahn@niehs.nih.gov>
To: Group finalising DDLm and associated dictionaries <ddlm-group@iucr.org>
Sent: Tuesday, 1 December, 2009 18:17:22
Subject: Re: [ddlm-group] CIF 1.5
Herbert J. Bernstein wrote:
> Dear Colleagues,
>
> I respectfully disagree. Indeed, I strongly disagree with almost every
> aspect of the recent CIF 2 decisions. However, I have had my say. Let
> us finish the design of something and get it into use.
>
Instead of CIF 1.5, maybe CIF1.1 software can initially use lists stored
as strings? That way, file I/O is still CIF1.1, but you can implement a
CIF2 list parser on the application side to deal with lists. In fact,
that might be a good first step before finalizing CIF2 syntax, to make
sure there are no design flaws in the list syntax.
I also disagree with many of the CIF2 changes. CIF2 seems to be aiming
towards a Python influenced syntax, rather than just keeping with the
original concept of CIF being simple and efficient. Unfortunately, that
is just the way humans work. The important thing is to make sure that
the syntax is precisely defined, so there are no parsing ambiguities.
Joe Krahn
_______________________________________________
ddlm-group mailing list
ddlm-group@iucr.org
http://scripts.iucr.org/mailman/listinfo/ddlm-group
Reply to: [list | sender only]
Re: [ddlm-group] CIF 1.5
- To: Group finalising DDLm and associated dictionaries <ddlm-group@iucr.org>
- Subject: Re: [ddlm-group] CIF 1.5
- From: SIMON WESTRIP <simonwestrip@btinternet.com>
- Date: Wed, 2 Dec 2009 00:50:34 +0000 (GMT)
- In-Reply-To: <4B155DB2.3050007@niehs.nih.gov>
- References: <279aad2a0911301535y3abf9ef2l8f8f31a7e2c9120@mail.gmail.com><alpine.BSF.2.00.0911301907230.1755@epsilon.pair.com><279aad2a0911301930p4ac515e6m5047d276575a5f90@mail.gmail.com><20091201100130.GB20378@emerald.iucr.org><4B15341C.4010801@mcmaster.ca><alpine.BSF.2.00.0912011025210.27482@epsilon.pair.com><4B155DB2.3050007@niehs.nih.gov>
I'm gradually starting to appreciate Herbert's CIF1.5 idea. In particular, I'm quite keen to start using
lists, even within the apparent confines of CIF1 and regardless of the DDLm use.
It would be a shame if the CIF2 changes were so unpalatable that they hindered introduction
of something that could already be very useful in current CIFs.
However, I look forward to seeing a full description of CIF2 syntax in the hope that it will, after all the
toing and froing, be as elegant and unambiguous as its predecessor.
From: Joe Krahn <krahn@niehs.nih.gov>
To: Group finalising DDLm and associated dictionaries <ddlm-group@iucr.org>
Sent: Tuesday, 1 December, 2009 18:17:22
Subject: Re: [ddlm-group] CIF 1.5
Herbert J. Bernstein wrote:
> Dear Colleagues,
>
> I respectfully disagree. Indeed, I strongly disagree with almost every
> aspect of the recent CIF 2 decisions. However, I have had my say. Let
> us finish the design of something and get it into use.
>
Instead of CIF 1.5, maybe CIF1.1 software can initially use lists stored
as strings? That way, file I/O is still CIF1.1, but you can implement a
CIF2 list parser on the application side to deal with lists. In fact,
that might be a good first step before finalizing CIF2 syntax, to make
sure there are no design flaws in the list syntax.
I also disagree with many of the CIF2 changes. CIF2 seems to be aiming
towards a Python influenced syntax, rather than just keeping with the
original concept of CIF being simple and efficient. Unfortunately, that
is just the way humans work. The important thing is to make sure that
the syntax is precisely defined, so there are no parsing ambiguities.
Joe Krahn
_______________________________________________
ddlm-group mailing list
ddlm-group@iucr.org
http://scripts.iucr.org/mailman/listinfo/ddlm-group
_______________________________________________ ddlm-group mailing list ddlm-group@iucr.org http://scripts.iucr.org/mailman/listinfo/ddlm-group
Reply to: [list | sender only]
- Follow-Ups:
- [ddlm-group] CIFtbx 4 testers needed (Herbert J. Bernstein)
- References:
- [ddlm-group] CIF 1.5 (James Hester)
- Re: [ddlm-group] CIF 1.5 (Herbert J. Bernstein)
- Re: [ddlm-group] CIF 1.5 (James Hester)
- Re: [ddlm-group] CIF 1.5 (Brian McMahon)
- Re: [ddlm-group] CIF 1.5 (David Brown)
- Re: [ddlm-group] CIF 1.5 (Herbert J. Bernstein)
- Re: [ddlm-group] CIF 1.5 (Joe Krahn)
- Prev by Date: Re: [ddlm-group] Stakeholders
- Next by Date: Re: [ddlm-group] Space as a list item separator>
- Prev by thread: Re: [ddlm-group] CIF 1.5
- Next by thread: [ddlm-group] CIFtbx 4 testers needed
- Index(es):