[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
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: "Bollinger, John C" <John.Bollinger@xxxxxxxxxx>
- Date: Wed, 29 Sep 2010 10:28:04 -0500
- Accept-Language: en-US
- acceptlanguage: en-US
- In-Reply-To: <20100929102536.GB24670@emerald.iucr.org>
- References: <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><alpine.BSF.2.00.1009281501030.93180@epsilon.pair.com><8F77913624F7524AACD2A92EAF3BFA5416659DEDE9@SJMEMXMBS11.stjude.sjcrh.local><a06240801c8c840b90dc7@[192.168.2.104]><20100929102536.GB24670@emerald.iucr.org>
This is perhaps irrelevant if James's compromise gains as much traction as it seems poised to do, but On Wednesday, September 29, 2010 5:26 AM, Brian McMahon wrote: [...] >In the real world, a need may arise to exchange CIFs constructed in >non-canonical encodings. ("Canonical" probably means UTF-8 and/or >UTF-16). Such a need would involve some transcoding strategy. > >What is the actual likelihood of that need arising? > >I would characterise James's position as "not very, and even less >if the software written to generate CIFs is constrained to use >canonical encodings within the standard". > >I would characterise the position of the rest of us as "reasonable to >high, so that we wish to formulate the standard in a way that >recognises non-canonical encodings and helps to establish or at >least inform appropriate transcoding strategies". I was about to deny that as a valid characterization of my position, but after some consideration I realized that it does cover me. Good wordsmithing. My divergence from the pack is probably over the mechanism by which I suppose CIFs must be exchanged. I view CIFs constructed via most encodings as inherently unsuitable for exchange, at least if they contain non-ASCII characters. Hence, the needed transcoding strategy (absent some established agreement otherwise) must be for the originator of the exchange to first transcode into a canonical encoding. From there springs my continued advocacy for options that in fact provide a canonical encoding. >There appear to be >strong disagreements among us, but in fact there's a lot of common >ground, and a drafting exercise would probably move us towards a >consensus. > >Do you agree that that is a fair assessment? Yes. >If so, we can analyse further: what are the implications of mandating >a canonical encoding or not if judgement (a) is wrong and if judgement >(b) is wrong? My feeling is that the world will not end - or even >change very much - in any case; but it could determine whether we >need to formulate an optimal transcoding strategy now, or can defer >it to a later date. > >However, if anyone thinks this is just another diversion, I'll drop >this line of approach so as not to slow things down even more. This may be a useful avenue to pursue, but I suggest we table it pending the response to James's compromise proposal. 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]
- References:
- 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 (Herbert J. Bernstein)
- 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 (Brian McMahon)
- Prev by Date: Re: [Cif2-encoding] A new(?) compromise position
- Next by Date: Re: [Cif2-encoding] A new(?) compromise position
- Prev by thread: Re: [Cif2-encoding] Revised Motion
- Next by thread: Re: [Cif2-encoding] How we wrap this up
- Index(es):