[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
I would agree that this distills the essence of our discussion. The two polar positions are then:
(a) Reliable transfer and archiving of information are the top priority
(b) Being able to process CIF using text conventions is the top priority
If we consider CIF as text as the overriding priority:
1. How do we then make exchanging and storing files according to text conventions sufficiently reliable for the purposes of CIF? How far are we prepared to compromise?
If we consider reliable exchange of information as the top priority:
2. How do we then make CIFs sufficiently accessible to text-based tools? How far are we prepared to compromise?
It would be useful if we came up with suitable answers to (1) and (2) to clarify what are alternatives are. We can then seek a compromise after finding a balance between the loss of textual convenience from emphasizing reliability with the loss of reliability gained by textual convenience (Simple!). I will be proposing a poll of the international CIF using community in a separate email to aid us in our deliberations.
Being clearly in the camp that values reliability before text, I propose the following scheme as a scheme for ensuring reliability while attempting to keep the file as accessible as possible to text tools, and invite others to propose a scheme that satisfies those that value text as the highest priority:
Scheme A:
--
T +61 (02) 9717 9907
F +61 (02) 9717 3145
M +61 (04) 0249 4148
Reply to: [list | sender only]
Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .. .... .. .. .. .. .
- To: Group finalising DDLm and associated dictionaries <ddlm-group@iucr.org>
- Subject: Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .. .... .. .. .. .. .
- From: James Hester <jamesrhester@gmail.com>
- Date: Thu, 1 Jul 2010 14:25:17 +1000
- In-Reply-To: <8F77913624F7524AACD2A92EAF3BFA541661229533@SJMEMXMBS11.stjude.sjcrh.local>
- References: <AANLkTilyJE2mCxprlBYaSkysu1OBjY7otWrXDWm3oOT9@mail.gmail.com><AANLkTikih0j6-vyLDPMOqcTkoiK545yE28y4fU9JTUa2@mail.gmail.com><20100623103310.GD15883@emerald.iucr.org><alpine.BSF.2.00.1006231033360.56372@epsilon.pair.com><alpine.BSF.2.00.1006231406010.30894@epsilon.pair.com><a06240802c848414681ef@192.168.2.104><381469.52475.qm@web87004.mail.ird.yahoo.com><a06240801c84949b70cb7@192.168.27.100><AANLkTilZj2UEffRwmvCrgnVbxrGwmsoqb9S7tw31MWSo@mail.gmail.com><984921.99613.qm@web87011.mail.ird.yahoo.com><AANLkTimLmnpS-HHP9en-zwUDeVKtbHSUJa36tUCOlQtL@mail.gmail.com><826180.50656.qm@web87010.mail.ird.yahoo.com><563298.52532.qm@web87005.mail.ird.yahoo.com><520427.68014.qm@web87001.mail.ird.yahoo.com><a06240800c84ac1b696bf@192.168.2.104><614241.93385.qm@web87016.mail.ird.yahoo.com><alpine.BSF.2.00.1006251827270.70846@epsilon.pair.com><8F77913624F7524AACD2A92EAF3BFA54166122952D@SJMEMXMBS11.stjude.sjcrh.local><33483.93964.qm@web87012.mail.ird.yahoo.com><8F77913624F7524AACD2A92EAF3BFA541661229533@SJMEMXMBS11.stjude.sjcrh.local>
[edit]
As part of extending the character set beyond ASCII, we abandon the premise that CIF is a text format, though under some circumstances it may still be possible to manipulate CIFs with tools designed for text.
Alternatively, I have been advocating essentially this: by extending the character set beyond ASCII, we magnify the importance of exchanging and storing CIFs according to text conventions, including correctly communicating encodings as necessary and transcoding as appropriate.
Alternatively, I have been advocating essentially this: by extending the character set beyond ASCII, we magnify the importance of exchanging and storing CIFs according to text conventions, including correctly communicating encodings as necessary and transcoding as appropriate.
I would agree that this distills the essence of our discussion. The two polar positions are then:
(a) Reliable transfer and archiving of information are the top priority
(b) Being able to process CIF using text conventions is the top priority
If we consider CIF as text as the overriding priority:
1. How do we then make exchanging and storing files according to text conventions sufficiently reliable for the purposes of CIF? How far are we prepared to compromise?
If we consider reliable exchange of information as the top priority:
2. How do we then make CIFs sufficiently accessible to text-based tools? How far are we prepared to compromise?
It would be useful if we came up with suitable answers to (1) and (2) to clarify what are alternatives are. We can then seek a compromise after finding a balance between the loss of textual convenience from emphasizing reliability with the loss of reliability gained by textual convenience (Simple!). I will be proposing a poll of the international CIF using community in a separate email to aid us in our deliberations.
Being clearly in the camp that values reliability before text, I propose the following scheme as a scheme for ensuring reliability while attempting to keep the file as accessible as possible to text tools, and invite others to propose a scheme that satisfies those that value text as the highest priority:
Scheme A:
- For the purposes of storage and transfer, CIF files must be treated by all file handling protocols as streams of bytes.
- Any encoding specifying the mapping from bytes to Unicode code points may be used, provided that:
- The encoding is specified in an international standard
- The encoding is distinguishable from all other standard encodings at the binary level. This requirement may be satisfied by an initial 'signature', provided that this signature is specified in the relevant international standard as being mandatory
- The encoding is supported across the range of platforms likely to use CIF2. "Support" includes:
- Availability of text input and output functions using this encoding across a range of programming languages
- Availability of applications on the platform to manipulate text in this encoding, most importantly text editors but also tools such as search
- The encoding is coincident with US-ASCII for codepoints <= 127. This requirement may be dropped in the future if CIF2 becomes the dominant form of CIF file.
--
T +61 (02) 9717 9907
F +61 (02) 9717 3145
M +61 (04) 0249 4148
_______________________________________________ ddlm-group mailing list ddlm-group@iucr.org http://scripts.iucr.org/mailman/listinfo/ddlm-group
Reply to: [list | sender only]
- Follow-Ups:
- References:
- Re: [ddlm-group] options/text vs binary/end-of-line. .. . (James Hester)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. . (James Hester)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. . (Brian McMahon)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. . (Herbert J. Bernstein)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .. . (Herbert J. Bernstein)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .. .... . (SIMON WESTRIP)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .. .... .. . (James Hester)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .. .... .. . (SIMON WESTRIP)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .. .... .. . (James Hester)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .. .... .. . (SIMON WESTRIP)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .. .... .. . (SIMON WESTRIP)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .. .... .. .. . (SIMON WESTRIP)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .. .... .. .. . (SIMON WESTRIP)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .. .... .. .. . (Herbert J. Bernstein)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .... .. .. .. .. . (Bollinger, John C)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .. .... .. .. .. . (SIMON WESTRIP)
- Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .... .. .. .. .. .. . (Bollinger, John C)
- Prev by Date: Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .. .... .. .. .. .. .
- Next by Date: [ddlm-group] Community consulation regarding CIF2 encoding
- Prev by thread: Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .. .... .. .. .. .. .
- Next by thread: Re: [ddlm-group] options/text vs binary/end-of-line. .. .. .. .... .. .. .. .. .. .. .
- Index(es):