[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
--
Reply to: [list | sender only]
Re: Treatment of Greek characters in CIF2
- Subject: Re: Treatment of Greek characters in CIF2
- From: James Hester <jamesrhester@xxxxxxxxx>
- Date: Fri, 21 Apr 2017 16:07:00 +1000
- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;h=mime-version:in-reply-to:references:from:date:message-id:subject:to;bh=S7WMfvJZbPfXtfSzKMKx4KrCaHV/cYPAcb3xSmGmljo=;b=lXGC+jmQm1mk/2N8shW06KbkeNPgjDSe9dXEHErGYc0Eur6MJv2URTE42OwH+/26JF89KRTD5IZvLKhYNxY4aW6Ah1AYMonXvpKDPfTeDxhMLn0Hm7Cem4G8Ly1SS2mk9OquDUEAs/iCJvj6a6zdzMrKF9C5MEiKeZxOPv2fIGCkA04I1ezdXae9tuxzrcVewOW6Pz0OL89Xxy/yHAzs/gPD0NoFqhc71wcsyZoCAlv2kAUXtO28kiry3tMYwDvNiqnPlsiqasy+ddkXjXSWw944YFZTHH60HulvfmDal7h6AGfCAvKbjYCFfd9mzm4af2/X82BOZ2uFFIj5eskyLQ==
- In-Reply-To: <CAF_YUvWUOYXL0Ek4dq=ZYp-J5PVyMv2m9voKUitsDZjtnLyWTA@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><MWHPR04MB0512EC6E2F22307C756FC31FE01B0@MWHPR04MB0512.namprd04.prod.outlook.com><CAF_YUvWUOYXL0Ek4dq=ZYp-J5PVyMv2m9voKUitsDZjtnLyWTA@mail.gmail.com>
I am also in agreement with Bob's list, with John's subsequent clarifications. I am also not convinced that there is a need to preserve duplicate datablock names and datablock order.
On 21 April 2017 at 00:25, Robert Hanson <hansonr@stolaf.edu> wrote:
and this also allows us to- as long as we don't cause an incompatibility, we can do whatever we want- no programs as of yet are implementing CIF-JSON, including COD and Jmol- we're talking about the future, not the present- Jmol is already creating something like this for internal use or export (undocumented)- COD is already using something like thisNow that John is with us, let's summarize where we are. Feel free to disagree!- CIF-JSON is a great ideaAgreed to so far - maybe?- all CIF keys will be made lower case, since in the CIF format it doesn't matter, and in JSON it does- upper-case keys will be non-CIF metadata or other application-specific or translation-specific keys,including CIF1/2 compatibility information- UTF-8 character encoding; \uFFFF for CIF <?> and JSON standard null for <.>- some question about whether top level should be [] or {}- some question about what to do with CIF1 non-latin characters
?Bob
_______________________________________________
cif-developers mailing list
cif-developers@iucr.org
http://mailman.iucr.org/cgi-bin/mailman/listinfo/cif- developers
--
T +61 (02) 9717 9907
F +61 (02) 9717 3145
M +61 (04) 0249 4148
F +61 (02) 9717 3145
M +61 (04) 0249 4148
_______________________________________________ cif-developers mailing list cif-developers@iucr.org http://mailman.iucr.org/cgi-bin/mailman/listinfo/cif-developers
Reply to: [list | sender only]
- 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)
- RE: Treatment of Greek characters in CIF2 (Bollinger, John C)
- Re: Treatment of Greek characters in CIF2 (Robert Hanson)
- Prev by Date: Re: Treatment of Greek characters in CIF2
- Next by Date: Re: Draft JSON specification, round 2
- Prev by thread: Re: Treatment of Greek characters in CIF2
- Next by thread: Re: Treatment of Greek characters in CIF2
- Index(es):