[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
From: "Bollinger, John C" <John.Bollinger@STJUDE.ORG>
To: Group for discussing encoding and content validation schemes for CIF2 <cif2-encoding@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@iucr.org
http://scripts.iucr.org/mailman/listinfo/cif2-encoding
Reply to: [list | sender only]
Re: [Cif2-encoding] How we wrap this up
- To: Group for discussing encoding and content validation schemes for CIF2 <cif2-encoding@xxxxxxxx>
- Subject: Re: [Cif2-encoding] How we wrap this up
- From: SIMON WESTRIP <simonwestrip@xxxxxxxxxxxxxx>
- Date: Wed, 29 Sep 2010 07:17:01 +0000 (GMT)
- In-Reply-To: <8F77913624F7524AACD2A92EAF3BFA5416659DEDE8@SJMEMXMBS11.stjude.sjcrh.local>
- References: <AANLkTi=hmKNFMgaeMqt69=sG6dOmxZRUrffB1khjF+mZ@mail.gmail.com><526633.3484.qm@web87004.mail.ird.yahoo.com><alpine.BSF.2.00.1009240742480.8859@epsilon.pair.com><613218.81205.qm@web87011.mail.ird.yahoo.com><281388.90819.qm@web87012.mail.ird.yahoo.com><463665.7127.qm@web87004.mail.ird.yahoo.com><alpine.BSF.2.00.1009251413550.93269@epsilon.pair.com><262880.46378.qm@web87002.mail.ird.yahoo.com><alpine.BSF.2.00.1009251537250.57408@epsilon.pair.com><a06240800c8c5653f38cf@192.168.2.104><476110.27334.qm@web87005.mail.ird.yahoo.com><a06240805c8c6224b8789@192.168.2.104><a06240803c8c65f78a402@149.72.2.199><8F77913624F7524AACD2A92EAF3BFA5416659DEDE3@SJMEMXMBS11.stjude.sjcrh.local><alpine.BSF.2.00.1009271801070.86201@epsilon.pair.com><alpine.BSF.2.00.1009271900080.86201@epsilon.pair.com><AANLkTikudiXBk7orHSAH=JonoeQHeNXVrzvAZmH3Wt94@mail.gmail.com><646265.82162.qm@web87004.mail.ird.yahoo.com><8F77913624F7524AACD2A92EAF3BFA5416659DEDE7@SJMEMXMBS11.stjude.sjcrh.local> <310698.3619.qm@web87010.mail.ird.yahoo.com><8F77913624F7524AACD2A92EAF3BFA5416659DEDE8@SJMEMXMBS11.stjude.sjcrh.local>
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
another environment is helpful to anyone.
Cheers
Simon
From: "Bollinger, John C" <John.Bollinger@STJUDE.ORG>
To: Group for discussing encoding and content validation schemes for CIF2 <cif2-encoding@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@iucr.org
http://scripts.iucr.org/mailman/listinfo/cif2-encoding
_______________________________________________ cif2-encoding mailing list cif2-encoding@iucr.org http://scripts.iucr.org/mailman/listinfo/cif2-encoding
Reply to: [list | sender only]
- Follow-Ups:
- Re: [Cif2-encoding] How we wrap this up (Bollinger, John C)
- References:
- [Cif2-encoding] How we wrap this up (James Hester)
- Re: [Cif2-encoding] How we wrap this up (SIMON WESTRIP)
- Re: [Cif2-encoding] How we wrap this up (Herbert J. Bernstein)
- Re: [Cif2-encoding] How we wrap this up (SIMON WESTRIP)
- Re: [Cif2-encoding] How we wrap this up (SIMON WESTRIP)
- Re: [Cif2-encoding] How we wrap this up (SIMON WESTRIP)
- Re: [Cif2-encoding] How we wrap this up (Herbert J. Bernstein)
- Re: [Cif2-encoding] How we wrap this up (SIMON WESTRIP)
- Re: [Cif2-encoding] How we wrap this up (Herbert J. Bernstein)
- Re: [Cif2-encoding] How we wrap this up (SIMON WESTRIP)
- Re: [Cif2-encoding] How we wrap this up (Bollinger, John C)
- Re: [Cif2-encoding] How we wrap this up (Herbert J. Bernstein)
- Re: [Cif2-encoding] How we wrap this up (Herbert J. Bernstein)
- Re: [Cif2-encoding] How we wrap this up (James Hester)
- Re: [Cif2-encoding] How we wrap this up (SIMON WESTRIP)
- Re: [Cif2-encoding] How we wrap this up (Bollinger, John C)
- Re: [Cif2-encoding] How we wrap this up (SIMON WESTRIP)
- Re: [Cif2-encoding] How we wrap this up (Bollinger, John C)
- Prev by Date: [Cif2-encoding] Addressing Simon's concerns
- Next by Date: Re: [Cif2-encoding] Addressing Simon's concerns
- Prev by thread: Re: [Cif2-encoding] How we wrap this up
- Next by thread: Re: [Cif2-encoding] How we wrap this up
- Index(es):