RE: Treatment of Greek characters in CIF2
- Subject: RE: Treatment of Greek characters in CIF2
- From: "Bollinger, John C" <John.Bollinger@xxxxxxxxxx>
- Date: Thu, 20 Apr 2017 14:10:13 +0000
- Accept-Language: en-US
- authentication-results: iucr.org; dkim=none (message not signed)header.d=none;iucr.org; dmarc=none action=none header.from=STJUDE.ORG;
- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=SJCRH.onmicrosoft.com; s=selector1-stjude-org;h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;bh=9mfuJNmIXqdHfsE14fahrbdrhCvlmoDhLrpavQWpmgw=;b=Ek/jNTackNFDgqRpD/iF/wT9liONvmzEm9yxwfcYpHCHzSsRvgv5NLqxfHNmTRqoogJ1u24gEia66U1CD6bP+N0YVhn1QNc/pQxvsYZyWVZ9zXPxuaG47Hexwdp7b2DM06jwSo7r0NWG7Eiy09KOo0pO1kDTXHAY6HicV0BzV9Q=
- In-Reply-To: <CAF_YUvX+3ptR1e18wCqH3BKQ9A2=B90mVQ8MVtXePzpKa2=Vbg@mail.gmail.com>
- References: <CAM+dB2d5NCbCb1Zc_QS3KkjscDH7Sk9NQVbQxhLn0nPtO6E+zA@mail.gmail.com><MWHPR04MB0512FE67D8266ED57567F119E01B0@MWHPR04MB0512.namprd04.prod.outlook.com><CAF_YUvX+3ptR1e18wCqH3BKQ9A2=B90mVQ8MVtXePzpKa2=Vbg@mail.gmail.com>
- spamdiagnosticmetadata: NSPM
- spamdiagnosticoutput: 1:99
I’m all for using CIF2 over CIF1 where we can, and I favor recommending that software authors recognize and correctly handle CIF2. But as long as there exists
software that we want to use but that doesn’t handle CIF2, we do need some way to deal with that. What I meant to convey in in my previous message is that I don’t think we need or want to formulate additional, centralized rules for interoperation purposes.
Doing so presents a semantic problem, and it doesn’t really solve the problem of producing CIF1 data in a form that any specific program will interpret as desired. John From: cif-developers [mailto:cif-developers-bounces@iucr.org]
On Behalf Of Robert Hanson I strongly recommend that all non-CIF2 data be transformed into CIF2 format. We have an opportunity to help with CIF1 -> CIF2 transition via CIF1 -> CIF2-JSON -> CIF2 even. The METADATA should reflect that this
was done. Let's be progressive, not regressive. If need be, software can revert that to CIF1. Is Brian McMahon listening? If so, Brian, can you chime in here? Bob On Thu, Apr 20, 2017 at 8:42 AM, Bollinger, John C <John.Bollinger@stjude.org> wrote:
Robert M. Hanson |
_______________________________________________ cif-developers mailing list cif-developers@iucr.org http://mailman.iucr.org/cgi-bin/mailman/listinfo/cif-developers
Reply to: [list | sender only]
- Follow-Ups:
- Re: Treatment of Greek characters in CIF2 (Robert Hanson)
- References:
- Treatment of Greek characters in CIF2 (James Hester)
- RE: Treatment of Greek characters in CIF2 (Bollinger, John C)
- Re: Treatment of Greek characters in CIF2 (Robert Hanson)
- Prev by Date: Re: Draft JSON specification, round 2
- Next by Date: Re: Treatment of Greek characters in CIF2
- Prev by thread: Re: Treatment of Greek characters in CIF2
- Next by thread: Re: Treatment of Greek characters in CIF2
- Index(es):