[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
--
Reply to: [list | sender only]
Re: CIF-JSON draft 2017-05-15
- Subject: Re: CIF-JSON draft 2017-05-15
- From: James Hester <jamesrhester@xxxxxxxxx>
- Date: Tue, 16 May 2017 10:46:11 +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=at1FlIPN427EhGZltSmfebRMhZA2QRPGscXE3Hc1ak8=;b=aIUt6asLi+omZ4zHA0jAXDGIdAKKLospeFYCQZlDkqmBgI9b9DxWUJ4JP21vSAMJVC7SSfIyOv6ENEDLfNf6u4uAh9+yXVPBTg7EVgkzcamFrUPsEU6NRYYhq6fY/UbS+Mt55KQLTaJpcUhcSQaFK2NRBXBgHjNYEvn31Sjw7DGzKfgTEAQvOTBkM2KGOPF3Xpci2Q3pjP3nlMoo4yAWqQzhs1MD65YD44SFlOQjWUxMEpC1Il03dYRgFFmdOEmkzr5sMIdbnItlSXJ9MKVVFXFsBBo9P9qxyMKgG+fSOpa7pOUHi/uaou+iTZZXticArkqCAAvW5kWY9ZGNs+QPRg==
- In-Reply-To: <CAF_YUvUGexW-7iSfJWQ_c=WZNnbzBJeFaNfzKRVK4DKmdydp+A@mail.gmail.com>
- References: <CAM+dB2cAAY3CjC741WU0GqaWmAi2iGHtwZ82iA1bCwuNoG6nQg@mail.gmail.com><CAF_YUvVa0JXgAN9Bec6fjd6Nmco5W7EHWLN=Ba=daRR9U-2PzQ@mail.gmail.com><CACaHzQVYeOfS9zTe4gDJMVNCTgxtat0zhMAd2EMX=etXj5g2Gw@mail.gmail.com><CAF_YUvWV3huhwoBuCOkKXqCcYH+8kjFCPjoa=j_v61JC4H32Jg@mail.gmail.com><CAF_YUvUMbVz2j5=XXD5WD3G+0XB4tY=r1zwXuADB14qQNZTPvg@mail.gmail.com><CAF_YUvXPj9g6CEnsKmwZwrp7p550nyykrnQY9iN5wpEnDzrrYQ@mail.gmail.com><CAF_YUvUaJM0bwV4vKZwARQw4Q44LN+TOyr4Ghge3P_qn90tUHQ@mail.gmail.com><CAF_YUvUGexW-7iSfJWQ_c=WZNnbzBJeFaNfzKRVK4DKmdydp+A@mail.gmail.com>
Hi Bob, thanks for the document, I will incorporate your clarifications into the draft. Of the points not covered in my other replies today:
1. Triple-quoted CIF strings: these are purely a CIF syntactical device for encapsulating a string value, there is no meaning attached to these that is not captured by a normal JSON string.
2. data names in case-normal form: I can see no problems with this, does anybody else have any thoughts? Such a restriction would handily enforce the need for datanames to be canonically-caselessly unique as JSON requires all object names to be unique within their parent object.1. Triple-quoted CIF strings: these are purely a CIF syntactical device for encapsulating a string value, there is no meaning attached to these that is not captured by a normal JSON string.
On 16 May 2017 at 08:57, Robert Hanson <hansonr@stolaf.edu> wrote:
Sorry, I forgot to send this earlier today.
Here are my suggestions. I'm not trying to force anything on anyone here. I just find that Google Docs are very useful in such collaborative discussions. There are some differences and questions, as mentioned at the top of the document.
https://docs.google.com/a/stolaf.edu/document/d/1_dMrxL9Q3LJ BgZWrCdFfXRHjckzW6Z5MkAMqA-Ywu FM/edit?usp=sharing On Mon, May 15, 2017 at 1:16 PM, Robert Hanson <hansonr@stolaf.edu> wrote:Two points:
1. I do not understand the stripping of "data_" and "save_" from the names we have for these.2. Save frames. What is the problem with just doing this?"data_another_block":{ "_abc":["xyz"], "save_internal":{"_abc":["yzx"
], "_r.fruit":["apple","pear"], "_r.colour":["red","green"]} }, }That is, why the special "frames" list?On Mon, May 15, 2017 at 12:53 PM, Robert Hanson <hansonr@stolaf.edu> wrote:2) list item names need not be lower-case, right? Nothing I see in CIF says that they conform to the requirements of data names. Thus, CIF2 could have upper- and lower-case names in list items.Two questions arising:1) CIF2 mentions byte order. This would be the (optional) first two characters of the data stream?--On Mon, May 15, 2017 at 12:30 PM, Robert Hanson <hansonr@stolaf.edu> wrote:I have several friendly suggestions. I think the way to do this is to just give you a link to a Google Doc that has my suggested changes made in it, and let you react to that.I think this one is going to take some more elaboration:Entries at the same position in JSON list datavalues correspond to one another if the datanames belong to the same category.
BobRobert M. Hanson
Larson-Anderson Professor of Chemistry
St. Olaf College
Northfield, MN
http://www.stolaf.edu/people/hansonr
If nature does not answer first what we want,
it is better to take what answer we get.
-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
--Robert M. Hanson
Larson-Anderson Professor of Chemistry
St. Olaf College
Northfield, MN
http://www.stolaf.edu/people/hansonr
If nature does not answer first what we want,
it is better to take what answer we get.
-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
--Robert M. Hanson
Larson-Anderson Professor of Chemistry
St. Olaf College
Northfield, MN
http://www.stolaf.edu/people/hansonr
If nature does not answer first what we want,
it is better to take what answer we get.
-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
_______________________________________________
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]
- Follow-Ups:
- Re: CIF-JSON draft 2017-05-15 (Robert Hanson)
- References:
- CIF-JSON draft 2017-05-15 (James Hester)
- Re: CIF-JSON draft 2017-05-15 (Robert Hanson)
- Re: CIF-JSON draft 2017-05-15 (Marcin Wojdyr)
- Re: CIF-JSON draft 2017-05-15 (Robert Hanson)
- Re: CIF-JSON draft 2017-05-15 (Robert Hanson)
- Re: CIF-JSON draft 2017-05-15 (Robert Hanson)
- Re: CIF-JSON draft 2017-05-15 (Robert Hanson)
- Re: CIF-JSON draft 2017-05-15 (Robert Hanson)
- Prev by Date: Re: CIF-JSON draft 2017-05-15
- Next by Date: Re: CIF-JSON draft 2017-05-15
- Prev by thread: Re: CIF-JSON draft 2017-05-15
- Next by thread: Re: CIF-JSON draft 2017-05-15
- Index(es):