[Cif2-encoding] How we wrap this up

[SIMON WESTRIP]

John, I do not think a specification that suggests that a CIF can be invalidated 
simply by being moved to
another environment is helpful to anyone.

Cheers

Simon




________________________________
From: "Bollinger, John C" <John.Bollinger at STJUDE.ORG>
To: Group for discussing encoding and content validation schemes for CIF2 
<cif2-encoding at iucr.org>
Sent: Tuesday, 28 September, 2010 21:56:24
Subject: Re: [Cif2-encoding] How we wrap this up


On Tuesday, September 28, 2010 2:19 PM, SIMON WESTRIP wrote:

> Perhaps it might further your cause to
>present your proposal more completely, and define "text" and "text file" 
>sufficient to program to.
>
>Certainly, although I think I understand your use of "local", I would like to 
>see it presented as part of
>a full specification of CIF encoding so that I might determine more clearly how 
>the concept will be received
>by current CIF users/developers.

Fair enough.  Here are the relevant excerpts of a revised full draft of the CIF2 
Changes document.  I had intended to hold off on this, pending possible adoption 
of the underlying concept, but as long as you asked:

------

TERMINOLOGY
Reference to character(s) means abstract characters assigned code points by 
Unicode.  [...]

Reference to CIF text means a sequence of characters collectively complying with 
the CIF syntax described in this specification.  CIF text is the unparsed 
logical content of a CIF, independent of any mechanism for representing that 
content concretely.

[...]

CHANGE X - REFINEMENT to CIF1
Persistent Form.
[...]
(3) CIF/local
CIF text is serialized according to this form by encoding it via the default 
text conventions for its environment, including not only character encoding 
scheme, but also the newline representation and possibly other details.  The 
specific meaning of "default text conventions" is system-dependent.  They are 
the conventions employed by the system's standard text editors when creating new 
files, the conventions the system's I/O libraries assume for 'formatted' or 
'text' files when not explicitly instructed differently, etc..

------

I am not emotionally tied to that exact wording nor even to all of the details, 
but I would be reasonably satisfied with them if adopted as-is.


Regards,

John
--
John C. Bollinger, Ph.D.
Department of Structural Biology
St. Jude Children's Research Hospital


Email Disclaimer:  www.stjude.org/emaildisclaimer
_______________________________________________
cif2-encoding mailing list
cif2-encoding at iucr.org
http://scripts.iucr.org/mailman/listinfo/cif2-encoding
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://scripts.iucr.org/pipermail/cif2-encoding/attachments/20100929/29deb50d/attachment-0001.html