[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reply to: [list | sender only]
Re: Draft JSON specification, round 2
- Subject: Re: Draft JSON specification, round 2
- From: Marcin Wojdyr <wojdyr@xxxxxxxxx>
- Date: Thu, 20 Apr 2017 11:33:51 +0100
- 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=gmUE8noONfHAaLtLiZrohTWbPVIm49QCrGB0A9E/VAs=;b=sE6/D9N5m8FTq7y62LpCUwROl2rRa/xtJmgRlHiPPi2nc71Pj7yLjFwfSrWjV7S8ApkIj5PNXQ7VCiIr/qb+r6BG2pbobKsi/x/s1BGruR3wnOFkUx5L7fteyPKiUiYN6yLdokYUsrmoaTsgsIL6G0qiR8pHsTGofrsgtXPSLOI/xaHSOtpi4vepmuebxu7stG/lbohFtvatuyFow5+WS0GLG6GCWDfHO6kI/NEehhKkFAzIa6qwFX6SWXSu+Kn1/KNLiCaliEQnyfkze5zD/h2p9/qvfPVNOyhs8UCcmME+BNP3DGHYW0HmLmT+CN0+AI7fTfaIByyYh5NvUXeD5g==
- In-Reply-To: <CAM+dB2f6wLa0U8shrN5D6=B+u4tFWYPG9byXvA0FWf_9dWCGzQ@mail.gmail.com>
- References: <CAM+dB2d4HcnH7PZRC4jYO8KLyNxs4pws_baT7WKi6vRiD2z1ow@mail.gmail.com><CAF_YUvURvhf+CkErvsCjNr=b=Nq2=FkM68Z_Tap3EsAzfArc+w@mail.gmail.com><CAM+dB2fCeZh_LdnvMsjfYzLyz8wLqwDErCZkKYJR8TVudkc6xA@mail.gmail.com><CAF_YUvXh=J5UVAm1YqFt8xe8DuRS2qC_-wHk-Ou1aNJuvEuOxQ@mail.gmail.com><CAM+dB2f6wLa0U8shrN5D6=B+u4tFWYPG9byXvA0FWf_9dWCGzQ@mail.gmail.com>
On 20 April 2017 at 03:35, James Hester <jamesrhester@gmail.com> wrote: >> Come to think of it, all upper case keys could be non-cif keys since we>> specify all lower case for CIF keys. Are data names case sensitive? Thus,>> this could be>>>> META_DATA>>>> perhaps?>>>>> Ooh, nifty idea. Loosely speaking, datablock names are caseless (may not> canonically caseless match in Unicode speak) so we could stipulate that all> datablock names are lower case (or the Unicode equivalent). Let's see what> the rest of developers here think about this. I also like the idea of having all the keys lowercase in JSON.It will loose some (not essential) information, but having easy andfast access to blocks/frames/items is a huge advantage. (though I'd rather write it as METADATA without _) Marcin_______________________________________________cif-developers mailing listcif-developers@iucr.orghttp://mailman.iucr.org/cgi-bin/mailman/listinfo/cif-developers
Reply to: [list | sender only]
- Follow-Ups:
- RE: Draft JSON specification, round 2 (Bollinger, John C)
- References:
- Draft JSON specification, round 2 (James Hester)
- Re: Draft JSON specification, round 2 (Robert Hanson)
- Re: Draft JSON specification, round 2 (James Hester)
- Re: Draft JSON specification, round 2 (Robert Hanson)
- Re: Draft JSON specification, round 2 (James Hester)
- Prev by Date: Re: Treatment of Greek characters in CIF2
- Next by Date: RE: Draft JSON specification, round 2
- Prev by thread: Re: Draft JSON specification, round 2
- Next by thread: RE: Draft JSON specification, round 2
- Index(es):